I created an approval Flow in a SharePoint document library and discovered that the "autosave" functionality in Excel or Word will trigger the approval flow before the end-user is finished modifying the document.
Has anyone found a way around this?
I created an approval Flow in a SharePoint document library and discovered that the "autosave" functionality in Excel or Word will trigger the approval flow before the end-user is finished modifying the document.
Has anyone found a way around this?
Someone else marked another answer as the "Solution" - Not sure who did that but it WAS NOT the solution and it DID NOT help.
This is the "workaround" I came up with to make this work:
As long as the end user completes all their changes to the file and to the file properties before clicking "Save" there will only be one approval sent out.
Hi @CP153319 ,
Two way:
1. Turn off the Autosave function in the file.
2.Where is the file saved in?
If the file is saved in sharepoint library, add a FileModifyStatus column in the library, let every one to modify the column to finished once they finish the update. you could create the flow with a Condition to check if the special column value is equal to finished, the approval would only start when the column is equal to finished.
No any other better solution for this issue.
Best regards,
Alice
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I'm using the trigger "when a file is created or modified" and the Flow is changing the approval status as it moves along. I appreciate your solution but I can't leave it up to the end user to trigger the flow - It must be automatic.
Hi!
Which trigger are you using? "When a file is created or modified", right?
If so, I would suggest any of these two approaches:
1.- Use "For a selected file" trigger, and request users to start the Approval Flow from Sharepoint menu. More info here -the example is with a Sharepoint List and 'For a selected item', but the approach is the same:
2.- Add a custom column to your SP Library, let's call it 'RequestApproval', type yes/no, default 'no' Request users to start the Approval Flow by changing it into 'yes'. Turn your current trigger a 'conditional trigger' by activating this feature, so it will only be executed if 'RequestApproval' value is set to 'Yes'. Now, once starts processing, your Flow should change this custom value into 'No' in order to avoid loops. More info on 'Conditional triggers' in this topic
Hope this helps