Power Platform Community Forum Thread Details

I’m promoting a solution from a Development environment to Production. The solution contains a cloud flow that updates a SharePoint list item.

But I ran into the following error when turning on the flow in Prod:

Turn on failed. Flow client error returned with status code "BadRequest" and details 
{"error":{"code":"InvalidOpenApiFlow","message":
"Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 
'The API operation does not contain a definition for parameter 'item/Division_x0023_1ApprovedBy/Claims'.'" }}

On the Prod's end:

In the SharePoint Update item action (see pic, operationId: PatchItem), the “Advanced parameters” section displays a duplicated/ghost parameter path (this does not appear in the Dev's end). Instead of targeting the proper People field once, I see an auto-generated key like:

Expected: Division #1 Approved By Claims (maps to item/Division_x0023_1ApprovedBy/Claims)
What appears: Item.item/Division_x0023_1ApprovedBy.item/Division_x0023_1ApprovedBy/Claims

Because of that extra nested item.item/... key, the connector thinks I’m sending a parameter it doesn’t recognize, and the flow can’t be enabled.

Workaround that unblocks me:

Open the Update item action on Dev's end
Re-select Site Address (environment variable), then List Name (environment variable)
Clear and remap parameter
Update solution on Prod's end

After doing this, the flow turns on and runs.

Questions:

Is this a known designer caching issue with the SharePoint connector’s advanced parameters after solution import?
Besides the “Clear all + re-select site/list” trick, is there a supported way to force a schema refresh during import so the ghost parameter never appears?

Any insights on the root cause and a cleaner long-term fix would be appreciated!

Categories:

Building flows

Hi @FA-22090824-0

Yes, what can happen is if you make changes to external pieces of the flow (tables, connectors, changing columns etc), what can happen is it will cache any field that already had a value entered into it.

So you will see these weird item/asflasdflasdf things when in fact they do not exist.

Jus clear the values from them. Save and it will be fine. However a couple of other thoughts

1) did you make changes in Dev to the Tables that, within the action, are now having this issue?

2) verify in Dev what it says in the flow action

3) did you do an upgrade or update when you imported?

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey