I am trying to automate document archival and I need to move files to other folders and subfolders within a document library and keep the same unique ID given by SharePoint to the file when uploaded/created. When I use the Move file flow action the file is given a new ID increased by 3 from the orginal ID (ex original file ID is 1401, moved file ID is 1404). When the move is complete the original file ID is not in the SharePoint document library (i.e. file ID 1401 no longer exists). The moved file appears as a new file due to the new ID and triggers other flows and causes issues with duplicating records. I use the ID as a unique identifier for tracking files in Excel and databases. What do I need to do to be able to move the file and keep the same file ID?
I provided below a sample flow that I used to test the move file action. Below are also screenshots of a test where a file was uploaded to folder 0_RECEIVED SharePoint assigned it ID 1401. After the flow executes the move file to folder RECEIVED_ARCHIVE the file ID is now 1404.
What do I need to do to be able to move the file and keep the same file ID? I cannot not use a copy and delete or create and delete actions since I must keep all document history and the same ID for the file in the document library.
I have made a test on my side and the issue is confirmed on my side.
You couldn't move the file in sharepoint library and keep the same file ID in microsoft flow currently.
If you want to move the file in sharepoint library and keep the same file ID in microsoft flow, please submit an idea to Flow Ideas Forum:
Thank you for the response.
Conclusion... the flow action of Move file for SharePoint does not work in a similar way as the "Move to" command in SharePoint libraries as descrided in Microsoft's documentation. The flow action Move files is actually a copy and delete original; that is very different from the "Move to" command. I confirmed it is a copy and delete by turn on admin logging and reviewed the log when I performed a test.
Here is a link to Microsoft's documentation and further down is a copy of the description for the action.
Moves a file. Works in a similar way to the "Move to" command in SharePoint libraries. Returns information about the new file after move.
In addition to that, the "move file" in OneDrive doesn't break the ID or the links you generate, in other words, works exactly like expected.
Is really increadible how unreliable Microsoft's documentation can be.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
Participate in the Power Virtual Agents Community Challenge
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.
Dont miss our very own April Dunnam’s The Developer Guide to the Galaxy! Find out what the Power Platform has to offer for the traditional developer.