Showing results for 
Search instead for 
Did you mean: 
Regular Visitor

SharePoint Move File action breaks Document ID Service assigned value

We have had a system in production for a couple of years now, however, in the last week or so we have observed that the Move File action in Flow results in the moved document being assigned a new Document ID when the Document ID Service feature ( is enabled in the Site Collection. This is a change in behaviour for the action as this was not happening previously. To compound this, the native "Move to..." action in the UI works flawlessly and preserves the Document ID assigned to the item.


Below is a screenshot of "LibraryA" showing 3 documents, each with a value assigned to "Document ID" by the Document ID Service. I have duplicated these values in a text field called "DocumentID History".



I have a Flow that is configured to run when the file is created/modified and a Yes/No field (not shown) that permits a document to be moved, via the Move File action, from LibraryA to LibraryB.


Below is the screenshot of after "DocA" was moved via the Flow and "DocB" was moved using the native "Move to" button in the Action Bar.


Notice that the Document ID value has been replaced in "DocA" but not "DocB".  This behaviour was not happening a week or so ago and so represents a change in the way the File Move action appears to be working.


I have raised a ticket with the Power Platform Support but thought I'd share this with the community now.

Community Support
Community Support


Hi @SimonChalfont ,


Thank you for sharing. If you just configured the Move file action and didn't make any other settings, then this change is weird.


Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Barry, 

Thanks for replying. Yes, it's more than weird; it's plain broken. It's ludicrous to have 1 behavior when moved via the UI and a completely different one when moved via Flow/Automate. It also completely undermines the value of the Document ID Service and breaks the fundamental promise that it "Assigns IDs to documents in the Site Collection, which can be used to retrieve items independent of their current location."

What's worse is that if you try to use DocIdRedir.aspx link with the expected Document ID then it is unable to locate the document.

Just to re-iterate, this is a change in the File Move action that has happened in the last week or so. It has been working as expected for over a year. 

I've been on a support call this morning and hopefully it will find its way to someone in the Engineering Team who will understand the impact. At the moment, we have a broken document management system for our finance team.


Hi @SimonChalfont ,


Thank you for your reply and look forward to the appropriate explanation or any solution given by MS Support.

If so, please share it with us.


Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Regrettably, if somewhat predictably, Microsoft Support has come back and reported that according to their “Subject Matter Expert” the Flow action is working as expected.  I have refused to accept that response and asked for the name of the person who has provided that assertion.

I have also reiterated the point that the recent change to the Move File action breaks the promise of the Document ID Service in SharePoint. As defined, the Document ID Service “assigns IDs to documents in the Site Collection, which can be used to retrieve items independent of their current location.”  The very essence of this feature is that it guarantees that when a document is assigned a value, then that value persists even if that document is moved to a different location. This guarantee is an absolute cornerstone of Enterprise Content Management and having Flow/Automate now break that promise is a serious issue that should be escalated quickly.

The impact is that in highly governed information management environments (i.e. legal, financial, healthcare) the Document ID value is considered sacrosanct and anyone who might have built their document filing routing logic using flows will now be facing a very serious issue as those values are now changing when before they did not.  The moment someone senior in either the SharePoint or Flow teams realises this then they will realise that a mistake has been made.

In my view, the issue is that in SharePoint/Flow terms, a Move File action is really just a Copy File followed by a Delete File and I suspect that code that was previously there to ensure the metadata of the item, including the Document ID, is preserved from the source item has been changed and as a consequence the Document ID value is being set on the copied item as if it is a new document (which technically it is) and not replaced with the original value (so as to keep it a “move”).


Not applicable

Has there been any feedback from Microsoft on this?  I've just tried using the Move File action and the SharePoint assigned ID also changes, incrementing by 3 every time the file is moved.  This action does not do what you would expect or the documentation describes and needs to be fixed.  How do we raise this to Microsoft?  Do we have to submit an 'Idea'?

Helpful resources


Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,700)