Forum Discussion
RLS in Paginated Reports - User cannot view
Make sure you provide Build permission to the users for the underlying dataset - https://docs.microsoft.com/en-us/power-bi/paginated-reports-embedded-data-source
FYI, we're shipping this week the changes to permissions to align paginated reports with Power BI reports for all scenarios. Customers should no longer require "Build" permission when the items are in the same workspace or deployed in an app, and can use the new viewer role same as PBI reports can. This will show up in tenants later this week or over the weekend.
Thanks!
FYI, we're shipping this week the changes to permissions to align paginated reports with Power BI reports for all scenarios. Customers should no longer require "Build" permission when the items are in the same workspace or deployed in an app, and can use the new viewer role same as PBI reports can. This will show up in tenants later this week or over the weekend.
Thanks!
Hi chrisfin can you confirm that this feature has shipped?
For me the issue is as of today reproducable, i have to manually add app-users permissions to the dataset.
Just adding the paginated report to the app does not automatically give any dataset permissions to the recipients. Works only if i build a native PBI Report for this same dataset and add this report (hidden) to the app, after app publishing the app receivers then automatically added with "APP(..)" permissions...when i then remove the native pbi report from the app and republish...the user permissions on dataset switches to "Read,Build".
It has always been necessary to manage dataset permissions seperately with a paginated report, as there is no data model within the report itself like there is with Power BI report.
thanks for this insight! Ok, as long as the pbi service will not detect the datasets used by the paginated report i can workaround with a dummy pbi report using the same dataset and adding this as a hidden navigation entry in app...not perfect but works 😉
We can also reproduce this issue as of yesterday - we have a dataset (with RLS) and a paginated report connected to that dataset all in the same workspace. Both objects are included in the app and build permission is granted through the app. Workspace members and admins cannot reproduce the issue but app consumers are getting the "error communicating with Analysis Services" error.
I assumed that the build permission to the dataset granted through the app would be sufficient for provisioning access but sounds like that may not be the case? Do we need to explicitly grant the build permission for the user group outside of the permissions granted through the app?
Was this working before, and now is failing? Or was it not working before?
Also, are you giving users build/reshare permission who access this through the app?
