Hi @Ckatz
I do have a combination of PA and PAD flows integrated with OneDrive for a reason.
How I do it in that flow:
1. PAD bot 1 downloads files from system A, and saves them into OD folder (this is SharePoint library mapped to the local filesystem with OneDrive). OneDrive is set to start automatically on user logon.
2. PA flow triggers for every new file in a SPO library and performs certain operations, that includes adding data to Excel file in that library then removing the file. This is happening while PAD 1 is still running.
3. PAD 2 launches. It waits until all files are gone, meaning PA flow did it's job and then waits 5m for OneDrive to fully sync the Excel file.
Now, looking at your case - if you have a premium license - you could try to use build in SharePoint connectors to work with the file, instead of relying on OneDrive (my flow was create before these were added).
If you still want to use OneDrive, without fixed "wait" interval as suggested by @CKN , perhaps this simple trick would help:
1. PA:
1.1 Create cloud flow that triggers each time your excel file is updated
1.2 Once trigger (meaning the file was uploaded from desktop) - create text file in the same mapped folder, let's name it: excel_updated.txt
2. PAD
2.1 Before you edit excel - delete the "excel_updated.txt"
2.2 Edit the excel file as you do now
2.3 Now, wait for the "excel_updated.txt" to appear in the folder again (set up the timeout as you need)
2.4 Complete the flow
So the sequence of actions happening here is:
PAD deletes the excel_updated.txt file -> updates the excel -> pauses -> OneDrive fully syncs the Excel to cloud -> PA discovers that the file was updated and triggers -> PA creates the excel_updated.txt file -> OneDrive syncs the txt file to local folder -> PAD sees the file and continuous to complete the flow
Hope this helps 🙂
Share
Report
69
All responses (
Answers (
