Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
"I’m working on a Power BI project where I need to build a report that serves multiple clients. I’m considering using a single dataset and applying filters via a query string (e.g., ClientID=123) combined with Row-Level Security (RLS) to restrict data access. For those who have worked with this approach, how does it scale in terms of performance and security when dealing with large datasets? Any potential drawbacks to watch out for?"
This is a doomed approach. URL filters are the opposite of RLS. Use separate reports.
I have a database containing client details, and I want to create a report for each client. Even though the reports will be similar, I aim to implement a single report that can be used for multiple clients. I'm exploring two methods: 1) filtering a report using query string parameters in the URL, and 2) dynamically binding datasets to a paginated report.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |