Higher Precedence - Static RLS vs Dynamic Hierarchy RLS

[Anonymous]

Hi, 

I have a general question. I'm creating row-level security (RLS) for my dashboard which involves a factual table, a lookup table with unique users, and a bridge table to connect the lookup with the factual table. It's a 1:M relationship from the lookup -> bridge -> factual table all connected via a unique id column.

I created a hierarchy RLS for those users in my lookup which will translate to other tables. However, I have one user, Alex, who should only be able to view the data based on filter selection. The dashboard is split between two categories: Brunch and Dinner. Alex needs to see data points for Dinner. When I create Role A, taking the heirarchy I created, all works well with everyone but Alex. However, when I create Role B which filter = "Dinner" it takes higher precedence over Role A since it seems to be at a high granularity. Alex works fine but now everyone's security is not correct.

Is there a way to create both roles without conflict? Thank you!

Solution: Thank you for all the help! I was mapping the hierarchy incorrectly.

[v-zhangti · Accepted solution]

Hi, @Anonymous 

Can you provide a simplified PBIX file for testing? Do you expect that other users can view Brunch and Dinner, and Alex can only view Dinner?

Looking forward to your reply, thank you.

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.