Forum Discussion
Local evaluation of Table.Join or Table.NestedJoin with key equality comparers is not supported
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!
Hi rkoffice ,
The error indicates that Power BI cannot evaluate the join operation locally due to the presence of key equality comparers, which are intended for internal use only and not supported in the Power BI Service environment.In Power Query, right-click each step and choose View Native Query.
If this option is disabled at any step, query folding is broken.
Try to remove Value. Native Query. from M expressions as it can interfere with query folding.
If folding cannot be preserved, consider switching the affected tables to Import mode instead of DirectQuery.
Hope this helps!
5 Replies
Are you in DirectQuery or Import?
Table.Join in M is typically a Merge
If this helped, please consider giving kudos and mark as a solution
me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Hi rkoffice ,
The error indicates that Power BI cannot evaluate the join operation locally due to the presence of key equality comparers, which are intended for internal use only and not supported in the Power BI Service environment.In Power Query, right-click each step and choose View Native Query.
If this option is disabled at any step, query folding is broken.
Try to remove Value. Native Query. from M expressions as it can interfere with query folding.
If folding cannot be preserved, consider switching the affected tables to Import mode instead of DirectQuery.
Hope this helps!
