Forum Discussion
View Errors. OK, Where are they?
Hi comish4lif2 ,
In general this happens when there are no errors in the query, but errors occur when the query results are loaded into the data model.
Examples:
- unique key values in Power Query (case sensitive), that are not unique when loading (case insensitive),
- numbers with fractions in a column with data type Int64.Type (Whole Number),
- etcetera.
Or you can have a try.
In power query-> "remove rows" section, click remove errors and check if error disappeared.
Maybe some calculations that used in the query resulted in "NaN" and "Infinity" in some cells which were actually the errors.
converted the columns to "text" from decimal # in the query editor and then replaced values (NaN, Infinity) with Blank. and then converted the columns back to decmal # and saved it.
Please choose a way which suits you.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- comish4lif24 years ago
Advocate II
There's no calcutions.
There's no fractions.
The errors that I can see are a GroupID that is initially identified as a number (based on the sampling of the first 1000 rows by BI). If I change the datatype to text, Close and Apply, it still shows the errors.Seems like it's a bug.
- Anonymous4 years agoNot applicable
Hi comish4lif2 ,
Please click the steps on the Power Query. Check which step causes the error.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- dmccardle2 years agoFrequent Visitor
How do you step through to check for bugs please?
- paul_johnson1 year agoFrequent Visitor
I had the same problem. I fixed mine. My errors were the result of having a column with binary content at the last step of a query. I had one query that tied to a SharePoint folder to see all the files in that folder. The rest of my queries were references to that query - the query dependencies looked like a pyramid. The top of the pyramid was the problem. I copied the Source step to each of my queries and deleted the query at the top of my pyramid. No more disappearing errors.