Forum Discussion
OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005)
Hi rocky09 ,
I had a similar report set up on the Power BI Service that failed to refresh but provided me with a more detailed error. It turns out one of the fields contains string values when the ODBC connection was expecting date. When I checked the set up for the original data source the field in question was shown as a string so I'm not sure where the change occured.
Luckily, in this instance, I think I'll be able to omit the field from the report as I don't think it's entirely necessary. Hopefully that will negate the issue.
Thanks,MarkJames
Solution Sagecheck the formats of the Column. First remove every step except source and try one by one. You will find which step is throwing the error.
Hi rocky09 ,
I had a similar report set up on the Power BI Service that failed to refresh but provided me with a more detailed error. It turns out one of the fields contains string values when the ODBC connection was expecting date. When I checked the set up for the original data source the field in question was shown as a string so I'm not sure where the change occured.
Luckily, in this instance, I think I'll be able to omit the field from the report as I don't think it's entirely necessary. Hopefully that will negate the issue.
Thanks,MarkJames
I am sure this is to do with the latest power bi updates. I have models that I created in 2019 that are giving me this error and I have noticed that the data types you set originally seem to revert to text.
Hello, I understand the source of the problem.
After checking the column types in Power Query, you will need to make sure in Power Bi Data that you have defined the columns in the same format as those of Power Query. The problem arises when the Power Query column type is equal to the column type in Power BI Data.By example
So, what worked for me was deleting the steps in the problem query, 1-by-1, and then Saving/Applying the changes. I kept working backwards until the error stopped popping up, and then I was able to diagnose what was causing the issues.