Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more
How to find where is the error? it's nothing under the table.
Hi @Anonymous
So are you clicking here to get that view? (no filters set?)
Some errors may not show up in the Query Editor, but are still reported as error when data is loaded into the data model.
An example would be that you have decimals in numbers that should be whole numbers as demonstrated in this short video.
I reported this as an issue with Microsoft and was told this is by design... ![]()
Hi @MarcelBeug
Yes that is true, because when data is loaded into the Query Editor it only Samples the first 200 rows.
Whilst when you load the data from the Query Editor into your Power BI Model it loads the entire dataset, and it is sometimes only then that it will then produce an error.
What I can suggest is if you know that your data has got, then format the column data type accordingly, as Power BI is doing a best educated guess.
Alternatively you could change the column to Text to see what different data types there are, and then once you know how to resolve the issue, go back into the Query Editor, resolve the data issue and try again?
Adding a column has nothing to do with loading data into the query editor; otherwise both can result in data mismatching the column's data type.
@Anonymous
So our best guess is that you have data somewhere in your table/query that doesn't match the column type, which could have happened at data load or by adding a column.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.