Forum Discussion

GreeshmaN's avatar
GreeshmaN
Icon for Advocate I rankAdvocate I
1 year ago

local evaluation of TableJoin or table.nestedjoin with key equal compareres is not supported

Hi Everyone,

I am facing a weired issue with the below message 

"local evaluation of TableJoin or table.nestedjoin with key equal compareres is not supported" in the visuals i my reports, the visuals are not displaying the data because of this error. The reports are working fine and all of a sudden am facing this issue. There are no failures while refreshing the semantic model and the report, only when we try to access the report am facing this issue.

I found that in the visual I have three YOY columns.
Example: R YOY, S YOY, K YOY
After removing the above three columns the visual is displaying the data, I don't think there is an issue with YOY columns they are basically Current _ PY/PY. The error message dosen't exactly say in which table there is an issue. It's very hard to check what's causing this issue.

Please provide your valuable suggestions.



General Comment
Need Help

3 Replies

  • rohit1991's avatar
    rohit1991
    Icon for Super User rankSuper User
    1 year ago

    Hi GreeshmaN

     

    This error usually happens when Power BI tries to evaluate a nested join or table relationship locally, which it can’t do especially with DirectQuery sources.

     

    Could you please try below

    • Avoid nested joins inside FILTER, ADDCOLUMNS, or similar DAX if you're using DirectQuery

    • Try moving logic into Power Query or using calculated columns instead

    • If possible, switch to Import mode for that table

  • GreeshmaN's avatar
    GreeshmaN
    Icon for Advocate I rankAdvocate I
    1 year ago

    Hi rohit1991 
    I have a multiple table in my semantic model and also there are lot of transformations applied in the power query, so it's very hard to trace where the issue is coming from. I had to test with each and every scenario to find out the poroblem which might take lot of time. Is there any way to troublehsoot the issue where the actual issue is coming from. Because the error message is very generic, if we know it's because of specific table that would be easy to work on fixing the issue.

    Also the semantic model is in Direct query & Dual mode which is basically of Composite model. There are multiple reports based of this semantic model but YOY calculations are created at each report level.

  • GreeshmaN's avatar
    GreeshmaN
    Icon for Advocate I rankAdvocate I
    1 year ago

    Hi rohit1991 
    I noticed a workaround that worked for me, I re-deployed the semantic model and the report worked without any issues. This is very strange issue, if there are issues it shouldn't work even after re-deploying the model.

    But I believe the issue could be because of the following reasons:
    1. Direct Query mode
    2. Performance issues with Direct query mode, the queries that are sent to the Data source may be not able to fetch the data at particular point of time and I think that caused the visuals to fail.