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.
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.
- adrien555510 years agoHelper II
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
- apralou3 years agoAdvocate II
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.
- DRibeiro183 years agoNew Member
A lot of thanks, man! You saved my life with this. I'm really thankful!
- austinsense10 years agoImpactful Individual
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!
- Anonymous5 years agoNot applicable
I'm having similar issue and I've been looking at it for a month now...
May I know how to check/know which step is causing the error?
I went into edit query and are these Error causing the problem? But these are just date modified and date created which I thought should not impact. Btw, my data source is from excel files on sharepoint. All data from 202105 (after april) cannot be refreshed and get loaded on PBI. In other words, take for eg. only HK file here for May is showing "Error" but all other country May files are not refreshed on PBI.
Any help is much appreciated !
- adamkn3 years agoNew Member
I came across this thread when trouble shooting a similar issue. I had a working PBI file based on Excel source files, and inadvertently broke the file while tinkering with some of the data fields. The solution for me was to adjust the Data Type in the Data tab, to align with the new format I had assigned to that field in Power Query. In my case, I had modified a field that was populating as a date, back to text in PQ but upon loading to PBI - it was trying to convert text back to date, which was throwing the error.