Flow run problem: Update a record, CDS

[Anonymous]

Anyone know what this error is?  The flow runs great in one sandbox environment (dev), but fails in another (uat).

Because it's CDS, I had to create it in a solution.  I published that solution and I've tried running it while in the solution and by doing 'save as' to pull it out of the solution.  It fails whether I run a test from the edit page or if I trigger it from Dynamics.

[ManishJain · Accepted solution]

Hi @Anonymous ,

Could you share complete error message and screenshot of what you are trying to accomplish. 

Thanks

[v-alzhan-msft · Accepted solution]

Hi @Anonymous ,

Could you please share a full screenshot of the configuration of your flow?

Does the record that you want to updated exists in the Current environment? if yes, does the record identifier correct?

Best regards,

Alice   

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Here is the latest version of the complete flow.  It's short:

And broken down to details:

I had "Team Name" in the update:

and received this error:

Changing to "Team", with the guid, worked.

....but not when I imported the flow, in a solution, to the next environment!

In the next (sandbox) environment, I can't turn it on unless it's published and I can't publish it, either, so I have to pull it out of the solution with a 'save as'.  Then, the run fails:

There are so many quid pro quos with using flows in Automate.  I started with Dynamics connectors, then found that's being deprecated.  I switched to "CDS", then I couldn't choose "when a record is created, updated or deleted", unless I went to "CDS (current environment)".  But this connector is hidden in Automate, so flow builders have to remember to specifically look for it when inserting each new step, because "Update record" is not the same between the two.  With the latter, the "owner (type)" does not need to be updated.

This is a very short - and should be easy - flow.  

[Anonymous]

This is all worked out now.  Flows can be migrated (deployed) without a solution:  https://carldesouza.com/deploying-microsoft-power-automate-flows-from-one-environment-to-another/