Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
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?
User | Count |
---|---|
102 | |
91 | |
84 | |
77 | |
71 |
User | Count |
---|---|
113 | |
104 | |
100 | |
73 | |
65 |