Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hi,
I'm hoping there is a simple fix - I'm just a bit confused.
I have a People Report (REPORT A) with data pulling from Sharepoint. There is Row-level Security on the dataset with users assigned to different business areas. It covers lots of different topics. My workspace runs in a premium capacity.
I created a copy of this report and narrowed down the content to one page only (REPORT B).
Users who have been shared access to REPORT B are not able to view this report and I don't know why. I don't know what would be restricted, as those this has been shared with have not been added to any of the security groups, therefore shouldnt be having any of the data limited to them. Their view looks like the following:
Data lineage of reports in question
Many thanks for any help
Solved! Go to Solution.
Hi @Anonymous ,
I'm afraid you are misunderstanding the use of RLS,RLS allows people to see a certain kind of contents,not resticting them,so you'd better create a user group where there are no filter applied and add them to that.
Hi @Greg_Deckler
All the roles I have assigned work correctly on the original People report, where I had wanted them to be in use. - There have been no issues when I created 'Viewing as' and also user feedback confirms that the roles are working correctly in practice.
On Report B (the copy) where I am having isssues, I don't want any of the users to be limited in what they saw so I have not added them to any of the user groups. Is that correct, or should I create a user group where there are no filters applied and add them to this?
Hi @Anonymous ,
I'm afraid you are misunderstanding the use of RLS,RLS allows people to see a certain kind of contents,not resticting them,so you'd better create a user group where there are no filter applied and add them to that.
Hi @v-kelly-msft ,
Thank you for explaining it!
I had thought that if a user was not in a group then that user would see all content.
An 'All Access' group created and issue remedied!
Thank you 🙂