Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
How to create a report with RLS control and a report that is not restricted by RLS in a pbix file without copying a fact table (because the fact table is too big and I don't want to copy it)?
Hi @rajendraongole1 ,
Check out Solved: How to use RLS on one page and NO RLS on the anoth... - Microsoft Fabric Community
if it hleps.
Cheers
ChenuSing
Hi @Will1 - To create a report in Power BI with Row-Level Security (RLS) control and another report without RLS restrictions within the same PBIX file, without duplicating the fact table, you can use measures and filters creatively.
attached the detailed steps, please follow and also sharing some resource please check
Row-level security (RLS) guidance in Power BI Desktop - Power BI | Microsoft Learn
Proud to be a Super User! | |
Thanks for your answer, this solution seems to inevitably copy the fact table, which will cause the file to remain very large❤️
Hi @Will1 ,
According to your statement, I think your requirement is to create a report with two pages one is under RLS control and another is not.
As far as I know, if you add RLS in your data model, users in each role can see the corresponding data.
For example, if UserA in role1, then UserA could only see that RLS restricts the data that role1 can see. We couldn't let UserA see all data without RLS at the same time.
So create a new report without rls or add a duplicate fact table may be the workaround.
If you want to restrict specific people to see data and some other people could see all data, you can try to user UERPRINCIPALNAME() to configure dynamic RLS.
Dynamic Row Level Security with Power BI Made Simple - RADACAD
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Will1 - You're absolutely right to aim for a solution that avoids duplicating the fact table and keeps the file size manageable.
Instead of relying on separate tables for restricted and unrestricted data, you can use DAX measures to dynamically control data visibility based on a toggle (eg. , slicer or parameters)
I hope this details helps. Thank you
Proud to be a Super User! | |