Forum Discussion
Row level security doesn't work when using 'Both' cross filter direction
- 7 years ago
We have issued a fix for this issue in the latest build 15.0.1102.235. Please upgrade to the latest build available.
Thanks,
Rohit
Hello,
Desactivate RLS on your report, add a measure with username() formula and publish the report to see what username() looks like.
On desktop (in my environment) the result of username() is DOMAIN\login and on the server it is [email protected]
I'm seeing the same behavior as Anonymous. I've confirmed that the filter he's setup (using USERPRINCIPALNAME()) is correct, but irrelevant to the issue.
Removing the security filter on the relationship between Responsibilities and Cost Centres (and ensuring the proper UPN exists in the Responsibilities table) allows the upload to succeed. I can see the Responsibilities table filtered as expected, but then the other tables naturally aren't filtered.
- rpatkar7 years agoPower BI Team
We have issued a fix for this issue in the latest build 15.0.1102.235. Please upgrade to the latest build available.
Thanks,
Rohit- Anonymous6 years agoNot applicable
We are still encountering same error in Power BI Desktop Version: 2.76.5678.782 64-bit (December 2019)
Is this resolved? if yes the how.. please share the step(s).
Thanks
- Anonymous7 years agoNot applicable
Hi Rohit
I just saw it. I'm busy updating now and will let you know how the test goes.
Thank you for the update.
- Anonymous7 years agoNot applicable
Success! Thank you for the fix for this and the direct query issue. We were struggling to roll back and was going to restore from backup in order to roll back. Now we've just upgraded with the new patch and all is good (both direct query and security cross filtering).
Kind Regards,
Pieter