Sent document for approval, approver viewed document in excel online, didnt close it and approved the document. I recieved an email saying User signed off on your item. Note that we were not able to update the column in SharePoint because the file was locked by a user. When the approver closed the file, it still didnt update and stayed on Pending? Should this happen? Any help would be much appreciated. Thanks Samuel
Yes,this should happle.
Since if the approver viewed document in excel online, didnt close it and approved the document, the flow would run when the document is approved. however, the "Update item" action to update the document status would run failed because the approver viewed document and didnt close it.Event if the approver closed the file sometimes later, the flow already run failed and will not update the document status.
So please let the approver make sure to close the document firstly, and then approve the document.
Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @v-yuazh-msft‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
Flow Community Manager
I have a similar issue but the file is not open and has not been opened drecently yet I get the message
Note that we were not able to update the column in SharePoint because the file was locked by a user.
Also is there a way to use the signoff as a template as i would like to perform more actions after the sharepoint column is updated
I also have this concern :
"Note that we were not able to update the column in SharePoint because the file was locked by a user."
> For me it's not a file like excel or word, but a simple item from a list in sharepoint..
I was able to fix this today by doing the following:
I have been working on this for weeks and even submitted a ticket to the PowerApps/Flow team. They were not able to fix it. Also, this was only occuring on a single doc library. I created a new library and everything worked just fine. I hope this helps.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.
Features releasing from October 2020 through March 2021
Fill out a quick form to claim your user group badge now!