Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.
Hi,
I'm wondering what will happen if one suer appears in multiple RLS groups.
for example, I have a user who appears in two security groups as below. I need to give her access to full company a+b + partial company c (only logistic and legal department).
How can I tell power bi there is a "or" relationsip between two groups?
Dynamic Role1 | ||
company | ||
a@bc | a | |
a@bc | b | |
Dynamic Role2 | ||
Company | Buisness Area | |
a@bc | c | Logistics |
a@bc | c | Legal |
Hi @Anonymous ,
So your requirement want to create a role that can see the content in A, B, and C?
You can refer to the blog I provided, it should be able to help you: Dynamic Row Level Security with Organizational Hierarchy Power BI - RADACAD
If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
It gets even weirder. You can have a user in two RLS groups with contradicting rules.
In general the more permissive rule overrides the more restrictive rule.
Can this still be done? Without RLS conflict?
Define "conflict". Permissive rules override restrictive rules. No conflict here.
By conflict here, I mean for example, the first role restricts users to only one region's data and it shows all brand categories. The second role restricts the user to a particular brand category data for all regions. The user is getting an error here due to the conflict in the nature of the roles. Which one of these can be classfied as a lesser restrictive role? Or how to achieve that?
Is the user getting an actual error message or are they seeing one product for one region?
The user is getting an actual error message. The message is as follows:
The query encountered security filters on a table relationship that cannot be reconciled for the current user. Please contact your administrator or developer to review role memberships and security definitions.
Please try again later or contact support. If you contact support, please provide these details.Hide details
Check out the November 2023 Power BI update to learn about new features.