Forum Discussion
RLS not working consistently - Only when refreshing
Hello,
I have a problem in my workspace with a report, I'm using RLS in Power BI Service following this schema:
The "All" role has the following RLS dynamic condition defined in the report: email = USERPRINCIPAL(). Typically this works fine, but sometimes, unexpectedly it does not work and users can't see the content of the visuals:
I thought it could be related to the session or authentication to PBI Service, but if one person starts having that problem, they will keep having it if they try with a different brower or using incognito navigation. The only way I got this fixed is refreshing the sematic model. Does anybody know why this is happening?
Hi jfer
The issue likely occurs due to a caching or authentication problem in the Power BI Service.
- Ensure the RLS condition email = USERPRINCIPALNAME() is correct and consistently matches the email format in your data.
- Verify users are logged in with the correct account and have the appropriate roles assigned.
- Refreshing the semantic model clears the cache, temporarily fixing the issue. To avoid this, disable Query Caching in the dataset settings.
- Ask users to log out and back in or clear cookies to ensure proper session handling.
These steps should resolve or reduce the problem.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" π
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Please Subscribe my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
1 Reply
- Poojara_D12Super User
Hi jfer
The issue likely occurs due to a caching or authentication problem in the Power BI Service.
- Ensure the RLS condition email = USERPRINCIPALNAME() is correct and consistently matches the email format in your data.
- Verify users are logged in with the correct account and have the appropriate roles assigned.
- Refreshing the semantic model clears the cache, temporarily fixing the issue. To avoid this, disable Query Caching in the dataset settings.
- Ask users to log out and back in or clear cookies to ensure proper session handling.
These steps should resolve or reduce the problem.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" π
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Please Subscribe my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS