Forum Discussion
RLS roles combination& Security Filtering Behavior = Both relationships
Hi all,
We have implemented the RLS security for the Power BI report and difined set of different filter for each role via DAX.
This works fine when user has single role membership, but throws an erro when user has 2 and more roles assigned
Error message "the user belongs to multiple roles that have security filters which isn't supported when one of the roles has filters affecting table with Security Filtering Behavior = Both relationships"
Expected behavious for me was - user with roles combinations should see the union of rows
Please, could you comment on above or suggest a workaround
Thanks
6 Replies
In my case, I fixed the issue by changing a many to many connection into a one to many. Which was possible on my table after removing the null values.
Still, I don't know why it was working fine before and they it suddenly appeared + the error message is clearly wrong.
I raised this with Microsoft and looks like like it is by design.
Hi Triggg ,
There is a similar thread that you could reference firstly.
If it can't work for you, please share a dummy file that we can test.
No, the thread you refer to is not the same problem. I have the same issue as Triggg, and it's nothing to do with both direction links (it's a single for my case), but both RLS profiles applied.
Have a look at
As far as we could tell in the December release of power bi desktop and service many to many cardinality relationships stopped working when multiple roles were selected.
There is a ticket in with microsoft but no response yet.
I believe you cna force it to work by replacing many to many relationships with a bridge table type setup but that's far from ideal.
I too have started to get this issue. Has been working fine for months but now stopped working with the same issue.
"The user belongs to multiple roles '****' that have security filters, which isn't supported when one of the roles has filters affecting table '***' with SecurityFilteringBehavior=Both relationships."
The table it references does NOT have security filtering behaviour set to Both.
Anyone found a solution for this?
