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
Am just planning ahead; if the dashboard are to be segmented so that Group A viewers only see Dashboard A and Group B viewers only see Dashboard B.
The initial dataset is common, with the data involving unique IDs for A & B intermingled in tables.
One could groom apart the data at the table level - then build separate reports published to separate dashboards.
There was no ability to copy a report (has that changed?) so one must repeat that effort I think.
Or possibly one could make Report A - and then copy the pbix file and make Report B with some changes to the Query Editor.
Is there another approach that maintains segmentation so A doesn't see B and vice versa?
@CahabaData wrote:
Am just planning ahead; if the dashboard are to be segmented so that Group A viewers only see Dashboard A and Group B viewers only see Dashboard B.
The initial dataset is common, with the data involving unique IDs for A & B intermingled in tables.
One could groom apart the data at the table level - then build separate reports published to separate dashboards.
There was no ability to copy a report (has that changed?) so one must repeat that effort I think.
Or possibly one could make Report A - and then copy the pbix file and make Report B with some changes to the Query Editor.
Is there another approach that maintains segmentation so A doesn't see B and vice versa?
I think Row Level Security can be applied to your case, however I don't see it was mentioned by you, may I know what is your concern?
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 |
|---|---|
| 23 | |
| 21 | |
| 20 | |
| 17 | |
| 13 |
| User | Count |
|---|---|
| 58 | |
| 51 | |
| 37 | |
| 30 | |
| 26 |