This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi,
Context:
There is Paginated report directly connected to SSAS server. SSAS has RLS applied on itself which is confirmed using pbi report pbix file. But the Paginatted report is not able to access the same RLS which is already applied on the SSAS.
Questions:
1. Will the RLS be directly pulled by Paginated reports without doing any changes in settings as pbix file? It is assumed that we are using same credentials to access paginated report as we use for pbix file where RLS is seen perfectly applicable. and RLS is already configured at SSAS data source level.
2. If not then how can we setup RLS for independent paginated reports?
3. while importing ssas to paginated reports is there any connection between creating connection string and rls getting implemented or obstructed? like are there any options in advance properties while creating connection string that needed to be manipulated to make rls work?
@lukiz84 @Reddy5833 @Anonymous @TelmoBarbosa @lbendlin
Solved! Go to Solution.
Hi @satyamsd21 ,
You can see in this topic (Re: PBI Report Builder - Paginated Report RLS With... - Microsoft Fabric Community) how I worked around the problem.
Basically, I published the paginated report with a user that does not have access to the server. This way, when a specific user opens the report, there is no impersonation, and the data is filtered based on the user viewing the report (uses RLS defined at AAS level).
Before doing this, I had published the paginated report with my user (admin access), and all the report views were impersonated with my user, ignoring all the RLS definitions.
You can use DAX Studio, for example, through the All Queries option, to check which user is being used when querying the server through a paginated report viewing.
Best regards,
Telmo Barbosa
Hi @satyamsd21 ,
You can see in this topic (Re: PBI Report Builder - Paginated Report RLS With... - Microsoft Fabric Community) how I worked around the problem.
Basically, I published the paginated report with a user that does not have access to the server. This way, when a specific user opens the report, there is no impersonation, and the data is filtered based on the user viewing the report (uses RLS defined at AAS level).
Before doing this, I had published the paginated report with my user (admin access), and all the report views were impersonated with my user, ignoring all the RLS definitions.
You can use DAX Studio, for example, through the All Queries option, to check which user is being used when querying the server through a paginated report viewing.
Best regards,
Telmo Barbosa
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 6 |
| User | Count |
|---|---|
| 27 | |
| 24 | |
| 22 | |
| 22 | |
| 18 |