The form fields are not updating

(2) Share

Report

Posted on by CU09010512-1

Hallo,

I've an approval automation flow where after approval action the form field s are supposed to be updated using the HTTP action.However, the flow is only updating the FormStatus field to complete. and not updating the other fields.The same flow was working fine in test environment, but this issue is occurring in the production site,I've also verified the internal column names, so that doesn't seem to be the problem.

Thanks!

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Haque 3,197 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU09010512-1,

Can you please check the response body from the HTTP aciton - it often contains error messages for the fields that failed.

As it was working in dev but giving trouble in prod - we need to check multiple things to make sure two ecosystems are same at least the list where form data is saved plus the flow.

1. If can remember - if any column is deleted and recreated or newly created in prod then there is a question of column internal names vs display name. I would suggest (to double check) - compare each column with the dev and prod list. Please bring them in notepad/notepad++ to see the difference.

2. The account running the HTTP request must have edit rights on all the fields. If you have expereinced or not - sometimes in production, the flow runs under a service account with limited field permissions.

3. HTTP request body - let's make sure DateTime fields in ISO 8601 (yyyy-MM-ddTHH:mm:ssZ). Choice fields must match the exact option value, and person fields must be passed as {"Email":"user@domain.com"}. SharePoint REST API is bit picky and choosy - it needs decorated and formatted data for integrity.

4. Low but sometimes hijacks our brain - ff your list uses multiple content types, the production list may have a different default content type. Fields not present in that content type won’t update.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

Valantis 5,228 on at

Like (3)

Report
Copy link

Link copied!

Hi @CU09010512-1,

The flow is not throwing an error because validateUpdateListItem returns 200 OK even when individual fields fail. That is why FormStatus updates and the rest do not. The failures are “silent”.

Try this:

   1.   Add a Parse JSON on the HTTP response body right after the action. It gives you an ErrorCode and ErrorMessage per field so you know exactly what is being rejected in production rather than guessing.
   2.   Compare column internal names between dev and prod side by side. If a column was deleted and recreated in production it gets a new internal name even if the display name looks identical.
   3.   People fields must use this format for the validateUpdateListItem endpoint specifically:
[{‘Key’:‘i:0#.f|membership|user@yourdomain.com’}]
   4.   Date fields must be formatted as yyyy-MM-ddTHH:mm:ssZ.
   5.   Confirm the account running the flow in production has edit rights on every field, not just the list.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups  @Valantis.

📝 https://valantisond365.com/

Was this reply helpful? Yes No
Valantis 5,228 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU09010512-1,

Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

Thanks and have a great day!

Was this reply helpful? Yes No