Local evaluation of Table.Join or Table.NestedJoin with key equality comparers is not supported

[RuchiK]

I'm facing an issue after publishing my Power BI report to the Power BI Service. The report runs perfectly fine in Power BI Desktop, but once published, I receive the following error:

Expression.Error: Local evaluation of Table.Join or Table.NestedJoin with key equality comparers is not supported.
Microsoft.Data.Mashup.ErrorCode = 10682.
The exception was raised by the IDbCommand interface.

My data source is Microsoft Dataverse.

I have not use this operations Table.Join or Table.NestedJoin in data transformation.

Would really appreciate any guidance or solution from someone who has encountered this before.

Thanks!

[v-pnaroju-msft]

Hi RuchiK,

We wanted to see if the information we gave helped fix your problem. If you need more help, please feel free to contact the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi RuchiK,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Hi RuchiK,

We would like to follow up and see whether the details we shared have resolved your problem.
If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft · Accepted solution]

Thankyou, @rohit1991, for your response.

Hi RuchiK,

Thank you for your follow up.

Based on my understanding, you are on the right path by applying minimal transformations; however, even lightweight operations such as creating custom columns or handling null values can affect query folding. Query folding is crucial for the effective functioning of DirectQuery and Dataverse within the Power BI Service.

In addition to the response provided by @rohit1991, please find below some additional steps that might assist in resolving the issue:

1. In Power Query, right click each step and select View Native Query. If this option is disabled after a particular step, it indicates that query folding is broken, which can prevent joins from being pushed down to Dataverse.
2. Reorder your transformations to preserve query folding. Ensure that steps such as custom column creation (SOW, Start Date, End Date), null replacements, and data type conversions are performed after any foldable steps like joins or column selections.
3. If query folding breaks due to complex business logic, consider implementing calculated columns such as SOW or date logic using DAX, or alternatively, create these as custom fields directly within Dataverse.
4. If full query folding cannot be maintained and there are concerns regarding performance or business logic, please consider switching those specific tables to Import mode.

Additionally, kindly refer to the following links for more information:
Understanding query evaluation and query folding in Power Query - Power Query | Microsoft Learn
Query diagnostics - Power Query | Microsoft Learn
Best practices when working with Power Query - Power Query | Microsoft Learn

We hope the information provided proves helpful in resolving your issue. Should you have any further queries, please feel free to reach out to the Microsoft Fabric community.

Thank you.

[RuchiK]

Hello @rohit1991 ,

I’ve applied minimal transformations on top of the DirectQuery Dataverse opportunity table, including:

• Selected only required columns for the report

• Created a new SOW column based on statecodename (using actualvalue or estimatedvalue)

• Added custom date columns like Start Date and End Date based on business logic

• Handled nulls and converted data types where necessary

All transformations are lightweight to ensure compatibility with DirectQuery mode.

[rohit1991]

Hi @RuchiK 

Even if you didn’t write Table.Join or NestedJoin yourself, Power Query can sneak them in for example, when you expand a related column or do a merge.

What’s happening is:
Power BI Desktop handles it fine because it can do the join locally. But once you publish it, Power BI Service requires the join to be pushed to Dataverse and if it can’t, the refresh fails with that "local evaluation not supported" error.

Could you Please try this:

Go back through your queries and check for any merged or expanded columns, especially from relationship fields.

If possible, try doing those joins earlier in the query, before any steps that might block folding.

If it still breaks, a safer route might be to load the tables separately and build the relationship in the model instead of in Power Query.