Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
I think I have this solved, so mostly recording this for other people to find.
On loading a query, many errors were reported. However, when I chose to show errors, the table in Power Query editor that is supposed to show errors came up blank.
Inside a Table.Group, I had an implicit cast. The calculation could return a fractional value, but I set the return type as integer. After changing the cast to explicit, the query no longer reported errors on load to Desktop.
// Before: causes load error.
{"Adjusted GLH", each List.Sum([Adjusted GLH]), Int64.Type }
// After: Explicit cast removes load error.
{"Adjusted GLH", each Int64.From(List.Sum([Adjusted GLH])), Int64.Type }
Is there some other way I could have viewed the errors as seen by Desktop if the Power Query editor wouldn't show them to me?
Solved! Go to Solution.
Hi @kleigh ,
Thanks for sharing your experience in resolving query loading errors in Power BI Desktop! I'm sure your efforts will help many more!
Power Query has diagnostics tools that can be used to analyze queries and their performance. You can start diagnostics before loading the data to capture detailed information about the query execution and potentially catch any errors.
If the table shows a column, you can click on the cell where the error occurred to see details of what went wrong.
And for advanced users, running PowerShell scripts can help diagnose problems by accessing the Power BI API and extracting more detailed error messages.
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @kleigh ,
Thanks for sharing your experience in resolving query loading errors in Power BI Desktop! I'm sure your efforts will help many more!
Power Query has diagnostics tools that can be used to analyze queries and their performance. You can start diagnostics before loading the data to capture detailed information about the query execution and potentially catch any errors.
If the table shows a column, you can click on the cell where the error occurred to see details of what went wrong.
And for advanced users, running PowerShell scripts can help diagnose problems by accessing the Power BI API and extracting more detailed error messages.
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 6 | |
| 6 | |
| 5 |