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
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.
Check out the April 2026 Power BI update to learn about new features.
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 |
|---|---|
| 37 | |
| 28 | |
| 28 | |
| 20 | |
| 18 |
| User | Count |
|---|---|
| 66 | |
| 36 | |
| 29 | |
| 25 | |
| 24 |