Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I have a couple of hundred workbooks I am interrogating with a PowerQuery. There s a problem in the source data, because one of the sheets n one of the workbooks has a '#NAME?' problem in a cell.
I want to find it so I can go fix it.
I suspect a numeric column is the culprit
My table is a couple of thousand line items long.... and the previw is only 30 lines at a time.
Suggestions?
Well, I've managed to solve my problem from a different angle.
Use Python.
A short script of 20 odd lines pulls 45,000 rows of data in less than 1 minute, and no frustrating "I can't do this" from PowerQuery on an Excel source.
Thanks for that .... functionality I did not know of.
Column profiling on entire dataset - yep
Column quality- there are no errors anywhere. Some Empty areas, sure, but nothing as an Error.
But there are errors ... it's just that Power Query cannot pick them up.
Now if I look at the data quality later in the list of APPLIED steps, then I run into this.
@Netrelemo
They appear on some steps, you just need to go over all the steps that are recorded and wait until the step updates itself (a few seconds).
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Well, maybe in your ideal world, but not here.
a) Your document advice "Handling errors at the cell level" is talking about cells in the Power Query results .. .not cells in the source data. You're not understanding the problem.
b) I can wait a full hour (the query takes 5 minutes to complete). All processe seem complete. Nothing magically appears. The quality analysis says there are 0% errors. Zero. But the query will not load data because there is a CELL ERROR in the underlying Excel document.
Power Query seems to have some fundamental weakness here.
Hi @Netrelemo
You can apply those steps :
1. From the view tab check on the option "Column quality"
2. If you have more than 1000 rows, you can test all of them if you change the default option:
Just click on the bottom left inscription and choose "column profiling based on all data set"
3. On hovering the mouse cursor on the place of statistics of quality m select the option of keep errors:
In this way you will stay with your problematic rows and their details :
You can also refer to the Microsoft documentation about the issue :
https://learn.microsoft.com/en-us/power-query/dealing-with-errors
from the part :
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
User | Count |
---|---|
88 | |
73 | |
69 | |
64 | |
56 |
User | Count |
---|---|
98 | |
92 | |
84 | |
74 | |
66 |