Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hello,
I am struggling to implement dynamic row-level security access to my data model. I have identified two relationships that are causing the problem (see highlighted in image below). If either of the highlighted relationships is deleted from the model, RLS will work; however, this causes my model to have erroneous reporting numbers. As you can see below, the user table is connected to the Organization table via "Location ID". The Organization table is connected to the Org Mapping Table via "Location ID". And, the Org Mapping Table is connected to the Item Sales table via "Organization Key".
Any possible solutions or ideas would be greatly appreciated.
Thanks!
You should avoid bi-directional filters. The one is likely needed for RLS in your case, but you should learn how to pass filters around with CROSSFILTER or TREATAS to avoid bi-di relationships, when possible. Can you go straight from the User Location Table to the Org Mapping table on location_id?
Pat
Hi Pat,
Thank you for your reply. I will take a look into CROSSFILTER and TREATAS. I am able to connect from the user location table to the org mapping table on location_idS. Unfortunately, I am running into the same issue as before with this new relationship.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.