Forum Discussion
Row Level Security - USERPRINCIPALNAME() Not Working?
If you had to look at the RLS pattern the issue is that you need to have it set up slightly differently.
I can confirm that yes the Viewer Role in an App Workspace will confirm that it will keep the RLS.
If you can test and read this blog post from Kasper where you can play with the model and get it working, which will give you a great understanding of how it all works: https://www.kasperonbi.com/power-bi-desktop-dynamic-security-cheat-sheet/
Hi GilbertQ
Thanks for that post
I actually started my own sample, pretty much one to one and am starting to slowly understand a bit more about row level security.
Some interesting points I noticed, is that while testing row level security in the service, it appears that as the owner/creator of the dataset regardless if I set myself up in a role, I am still able to see all the data.
Another interseting point, I noticed is that with the sample from kaspersky, it looks like there is a "bridge" table, lack of a better word that helps to unify the users and the profiles together. Then I am able to use both directions, and apply row level security check box.
Im still a bit gray on how relationships work in Power BI, in terms of the direction (single or both direction) but I think Im getting a bit of a better handle on things now, thanks to your post
- Hi there
No worries, that is a great starting point and trying to learn it with your own data.
You are correct that if you are the person who uploads the PBIX file you are the Admin and can see all the data.
With regards to the cross-filter direction set to both, this allows for the security to flow between the tables, which then means that it will then correctly apply the security.