Others

Fix Power Automate Move File Fails with Source Object Error

Phi Hung Vo Oct 1, 2026 869 views

Question details

The user's Power Automate flow fails when attempting to move a SharePoint file, returning an error that it cannot verify the source object.

How to Fix Power Automate Move File Fails with Source Object Error

Product: Power Automate
Device & OS: not provided
Scenario: Moving a SharePoint file automatically when its status is changed to Completed.
Observed behavior: The flow fails with a source object verification error, typically because the file ID is used instead of the Identifier property in the move action.

Before you start

Verify that your Microsoft account connection in Power Automate has the necessary Read permissions for the source SharePoint folder and Write permissions for the destination folder before editing your flow.

Solution 1Recommended

Use the File Identifier Property in the Move File Action

Resolve the source object verification error by mapping the correct Identifier dynamic content rather than the standard ID.

In Power Automate, the 'ID' is simply an integer tracking the item's row in SharePoint, while the 'Identifier' is a specialized encoded string required for file operations. Supplying the ID where an Identifier is expected is the most common cause of the source object error.

Open the Move File Action

Clear the Incorrect Mapping

Click on the 'File to move' field and delete the existing 'ID' variable if it is currently placed there.

Select the Identifier Property

Click inside the field to open the dynamic content menu. Under the 'When an item or a file is modified' trigger section, click 'See more', and select the 'Identifier' property.

Save and Test

Click 'Save' at the bottom or top right of the screen, then run a test by modifying a file in SharePoint to ensure the flow triggers and completes successfully.

Use the File Identifier Property in the Move File Action

Correct Property Mapping: Using the 'Identifier' instead of 'ID' allows Power Automate to accurately locate and verify the source SharePoint file for relocation.

Solution 2

Add a Get File Properties Action to Retrieve the Identifier

Use this workaround to pull the necessary file identifier if it is not readily available from your initial trigger's dynamic content.

Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While Power Automate handles complex SharePoint workflows, you need a reliable office suite to create, edit, and manage those documents. WPS Office provides a lightweight, free alternative to Microsoft Office with a highly familiar user interface, seamless migration, and excellent format compatibility.

1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
3. Open and Edit Files: Launch WPS Office to instantly open, edit, and save your existing Office documents with zero compatibility issues.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Easily edit and save files locally before uploading them to your automated SharePoint workflows.Lightweight design that runs smoothly on almost any device without consuming massive system resources.Includes built-in PDF editing tools for comprehensive document management.

microsoft office alternative - wps office

Frequently Asked Questions

What is the difference between File ID and File Identifier in Power Automate?

The File ID is a simple integer representing the item's row number in a SharePoint list or library. The File Identifier is an encoded string that Power Automate uses behind the scenes to securely locate and verify the specific file object across file manipulation actions like move, copy, or delete.

Why does my flow fail with 'Access Denied' when moving a SharePoint file?

This typically occurs because the user account used to authenticate the SharePoint connection in Power Automate lacks the necessary permissions. It must have Read permissions for the source library and Write permissions for the destination folder.

Can I move a file to a completely different SharePoint site using Power Automate?

Yes, you can move files between different SharePoint sites. Ensure that your 'Move file' action is configured with the correct Destination Site Address from the dropdown, and that your account connection has adequate permissions for both the source and destination sites.

Office Quick Solutions