Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello All,
I'm quite struggling with a really strange behaviour on a published report.
Here is the context :
- We have 2 tables with 2 relationships :
1 active, 1 inactive
- I got measures in a Matrix using each, depending of the business rule.
- It works perfectly on Desktop
- It also works perfectly once published, with a contributor, member or administrator role in the workspace.
BUT, whenever the role is viewer i got this error message (sorry in french) :
If i translate, it would be something like :
"...., But table "Ventes - Détails MDV" has two paths to table "Ventes - Détails Commande" : "Ventes - Détails MDV" -> "Ventes - Détails Commande" and "Ventes - Détails MDV" -> "Ventes - Détails Commande"
Honestly, i'm totally confused there.
I reviewed difference between workspace roles, and i see not a single feature that could explain this.
If you have an idea, please don't hesitate !
Solved! Go to Solution.
Hi @Mephys ,
By my reserch, the problem usually caused by the RLS, which only takes effect when the user is in the viewer role.
You have two relationship between two tables, and I guess you use USERELATIONSHIP function to active the inactive relationship in your sample, which will cause an error when there is RLS. RLS is creating a direct path using the table relationships. So, when USERELATIONSHIP() is added, that can sometimes cause a circular reference. The limitation is listed in the official document: USERELATIONSHIP function (DAX) - DAX | Microsoft Docs
USERELATIONSHIP cannot be used when row level security is defined for the table in which the measure is included.
The general fix to that is that you have to adjust your filter flow (single or both) or otherwise change your model so that you do not have two paths between tables.
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Mephys ,
By my reserch, the problem usually caused by the RLS, which only takes effect when the user is in the viewer role.
You have two relationship between two tables, and I guess you use USERELATIONSHIP function to active the inactive relationship in your sample, which will cause an error when there is RLS. RLS is creating a direct path using the table relationships. So, when USERELATIONSHIP() is added, that can sometimes cause a circular reference. The limitation is listed in the official document: USERELATIONSHIP function (DAX) - DAX | Microsoft Docs
USERELATIONSHIP cannot be used when row level security is defined for the table in which the measure is included.
The general fix to that is that you have to adjust your filter flow (single or both) or otherwise change your model so that you do not have two paths between tables.
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.