Field is no longer present in the operation schema (Flow un-editable)

(1) Share

Report

Posted on by Warren_Gibbs

I’ve had a Power Automate flow working for quite some time.

A requirement change resulted in me changing the data type for five columns in SharePoint.

The problem I have now is that my Power Automate cannot be edited as saving the flow throws the below error in the Update Item function for two of the five fields I changed.

I have tried creating a new connection for the Update Item function in the hope it would refresh the schema I have also tried removing and adding the Update Item function again.

I am almost at the point of deciding to recreate my flow from scratch – but surely this cannot be the solution to fix this?!?!?

Thanks

Categories:

Building flows

I have the same question (0)

All responses (16)

Answers (1)

eric-cheng 5,171 on at

Like (3)

Report

Hi @Warren_Gibbs ,

Can you try, deleting it, saving it and then adding it back in

Did a bit of searching online and there isn't an obvious solution outside of reverting the changes made to the SP list or recreating the flow.

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

Was this reply helpful? Yes No
Verified answer

Warren_Gibbs 65 on at

Like (3)

Report

Thanks @eric-cheng. In the end I needed to recreate the Flow from scratch.

Hoping that this will be addressed by Microsoft at some point in the future!

Let's just say 'lesson learnt'

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

All: I found that when I changed answer types in my Microsoft Form that is linked to my Power Automate Flow, It threw this error. So if you have a linked process and edit it, it could cause Power Automate to throw this error. Hope this helps,

Was this reply helpful? Yes No
ohermans1 11 on at

Like (3)

Report

For people trying to fix this - the current work around is to copy of past the specific action then delete the original one, this usually fixes it.
Alternatively, just recreate the issue action and copy and paste across the information.

Not the best solutions, but they work. Would be great if the underlying issue could be fixed.

Was this reply helpful? Yes No
CW 1,044 on at

Like (1)

Report

Don't count on it!!

Was this reply helpful? Yes No
CW 1,044 on at

Like (1)

Report

Nope, that just returns back what's in the clipboard.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (2)

Report

In my case seems like the it change the order of the field in share point. So he can't find the right spot to get the data.
Hope this could help.

Was this reply helpful? Yes No
CW 1,044 on at

Like (1)

Report

That would make sense.

Was this reply helpful? Yes No
ACACAC2024 2 on at

Like (1)

Report

For me, the reason why I got this message was because I had changed the name of a Column Header, and it no longer matched what the flow thought was the header.

Was this reply helpful? Yes No
Gilmour 362 on at

Like (1)

Report

After you delete the value in he field, make sure you don't leave any characters, spaces, paragraph lines. Once I did that, my flow saved and works again.

Was this reply helpful? Yes No