We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. 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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |