I currently have a flow which:
- Receives email.
- Saves attachment to SharePoint as .xlsx.
- Runs an excel script to convert the XLSX range to a table.
This works fine up to the execution of the script where I receive the error message:
Is anyone able to assist with troubleshooting?
It could be the case that you browsed to the script file in the script location box on the script Flow step and selected it, saved the Flow and then, afterwards, updated the script file? This may cause the step to no longer be able to find the script file. If you have updated that script file the Flow step may be looking for its original SharePoint DocumentId and that could have altered when the script file was updated. I had a similar issue but it was with File in the script Flow step because I replace the File every time the Flow runs. I overcoming this by putting the File value for the script job step into a variable and using the variable in the script Flow step File input box (see image).
Can you share what this looked like?
I'm having the same issue-
Converted MS form response to a multi-sheet workbook. Save it under a new name, run a script to delete the un-needed input sheets, and email the complete sheet back out.
It worked fine up until last Fri, now the run script flow step fails even though the script itself runs fine in a web browser.
I ran into this issue and it took a few hours to determine the cause. In my case I was copying an Excel workbook in SharePoint online and then completing processing on that copied file, importing data from it and then deleting it. I determined the cause to be that I had browsed to a copy of that temporary file and selected it within my Flow steps and then saved the Flow. As far I can determine when you do that what is actually saved is the SharePoint DocumentId. Because my Flow created and deleted the file that DocumentId changed every time it ran so it could not find the Workbook. I fixed it by initialising a string variable and storing the document location within it, I guess, forcing it to parse at runtime as opposed to save time. I guess that is how MattLincoln solution works too.
Hello Matt,
Please share some guidance on how I get the file name to concatenate, the file name that I get when I view the file on OneDrive online vs when using OneDrive via my file explorer window, differs and I can't seem to get it to work.
This can be caused if the location you are referencing has more than 100 items within the folder. I resolved by creating a new folder within the library and moving the script to there then running it within my power flow.
I too have same error
For a heads up with people if you wish to try and use a Script from a Sharepoint site it looks to be available now. You can now run scripts directly from Sharepoint sites which has worked greatly for me.
#1
Michael E. Gernaey
497
Super User 2025 Season 1
#2
David_MA
436
Super User 2025 Season 1
#3
Riyaz_riz11
244
Super User 2025 Season 1
Share
Report
All responses (
Answers (
