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!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi @Anonymous ,
Probably because introducing this join creates such a loop in your data model, resulting in ambiguous table usage.
In this, when you introduce a relation between Table B and Table D, it's morelikely that it would result in a loop. The Case might be your Table C and Table D are already related. Since your Table B and Table C are related, if you introduce a new join between Table B and Table D, that will result in a loop as Table B and Table D are already related by an indirect relationship through Table C
This is the related document, you can view this content:
https://community.powerbi.com/t5/Desktop/Row-level-security-and-relationship/m-p/660109
https://community.powerbi.com/t5/Desktop/RLS-using-an-inactive-relationship/td-p/1017906
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 104 | |
| 81 | |
| 69 | |
| 50 | |
| 46 |