Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hello all,
Needing some guidance! Hopefully there is a simple solution available!
I am working through several power BI report dataflows (through Fabric) which have errors relating to Pipeline Exceptions, Invalid Cell Value. However, when I go into the power query none of the steps are erroring out due to this openly, only the Pipeline is. However, I do see the error arise if I try to open the filters on the query and load more.
Typically, I would simply open the datasource and CTRL + F for the erroneous value...
The trouble is that the report is using a custom function to pull data from a folder full of templated spreadsheets into one consolidated view. I cannot tell which workbook the data error is stemming from.
My question is: Is there a method in Power BI to quickly and easily identify the source of the errors in the Excel workbooks they are pulling from?
Here is the error, as seen from Fabric dataflow refresh:
Error: DataFormat.Error: Invalid cell value '#REF!'. . RootActivityId = efe8610d-fb49-442c-ace3-09d4f9d8a6af.Param1 = DataFormat.Error: Invalid cell value '#REF!'. Request ID: 19fda3b9-bf43-485c-af05-11b147f97b8f.
Solved! Go to Solution.
I was able to resolve this issue by inserting a temporary step after the folder of excel workbooks is loaded into the query, which filtered the workbooks down by name into batches (beginning with). Using this I was able to test batches of about 5-10 at a time, until I narrowed it down to the two files which were throwing the "#REF!" errors. I opened them up, cleared up the formulas generating the errors, and now the dataflow is working again.
I was able to resolve this issue by inserting a temporary step after the folder of excel workbooks is loaded into the query, which filtered the workbooks down by name into batches (beginning with). Using this I was able to test batches of about 5-10 at a time, until I narrowed it down to the two files which were throwing the "#REF!" errors. I opened them up, cleared up the formulas generating the errors, and now the dataflow is working again.
Hi @PowerBI_Chaos ,
#REF! and #N/A are Excel errors, not Power Query errors, so you're correct to want to trace this back to the Excel source.
To get this identified quickly you need to first: ignore generic ChatGPT answers, second; do it in Excel (not in the Dataflow). Dataflows are slow to load/filter and the rows aren't guaranteed to be in the same order as your source anyway.
In your Excel file you can either:
-1- Hit F5 (Go To), click on 'Special', select 'Formulas' radio button, and check the 'Errors' box.
-2- Hit Ctrl+F, type #REF! or #N/A in the Find field and either 'Find All' or 'Find Next'.
Pete
Proud to be a Datanaut!
Hi there,
Thank you for the reply. I had tried to adjust my post last night, but it appears to have not went through. While I was able to resolve one of the two, using the exact method mentioned... The problem is that the second power query pulls data from a bunch of excel files in a folder. Is there any way in Power Query to tell which of the files the errors are coming from? Otherwise I would need to open each and every one of them up, and there are like 50 or more.
I took this over from my predecessor, and am trying to piece it back together. Pulling data in this manner is not my preferred method.
When you say that "the second power query pulls data from a bunch of excel files in a folder", do you mean it uses the Transform & Combine folder connector? You can tell if this is the case as you will have an auto-generated folder of queries called "Helper Queries" or similar.
If so, then you should see a [Source.Name] column in the combined query (the final one where all the files get combined together, not a helper query) that will tell you exactly which file each row has come from. You may need to click back up the query step list a bit in case this column has been removed in subsequent steps but, once you find it, you can use it identify exactly where your errors have come from.
Pete
Proud to be a Datanaut!
Thank you for your reply BA.Pete.
The query pulls yearly financial data from a folder full of excel documents using a custom function it seems. Below is the function (step) that is used to pull in this data. All of the preceding steps are getting to the folder location and removing unncessary files through transformations. After this step it is normal transformations cleaning up the data. Nothing appears wrong within the transformations, however when/if I try and 'load more' than the sample (1000) rows then the error data.format error '#REF!' appears. The problem is that the query does not tell me where the error is stemming from, which of the myriad of excel files that the query pulls from within the folder.
-------------------------------------------------------------------
Ok. If you were using the standard folder connector you would be able to select the step where the custom function is invoked and see which nested table showed as an error.
As it is, I think you'll need to go into your Dataflow, select the combined query, hit Ctrl+A on the table to select the whole thing, then go to the Home tab > Keep Rows > Keep Errors.
Depending how large/complex your data pipeline is, this could take a significant amount of time, but it should retain every row that contains an error in any column which you can hopefully use to identify the offending file based on the data contained in the other columns.
Pete
Proud to be a Datanaut!
Identifying the exact workbook, sheet, row/column, and cell causing errors in Power BI dataflows can be a bit challenging, but it is possible with a systematic approach. Here are some steps you can follow to pinpoint the source of the errors:
Check Data Sources:
Dataflow Query Errors:
Column Profiling:
Data Lineage:
Error Handling in Power Query:
Testing Individual Steps:
Excel Workbook Audit:
Data Validation:
Error Logging:
Consult Power BI Community:
Identifying the exact source of these errors may require a combination of these methods, as well as careful examination of both the Power Query steps and the source Excel files.