Forum Discussion
PBI Report Builder - Paginated Report RLS With Roles Defined at AAS Level
Hi Anonymous,
Thanks for the reply. Unfortunately the documentation you provided did not help.
I used the information shared in this link https://learn.microsoft.com/en-us/power-bi/guidance/migrate-ssrs-reports-to-power-bi to migrate the reports to Power BI Service, following this steps:
"Anyone with permission to access to the report server instance and the Power BI workspace can manually migrate reports to Power BI. Here are the steps to follow:
- Open the report server portal that contains the reports you want to migrate.
- Download each report definition, saving the .rdl files locally.
- Open the latest version of Power BI Report Builder, and connect to the Power BI service using your Microsoft Entra ID (previously known as Azure Active Directory) credentials.
- Open each report in Power BI Report Builder, and then:
- Verify all data sources and datasets are embedded in the report definition, and that they're supported data sources.
- Preview the report to ensure it renders correctly.
- Select Publish, then select Power BI service.
- Select the workspace where you want to save the report.
- Verify that the report saves. If certain features in your report design aren't yet supported, the save action will fail. You'll be notified of the reasons. You'll then need to revise your report design, and try saving again."
While I expected Power BI to secure the data based on the roles defined in the Azure Analysis Services Server and the user viewing the report, it appears that all queries made to the server are using the user who published the report, rather than the user who is currently viewing it.
I have reviewed the documentation regarding the usage of the "userid" parameter, but I am struggling to find a way to dynamically "call" a role using the "userid" parameter in the DAX query.
Any insights or guidance you can provide on this matter would be greatly appreciated.
Thanks in advance.
Best regards,
Telmo Barbosa
Hi,
I already managed to solve the problem. For me, it is not the correct solution but i did not find any other.
I have resolved the issue by publishing the reports using a user without server access. This allows queries to be made with the user ID of the viewer rather than the publishing user. I am considering opening a support request with Microsoft to seek further clarification and a potential long-term solution.
Best regars,
Telmo Barbosa