Power automate update sharepoint properties locked file issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1297188%22%20slang%3D%22en-US%22%3EPower%20automate%20update%20sharepoint%20properties%20locked%20file%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1297188%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EWe%20have%20developed%20a%20Power%20Automate%20document%20approval%20workflow%20running%20on%20a%20document%20library.%3C%2FP%3E%3CP%3EHowever%2C%20the%20workflow%20is%20unable%20to%20update%20any%20of%20the%20document%20properties%20through%20the%20SharePoint%20connector%20%22Update%20file%20properties%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20because%20the%20document%20is%20opened%20by%20the%20authors%2F%20reviewers%20etc%20while%20the%20workflow%20is%20running.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20separate%20%22on%20document%20creation%22%20Power%20automate%20workflow%20that%20updates%20document%20properties%20(e.g.%20pre-populates%20manager)%20doesn't%20work%20either%20as%20when%20the%20user%20clicks%20on%20new%20it%20by%20default%20opens%20the%20document.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20locking%20of%20the%20file%20was%20never%20an%20issue%20with%20previous%20SharePoint%20versions%20(e.g.%20using%20SharePoint%20Designer%20workflows).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1297188%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Approval%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1297297%22%20slang%3D%22en-US%22%3ERe%3A%20Power%20automate%20update%20sharepoint%20properties%20locked%20file%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1297297%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3ETry%20to%20check-out%20the%20document%20and%20then%20try%20to%20update%20the%20properties%2C%20before%20that%20you%20have%20to%20verify%20whether%20the%20document%20is%20in%20checked-in%20or%20checked-out%20status%2C%20based%20on%20that%20you%20have%20to%20proceed%20with%20the%20check-out%20and%20update%20actions.%3CBR%20%2F%3EPlease%20enable%20the%20document%20check-in%20and%20check-out%20feature%20to%20achieve%20the%20above.%20It%20is%20best%20for%20all%20the%20users%20to%20check-out%20and%20then%20modify%20the%20document%2C%20it%20can%20help%20the%20users%20in%20many%20ways%20and%20also%20the%20version%20history%20with%20comments%20is%20best%20for%20them%20to%20verify%20what%20changed%20in%20the%20document.%20Also%20helpful%20in%20easy%20recovery%20of%20the%20old%20document%20based%20on%20the%20comments%20and%20version%20history.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20it%20helps%2C%20please%20like%20it%20or%20mark%20it%20as%20a%20solution%20if%20it%20resolves%20ur%20clarification%20or%20issue%3CBR%20%2F%3E-Sudharsan%20K...%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

Hello,

We have developed a Power Automate document approval workflow running on a document library.

However, the workflow is unable to update any of the document properties through the SharePoint connector "Update file properties".

 

This is because the document is opened by the authors/ reviewers etc while the workflow is running.

 

A separate "on document creation" Power automate workflow that updates document properties (e.g. pre-populates manager) doesn't work either as when the user clicks on new it by default opens the document.

 

This locking of the file was never an issue with previous SharePoint versions (e.g. using SharePoint Designer workflows).

 

1 Reply
Highlighted
Hi,
Try to check-out the document and then try to update the properties, before that you have to verify whether the document is in checked-in or checked-out status, based on that you have to proceed with the check-out and update actions.
Please enable the document check-in and check-out feature to achieve the above. It is best for all the users to check-out and then modify the document, it can help the users in many ways and also the version history with comments is best for them to verify what changed in the document. Also helpful in easy recovery of the old document based on the comments and version history.

Hope it helps, please like it or mark it as a solution if it resolves ur clarification or issue
-Sudharsan K...