March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hello,
I have a number of refreshes failing due to "The field 'FileLeafRef.Suffix' of the record wasn't found."
Does anyone konw what might be going on?
I have tried manual refreshes within the workspace and via desktop.
Through the Query Editor I see this is failing on some Excel files on Sharepoint so I checked permissions and nothing says things have changed, and the files are still there.
Lineage view shows all connections are successful but the refresh is failing.
Any help would be greatly appreciated!
Thank you.
Solved! Go to Solution.
I actually just removed the filter and sort all together.
Your solution might have been better, but at least this way if something changes for sort and filter again then by removing them I won't have to worry about it.
Whats strange is these querries have been working fine for months, then the night of the 20th they all broke. Feels like there was a release somewhere that broke it all, in SharePoint or PBI I dont' know.
Unfortunately the error messaging sent me down the path of permissions which was wrong.
Thanks for the post!
Good news,
MS has fixed the problem the Extension column no longer returns an error.
The PBI reports are already updated normally.
😉
I have noticed that is the case with Sharepoint files, the file extension is not being read correctly - for my reports i have fixed it by changing the following line in the advanced editor in M query.
FROM -
#"Filtered Rows" = Table.SelectRows(Source, each ([Extension] = ".xlsx") and ([Name] = <FileName>))
TO -
#"Filtered Rows" = Table.SelectRows(Source, each [Name] = <File Name>
I actually just removed the filter and sort all together.
Your solution might have been better, but at least this way if something changes for sort and filter again then by removing them I won't have to worry about it.
Whats strange is these querries have been working fine for months, then the night of the 20th they all broke. Feels like there was a release somewhere that broke it all, in SharePoint or PBI I dont' know.
Unfortunately the error messaging sent me down the path of permissions which was wrong.
Thanks for the post!
@Ironpixel probably some column name in the excel file is changed which is used in PQ and that's why it is failing. Go thru each Power Query step and check at which steps it fails and debug from there.
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
Hi @parry2k
"Through the Query Editor I see this is failing on some Excel files on Sharepoint so I checked permissions and nothing says things have changed, and the files are still there."
Some of the excel files have additional lines of data, some of the files haven't changed at all.
This seems to be happening at loading of the excel file and my permissions haven't changed.
This is happening on multiple excel files across mulitple Power BI files.
_Still looking.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
124 | |
89 | |
84 | |
70 | |
51 |
User | Count |
---|---|
206 | |
143 | |
97 | |
79 | |
68 |