OLE DB or ODBC error: [Expression.Error] Local evaluation of join with key equality comparers

[Anonymous]

Hi PBI Community, 

I'm currently stuck with the following error: 

Backstory

I am attempting to create a report in PBI Desktop (February 2020) with a DirectQuery connection to a PostgreSQL database. I have 5 tables within the report (a centralised Date table and 4 e-commerce data tables, all of which have a Date column). I am able to build visualisations within the report with data from the various tables individually without any problems but when I make a relationship in the data model between the DateTime table and any of the e-commerce tables (necessary) I get the above error. 

Trouble-shooting thus far

Trawling through the interwebs, some posts have vaguely suggested that this error may be due to trying to join mixed data types (I can confirm all of the Date columns I'm trying to relate are of the same underlying format) or joinAlgorithms (I don't have any table joins or merges, as far as I am aware)(@ImekF solved this one, might be able to help here?).

I am at a loss.  I include below a sample of data for each table.

Date table

E-commerce tables follow same format as below

Hopefully someone can help, and many thanks in advance!

[Deepanshu_46]

Did you get it resolved? I'm also stuck in the same issue and unable to resolve it. Your help with this would be highly appreciated.I am using Direct query connection with snowflake.

[mwegener]

Hi @Anonymous ,

I always try to avoid DirectQuery mode or reduce it to simple queries.

Hence my questions:

- Do you really need DirectQuery mode?

- Can you merge the queries with SQL beforehand?

[Anonymous]

Hi @mwegener ,

Thanks for your reply.

The purpose of this report is to provide near-real-time-data to stakeholders in our business, and given that we are using Pro licences (read: 8 times/day refresh not timely enough), DirectQuery is necessary. 

I will look into the viability of combining the data into one SQL query but if we can find a PBI solution or at least an explaination for why this error is occurring that'd be great. 🙂 

[amirh]

Any news?

Maybe a fix/workaround?