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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I am working with a dataset where Row-Level Security (RLS) is implemented, and we have multiple thin reports. We now have a requirement for one of these thin reports to display global numbers, effectively overriding the RLS implementation.
My current solution involves creating duplicate tables (both dimension and fact tables) specifically for this report to bypass RLS. However, this approach leads to having multiple fact tables with millions of rows, which significantly increases the dataset size and computational overhead.
Is there a more optimal way to achieve this without duplicating large fact tables? Any suggestions or best practices would be greatly appreciated.
My dax to filter the dataset looks like this.
Is there a more optimal way to achieve this without duplicating large fact tables?
Not really. Consider using separate reports/audiences. But the data duplication is required.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.