Forum Discussion
Test Role : Join Paths are expected to Form a Tree. Two Join Paths To Table
Hi,
I have a power bi report I made a few month ago (with an earlier version of power BI) which was working very well but I had to make a few cosmetic modifications.
With the current version of power bi, when I test the report with "View as role", I have an error message: "Join Paths are expected to Form a Tree, but the table 'sales' has two Join Paths To Table 'SalesRep'...." My role only filter on a SalesRep.
The error does not occur when the "View as role" is not activated and I Slice on the SalesRep.
I also tested the security on powerbi.com with the test as a role and I have the following error:
" Couldn't load the data for this visual
Couldn't retrieve the data for this visual. Please try again later.
Please try again later or contact support. If you contact support, please provide these details"
It was working before, is it a bug ?
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. Can't really help more without a picture of the relationships.
9 Replies
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. Can't really help more without a picture of the relationships.
Greg_Deckler I faced similar issue recently. I change the relationship to single instead of both and that resolved the issue. Thanks.
Anonymous
Please check if you apply multiple row level filter on same table. See a similar thread below:
Regards,
HI Greg_Deckler
I have the same problem. I have two paths but one is not active. I activate it only in a misure.
Tha strange thing is that witout testing role, my report works well, but when I try to apply a role, I see the error message
Thanks in advance
Enrico
Hello,
Try the below you should be able to get this resolved.
1. Check if the issue is related to visual. Try to use old table to create a new visual and check if the issue appeared again. 2. Check if the issue is related to Row-Level Security. Try to delete the old Row-level security, then build a new one to test if the issue appeared. 3. Check if the issue is related to the relationship. Remove the relationships and re-create the relationship and test again. If above is not help, please share some detail information about your issue.
Regards,
naveen
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.
