Forum Discussion
OLE DB or ODBC error DISP_E_TYPEMISMATCH
- 10 years ago
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
Can you just delete the "changed type" step
- adrien555510 years agoHelper II
Sorry, didn't mention that deleting only "changed type" wasn't enough.
I had to delete all steps to get the connection with the data back.
Anyway, I'll recreate the steps, but It's a bit of a pain if it happens again after many changes in the query editor. We'll see :)
Thanks!
- evang55010 years agoMicrosoft Employee
Hi adrien - did you ever figure out why this was happening? And if there was a fix/work around? I'm having the same issue.
- adrien555510 years agoHelper II
Hi Evan,
Yes it worked for me. I had to remove all the applied steps (5 or 6) until the step 'changed type' which seemed to cause the error.
Since I re-created all the steps, the error never showed up again, so worth trying it!