Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
"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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
4 | |
4 | |
4 | |
4 | |
4 |