Forum Discussion
OLE DB or ODBC error DISP_E_TYPEMISMATCH
Hi All,
this error shows up when I try to refresh data.
The data source is a local csv :
Config: windows 10
thanks for helping :)
Adrien
The type mismatch is probably happening because you're doing some conversion from the orginial data types - go into the query editor and remove any type conversions and see if that works.
23 Replies
This is the 3rd time this has randomly happened to me. I have not changed the source data. Does any one have a resolution?
Each time this happens I have to start from scratch and add the source again, add my conditional columns, etc. I basically have to redo my entire report.
So far I have tried deleting all the "Changed Type" tasks from the query editor, re-installing Power BI, clearing my Power Bi cache. And no luck.
Please,
Completely stuck with this.
Since the error talks about "type mismatch", I tried to define all data type to 'text'
but no effect,
Help!
The type mismatch is probably happening because you're doing some conversion from the orginial data types - go into the query editor and remove any type conversions and see if that works.
It's kinda weird, as by removing all steps in the history, it does the trick, data is refreshed, and by opening again the query editor, PBI recreates automatically the deleted steps (which are Promoted header, and Changed type).
I performed the test on a backup file.
To "clean" the production datasource, I then need to delete all applied steps in the query editor....
As there are many steps applied, is there any alternative, so as to avoid to recreate each and every step?
Many thanks for helping me resolve this issue
Unfortunatly I am now getting this error on a dataset that had been working fine for months. I dont even have any change type commands in my query. The only reason I knew there was an error is because my on premises gateway data suddenly stopped refreshing today and no ones dashboards worked.
Any other ideas on how to troubleshoot?
Thnk you,
Jesse
Never mind! One of our sales reps accidentally typed "Trina" into the sales order number field and hit "save"... sigh. All good now.
Just in case someone experiences this problem still.
Although I had not made any changes to my columns, it simply had a conflict with the name of the columns.I had used the letters "i" and "I" (in capitals) to name two of my columns.
I changed the names of the columns, closed and applied, and it worked again.Paulo
I have the same issue - what did you do to resolve this?
