Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi, I have a challenge with the following use case and I'm hoping somebody could help me. I created an employee scorecard report, that contents all necessary data for all approximately 100 people. The goal is providing every single employee its own (filtered) dataset in a dashboard. At the moment my only - very time consuming- idea is, setting a report filter for each employee, uploading each report to Power BI Service and creating a single dashboard for the employee. Is there any trick or different approach providing a same structured dashboard based on the same dataset for different employees instead of copying pre-filtered reports 100 times? Thanks in advance 🙂 Stefan
Solved! Go to Solution.
@SFeldmann Setting a report filter won't be a secure way of only showing each individual their information, they can still interact with the filters.
You should look into Row Level Security, this would allow you to build 1 model/reports for all users.
@SFeldmann Setting a report filter won't be a secure way of only showing each individual their information, they can still interact with the filters.
You should look into Row Level Security, this would allow you to build 1 model/reports for all users.
Seems the solution only works for Direct query reports .
Is there any solution for Commit querries
I need to show reports by customers and the customer should not be able to see data for other customer.
Any suggestion
Hi
I have a similar use case except the data is not sensitive so I do not want to use Row Level Security.
Mine is a sales report, where each branch manager will need their own pre-filtered dashboard. Branch managers report to Region Managers, who need their own version.
Probably looking at about 175 dashboards!! Not ideal!!
I don't want to use RLS as a workaround because it's not the right solution for this use case.
Is there another option?
Any help would be very much appreciated!!
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
34 | |
31 | |
19 | |
12 | |
8 |
User | Count |
---|---|
52 | |
36 | |
29 | |
14 | |
12 |