I have been working with an export from my hr system, and wanting to import the data into an Excel file in a SharePoint library.
I had success using the Microsoft Excel Online Helper scripts when importing the file into an Excel worksheet in OneDrive. I want to update the flow to write to a shared Excel file located in a Sharepoint library.
Once I got the file permissions correct, I am able to select Sharepoint and I can select the .xlsx file located in the Sharepoint library. This is basically a copy of the same file I was using in the OneDrive location.
However, I am receiving the error: "Failed to load spreadsheet."
See the attached screenshot for the message details.
Any thoughts what might be different? I was wondering if something is hinked in the caching maybe?
Thanks as always for your time and help!
Can you share your spreadsheet? I assume your sheet is named "Sheet1"?
Correct, the sheet is named "Sheet1".
I have attached a copy of the downloaded worksheet.
You don't think there is any caching going on since the flow step was first using a OneDrive location and is now using a SharePoint location?
Test Employee List SharePoint.xlsx (16.4 KB)
So it works fine when in your OneDrive, but not when in SharePoint? Can you try a new flow step install from the marketplace and test as well? I just tested toggling between OneDrive and SharePoint and it seemed to work fine.
Tyler - I performed the following with success:
#1 - I deleted the export flow
#2 - I created a new flow and imported the latest version from the Marketplace
#3 - This time, I set it up directly to SharePoint (not OneDrive first). After a couple of saves and selections, everything worked as expected.
I wonder if the issue is: all the saves and updates that happen in the flow step are just not condusive for changing the file type (i.e. from OneDrive to SharePoint).
We are running into a few other issues, but I will address them in new conversation threads.
Thanks for your help on this!
-mitchel
Potentially. I tried swapping and everything was working fine on my end. If you share your old flow zip here I could maybe check the underlying data to see if that's the case.