DirectQuery in Composite Model

[victor_s]

Hi. I have a composite model with direct queries that looks like this

When I try to make a table visual with user_action metrics and aggregation by country, I get the following error:

OLE DB or ODBC error: [Expression.Error] Local evaluation of Table.Join or Table.NestedJoin with key equality comparers is not supported..

I couldn't find any mentions that DirectQuery does not allow "nested" relationships. So, I guess I am missing something here. 

[Anonymous]

I had the same issue. The solution for me was that I accidentally sorted one of my dimension tables in Power Query. I don't think you can do any modifications to dimension tables in the Power Query if they are related to a direct query table. In my case, the dimension table is in Dual mode and connected to a Direct Query Fact Tabel. It worked again after i deleted to step in Power Query. 

[wastek]

is there any solution for this problem available ? We are facing the same with postgreSQL direct query:
Without it we cannot make any charts using fields from 2 different tables having a correct relationship

[Aakash96rah]

Any solution for this? I am getting the same error

[Anonymous]

Update:

After some investigation I discovered that during my change to the formatting I accidentally changed the data type of some of the fields in one of my tables which was part of the join. Although the modified fields were not keys used in the join it was enough to trigger this particular error. Upon restoring the types to their correct settings my visuals started working again.

Aside: The reason why I accidentally changed the type of some fields was due to an issue where filtering the fields and selecting multiple fields using shift still selected the fields that were not visible. I assume this is a bug.

[Anonymous]

I've just hit this issue after adjusting some formatting settings for Date values. After making that change a number of visuals which were loading previously, fail to load and the details show the "Local evaluation of Table.Join or Table.NestedJoin with key equality comparers is not supported".

One of the visuals affected doesn't reference any of the changed columns at all.

The puzzling thing to me is that Power BI appears to have convinced itself it can't do a thing that it was doing previously.

The error message could certainly benefit from detailing what tables it was trying to join and what keys it was referring to.

[Anonymous]

did you manage to fix the problem?

[amirh]

any news

[amitchandak]

Which Databases in there for Direct Query

[victor_s]

postgresql