Forum Discussion
Detected type mismatch Error
Hi LB-Tech
That is the error query which gives you the idea of what the errors are abut you're supposed to fix the type mismatch error from the referenced query itself. The common scenario fo a type mismatch error is that a coliumn has been set to a type number but some of ther rows contain characters other than numbers so naturally those non-numeric characters cannot be converted to numbers. Once the type mismatched error is fixed in the referenced query, that error query should not return any row. If you click the blank space next to a cell with error, it will tell you what the error is. In the screenshot below, Column1 is set to type number but there are rows with alphanumeric characters thus the error.
Hi LB-Tech
That is the error query which gives you the idea of what the errors are abut you're supposed to fix the type mismatch error from the referenced query itself. The common scenario fo a type mismatch error is that a coliumn has been set to a type number but some of ther rows contain characters other than numbers so naturally those non-numeric characters cannot be converted to numbers. Once the type mismatched error is fixed in the referenced query, that error query should not return any row. If you click the blank space next to a cell with error, it will tell you what the error is. In the screenshot below, Column1 is set to type number but there are rows with alphanumeric characters thus the error.
Thank you for the reply.
So, You are refering this error is a normal problem. Is there any other way to stop this mismatch error.
If in case of scheduled refresh, will this error disturb the process?
The query will still load most of the time and will return blank rows for those with errors. For example, changing data type of a column to date when someone of the values contain string will error out for those rows but loading wont be affected. However, if that error is because the date is in the wrong format - for example, if 24/12/2024 returns an error because your locale is set to US but the source uses GB then this needs to be corrected in the query itself. If not, you'll get blank or wrong dates - think about 7/1/2024 being July 1 instead of Jan 7. Ignoring the error is a case-to-case basis but investigating why there is an error is worth doing than risking loading incomplete or wrong data.