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
Thanks, this lead me to solve this problem with a file that had been working fine for months.
- Take a copy of steps in advanced editor for problem table.
- Clear all steps except source.
- Apply and let model complete data refresh without error.
- Paste all steps in advanced errror to reinstate table.
- Apply and model should complete data refresh without error.
Hugely frustrating and weird fix demonstrating that nothing was actually wrong with the file in the first place but something had changed in the environment.