SharePoint Document Issues

Fix Power Automate Overwriting SharePoint Timestamps

Maira Mehtab Sep 27, 2026 869 views

Question details

A Power Automate flow is updating or overwriting earlier timestamps on existing SharePoint items instead of modifying only the specific row that triggered the flow.

Product: Power Automate
Device & OS: not provided
Scenario: Automating SharePoint list or document library updates based on a specific row's status changes.
Observed behavior: Earlier timestamps on multiple SharePoint rows are unexpectedly overwritten by the flow during a targeted update operation.

Before you start

Pause the affected Power Automate flow immediately to prevent further unintended timestamp overwrites on your SharePoint lists or document libraries while you troubleshoot the configuration.

Solution 1Recommended

Restrict the Update Scope to the Specific Row

Modify the Power Automate flow so its lookup or update action targets only the specific row whose status triggered the change, preventing bulk overwrites.

This issue typically occurs when a flow's lookup or update action targets multiple rows instead of strictly isolating the single row that needs updating.

Review Trigger Conditions

Open your flow in Power Automate and verify that the initial trigger accurately captures the unique identifier (ID) of the specific SharePoint row.

Check Lookup Criteria

Inspect any "Get items" or lookup actions in your workflow. Ensure they are filtering results via an OData filter query to fetch only the exact row needed, rather than pulling multiple rows.

Correct the Update Action

Click on the "Update item" or "Update file properties" action and ensure it references the specific row's ID from the trigger output. Avoid using arrays that loop through and overwrite all fetched rows.

Check Apply to each loops: If your update action is sitting inside an "Apply to each" loop unexpectedly, it is a strong indicator that a previous step is returning an array of multiple items instead of a single object.

Solution 2

Escalate to the Power Platform Community

If adjusting the flow scope does not resolve the timestamp overwrite issue, posting your specific workflow configuration to the dedicated Microsoft community is the best way to get expert assistance.

Free Microsoft Office alternative

Looking for a Simpler Way to Manage Documents? Try WPS Office

If complex SharePoint and Power Automate workflows are causing unexpected issues and consuming your time, consider WPS Office for a streamlined, reliable document management experience. It is fully compatible with Microsoft Office formats and provides a familiar, lightweight interface without the steep learning curve of intricate automated triggers.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the suite on your device.
3. Open Your Office Files: Drag and drop your existing Microsoft Office documents into WPS Office to continue working seamlessly without formatting loss.

Free, lightweight, and incredibly fast to install and launchFully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx)Familiar user interface ensuring a seamless migration with zero learning curveBuilt-in PDF editing, cloud syncing, and easy document sharing without complex automation setups

Frequently Asked Questions

Why is Power Automate updating all my SharePoint list items at once?

This usually happens if your "Update item" action is placed inside an "Apply to each" loop that iterates over multiple items without a strict unique ID filter. This causes the flow to apply the timestamp and changes to every item the previous step fetched.

How do I prevent modified dates from changing in SharePoint when using Power Automate?

Standard Power Automate update actions will always trigger a new modified date timestamp. To bypass this and preserve the original timestamp, you must use the "Send an HTTP request to SharePoint" action invoking the `ValidateUpdateListItem` method instead of the standard update action.

Where is the best place to ask advanced Power Automate configuration questions?

Advanced flow logic and configuration issues should be posted in the Microsoft Power Platform Community or Microsoft Q&A. General Microsoft Office consumer forums usually do not provide the in-depth support required for intricate Power Automate troubleshooting.

Document & File Issues