SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

Like (1) Share

Report

Posted on 9 May 2025 15:36:14 by CU08052029-0

Hi all,

I'm running into a frustrating issue when using Power Automate and the SharePoint REST API to update file metadata in a document library.

Setup:

Library

Versioning: enabled

Permissions: Flow runs with a user who has Edit or higher permissions

Scenario: Flow is triggered on file modified, or runs manually

The Problem:

REST calls (ListItemAllFields, validateUpdateListItem) all return HTTP 200 OK

BUT: Metadata is not actually updated for any existing files

The same logic works perfectly for newly created files

What I've Already Tried:

Used ListItemAllFields with correct __metadata.type

Verified internal column names and permissions

Used both bNewDocumentUpdate: true and false

Files are manually checked out and it triggers the power automate flow

Flow uses correct FormDigestValue from _api/contextinfo

No errors or throttling — flows run successfully but metadata stays the same

Manually edited metadata in SharePoint UI to "unstick" the item — didn’t help

What's Working:

The exact same flow does successfully update new files

Issue only occurs on files that already existed in the library

What I Need Help With:

Is there a known reason why REST metadata updates are ignored for existing files in some libraries?

Could this be related to content types, required fields, or versioning history?

Is there a backend limitation where old list items lose updateability via REST?

I’ve exhausted the typical troubleshooting paths and would really appreciate any insights, workarounds, or confirmations if others have hit this limitation.

Thanks in advance!

Categories:

Business Process Flows

I have the same question (0)

All responses (6)

Answers (0)

CU08052029-0 6 on 12 May 2025 at 12:29:08

Like (0)

Report

SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

@stampcoin I did the exact same thin g you mentioned in the post earlier - it works for any new document I create and update but for old documents it works for the new test col i created but not for the old columns like status and opi approval status ( both are single text column)
and the values are populated by another power automate flow.

Was this reply helpful? Yes No
stampcoin 4,168 Super User 2025 Season 2 on 09 May 2025 at 21:21:03

Like (0)

Report
SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

@CU08052029-0,

1.Quick test: patch a PDF or a throw-away text file in the same library—does the update stick? If yes, it’s the promotion engine.
Work-arounds

change the flow to overwrite the XML as well: add the same columns as document properties with Office JS or Graph /drive/items/{id}/workbook/….
• Strip the XML once (Open - File - Info - Check for Issues → Inspect Document → Remove All “Custom XML Data”) and re-upload, or automate it with ScriptLab/PnP.PowerShell. Users report that removing the XML stops the rollback.

https://techcommunity.microsoft.com/discussions/sharepoint_general/my-excel-document-properties-keep-reverting-when-i-save-the-file/2826913

https://techcommunity.microsoft.com/discussions/sharepoint_general/unable-to-save-managed-metadata-in-sharepoint-document-library/3968774?utm_source=chatgpt.com

2. In the same Outputs look for "LockId": or "CheckedOutByUserId":.
• Check the file out as the service account before the update (POST…/checkout) then check it back in.
• Or call …/ValidateUpdateListItem?@CheckInComment=''&@bNewDocumentUpdate=true.

3. GET …/GetComplianceTag; if IsTagPolicyHold=true your only option is to relabel or temporarily unlock the record (requires Compliance admin).

4. Always send If-Match: * and X-HTTP-Method: MERGE (or use the Graph /fields PATCH, which does that for you).

5. Add bNewDocumentUpdate:true in the body to prevents extra versions even when versioning is on.

POST _api/web/GetFileByServerRelativePath(decodedurl='/sites/Docs/Lib/old.docx')/ListItemAllFields/ValidateUpdateListItem Accept: application/json;odata=nometadata Content-Type: application/json;odata=verbose If-Match: "*" X-RequestDigest: @{body('Get_contextinfo')?['d']['GetContextWebInformation']['FormDigestValue']} { "formValues":[ {"FieldName":"Project","FieldValue":"Contoso"}, {"FieldName":"Status","FieldValue":"Approved"} ], "bNewDocumentUpdate": true }

that's all I found.. good luck.

Was this reply helpful? Yes No
CU08052029-0 6 on 09 May 2025 at 19:02:34

Like (0)

Report

SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

@David MA

Flow Process :

user checks out the file manually - flow gets triggered - discards the check out- check out again- update the columns - checks in

Send HHTP request is updating the "TestCol" column but its not updating the other two columns.

I have exhausted all my resources. Any help is appreciated.

weird part is it works for any new file I create

Screenshot 2025-0...

Was this reply helpful? Yes No
CU08052029-0 6 on 09 May 2025 at 18:55:59

Like (0)

Report

SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

@stampcoin I checked there is no HasException True for any columns

Was this reply helpful? Yes No
stampcoin 4,168 Super User 2025 Season 2 on 09 May 2025 at 18:12:35

Like (0)

Report

SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

@CU08052029-0 Hi,

You said you flow works for the new files but not for old ones.

Try to pick a failing run open Outputs → body/results: for every field you tried to set if you see "HasException":true,"ErrorMessage":"Field xxx does not exist on this type"

Push the column down with “Add from existing site columns” + Update all content types or run Set-PnPListItem -ContentType.

Was this reply helpful? Yes No
David_MA 12,032 Super User 2025 Season 2 on 09 May 2025 at 16:43:53

Like (0)

Report

SharePoint REST API 200 OK but Metadata Not Updating via Power Automate for Existing Files

Please share the configuration of the HTTP request you are trying to use so we have a better understanding of what you are attempting. Without actually being able to see how it is configured, it is hard to say what you may be doing wrong.

Was this reply helpful? Yes No

Community site session details