OLE DB or ODBC error: Type mismatch - With no transformations done to Datatype

[Kurtle]

Hi everyone,

I am receiving this error when trying to add a couple of new columns to my dataset: OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH)).

I have combed through the forums here and in a variety of other places to try and find a solution but they all appear to say that it is due to a data type transformation which I am not doing, just filtering: 

The column that I believe is the root cause is deleted_at which I filter down to be null.

In the source (MariaDB) the datatype is timestamp:

 

Does anyone know if this is an issue with the source system or if I am doing something wrong? 

Thank you in advance!

[mwegener]

Hi @Kurtle ,

was your problem solved?

[Kurtle · Accepted solution]

Yes, this problem was solved after a week and a half of back and forth with support. There were 2 cell values that were causing this issue. Instead of 2020 the cell had 2020 (10). Not sure why the quary wasn't returned with errors instead of cancelling the entire refresh but they are looking into it some more.

[amitchandak]

@Kurtle , refer these and try to find the error

https://www.youtube.com/watch?v=OE6DPmKqN7s

https://www.youtube.com/watch?v=9-Lag0VOiTs

[Kurtle]

@amitchandak The table the is causing this issue has less than 100 rows with no errors in the date columns. I only use the deleted_at column to filter out items that have been soft deleted. These videos do not cover the OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH)) error

[v-zhenbw-msft]

Hi @Kurtle ,

Refer the following post, hope them help.

https://community.powerbi.com/t5/Desktop/Error-OLE-DB-or-ODBC-error-Expression-Error-We-cannot-conve...

https://community.powerbi.com/t5/Desktop/OLE-DB-or-ODBC-error-Type-mismatch-Exception-from-HRESULT/m...

Make sure your column does not have different types of data.

Best regards,

Community Support Team _ zhenbw

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Syndicate_Admin]

> Make sure that the column does not have different types of data.

This was the solution for my case. The last records added to my dataset were in a different format.