We are rolling out shared datasets within our organisation. All our workspaces are created via the new workspace experience. Workspace 1 contains the dataset and Workspace 2 contains the report. We have published Workspace 2 as a Workspace App in order to share the report to multiple users via AD groups.
We have configured the following permisisions:
- In tenant settings: Use datasets across workspaces for the entire organization = Enabled
- Workspace A dataset:
[Test1] Direct Access: build permission
Workspace Access: Viewer
[Test2] Direct Access: build permission
Workspace Access: not added
- Workspace B report: viewer
We get below errors:
"Permission required: you cannot see the content of this report because you do not have permissions to the underlying dataset. Please contact the dataset owner to request access". &
"Something went wrong Unable to load the model"
How do i set this permission correctly so end users doesnt need the contributer role? Currently our endusers has the contributer role because this is the only way for them to see data, but ofcourse this is not the ideal situation.
Solved! Go to Solution.
I think this may be a dataset permission issue.
The first and last bullet specify that you the user accessing the dataset will need at least Read access to the dataset.
You may need to go to the dataset and assign Read permissions to the users you want to grant access to.
Hi @npergand ,
I've also tested that scenario,
This is the settings for workspace 1 (dataset)
the 3rd user has Read, build and reshare access
and this is the Access settings in the workspace the same users is assigned the viewer role
This confuses me, as I haven't been able to reproduce your issue.
We have the same tenant setting enabled.
When end user X gets the App, he received the first error you stated: "you cannot see the content of this report because you do not have permissions to the underlying dataset. Please contact the dataset owner to request access"
The report in the app now loades successfully for the end user.
I'm not sure what the difference is. We did not experience the "Something went wrong Unable to load the model" error.
I don't know if it is worth noting that both workspaces are on our premium capacity.
Hi @collinq ,
Yes. The user has the viewer role in the APP workspace & in workspace 2. If the user goes to ''Apps'' he sees the dashboard, but when he open the app/report he got the error "Something went wrong Unable to load the model"
If I assign him the contributer role in workspace 1 (dataset), the error disappears and he is able to see the data in the app/report, but we don't want to give end-users contributer role. So the issue is that the user CAN see the APP or report in the workspace but is not able to see the data.
Hey @matDutch ,
I don't see you mentioning it - but are you using RLS? (Grasping at a straw there.) Is this Direct Query or Import (or something else)?
hey @matDutch ,
Well, I was hoping that this was related to RLS or the data itself. I think the issue is the cross-sharing. I found this article that has Considerations and Limitations that seems to indicate they need build access to the dataset. (Exactly what you do NOT want to do.)
I say that based on this sentence:
Which I found on this page: Intro to datasets across workspaces - Power BI | Microsoft Docs
This one might be helpful as well:
Hi @collinq Thank you! I have read it as well, im just wondering how others set this up as i haven't found the right solution.
For the test i assigned him the Build role and he is still not be able to see the data. So i don't know what i'm doing wrong here.
Click here to read more about the June 2022 updates!
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Mark your calendars and join us on Thursday, June 30 at 11a PDT for a great session with Ted Pattison!
Join us on June 20 at 11 am PDT when Kim Manis shares the latest on Azure Synapse analytics, the Microsoft Intelligent Data Platform, and notable Power BI Updates from Microsoft Build 2022.