Join Paths are expected to Form a Tree. Two Join Paths To Table... Row Level Security Error

[campelliann]

Hi, 

I am getting this error when I test a role. The role filter is applied on the Table "Lookup_BU" (upper left in the model below)  I am not sure why this happens. I dont understand if it is the model per se, or the fact that I am using Userelationship in some of the measures.

So why this is, and how to solve it? 

[jaap_olsthoorn]

For me the issue was that the measure that was being used, used CROSSFILTER to overrule some relationships. I re-wrote the measure to not use CROSSFILTER but something else (I stored the list of values I needed in a calculatetable, and referred to that instead of using any relationships at all).

What I still don't understand is that this measure broke when using RLS, but not when using the exact same filters using the filter pane or a slicer. Not sure what the real difference is between the two.

[Anonymous]

Hi @campelliann ,

Seems really weird that RLS would cause this. The error that you are getting indicates that you have two active relationship paths between two of your tables, so Power BI doesn't know which one to use. 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. 

I have also found a similar post, please refer to it to see if it helps you.

Solved: Test Role : Join Paths are expected to Form a Tree... - Microsoft Power BI Community

My suspicion is that you really do have two join paths between the tables. This is usually the result of the cross-filter direction being in both directions on all relationships and you need to change one to be in a single direction. 

Best Regards

Community Support Team _ Polly

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

[campelliann]

Hi there and thank you, it is really weird indeed, but the visuals were only breaking with RLS. But Powerbi didnt said that the model was ambiguous and this seems to me the same kind of error. One of the paths is inactive as you can see in the picture. I managed to solve the problem removing "userelationship" and replacing it with Treatas + crossfilter (none).