Status 400 - "The passed-in field could not be found"

[ericsumerfield]

We have a site that is using PowerAutomate to run a workflow to request and capture (save) approval status (for training requests) back to a SharePoint Task List.  This is the second workflow doing something similar, and the first is working as expected (for PTO/time Off Requests), however, this one keeps erroring out with the following output.

"status": 400,

"message": "The passed-in field \"Status_x0020_of_x0020_Request\" could not be found\r\nclientRequestId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx\r\nserviceRequestId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

the power automate flow is running using a service account with full access to the SharePoint site, so we do not think its a permissions issue, if we use the update SharePoint item and manually designate each of the required fields on the task list it works, but trying to dynamically call the list and only push the value to the single field does not seem to work no matter what we try.

I read some articles that said to delete the step and re-create to resolve, but that did not work, we even tried re-creating the entire flow, with no improvement.  Any suggestions are welcome as we are kinda at an impasse here.

[Pavan_Mani_Deep · Accepted solution]

Hi @ericsumerfield ,

When you were using the field name from SharePoint, make sure you have used the correct field name.

If you keep both the actions – ‘Get items’ and ‘List rows’ without filters and run the flow, they’ll give you a JSON will all the columns. And since they also use the internal names, you just have to find the column in the output.

Refer to

https://tomriha.com/why-does-power-automate-filter-query-fail-column-does-not-exist/

https://www.youtube.com/watch?v=OMCk9UnhlJU

If I have answered your question, please mark your post as Solved.

If you like my response or got a direction forward to proceed, please give it a Thumbs Up. Appreciate your Kudos. You can accept more than one post as a solution.

If you were still facing any issue or challenge, please do let me know so that I can try to check for you. Happy to help you further.

Blog:https://ecellorscrm.com

Cheers,

PMDY

[ericsumerfield]

The field meta name was different than the visible label for some reason, viewing the field in advanced edit mode gave me the correct technical name to use.  Much appreciated.