If you’re building a Flow that uses Dataverse connectors, you might need to change the metadata and it doesn’t reflect in the Flow and the issue continues to occur even after publishing the changes.
Let’s suppose you are using Add a row action to create a new record in Dataverse/Dynamics CRM –
- And when the Flow runs, the record is not created because you end up having this error where the length of the field enough to store the data.
- Now, in order to fix this –
- Now, even after I changes the above length – the error still occurs.
Let’s look at the issue –
- The issue is, at the time of creating the step, Flow stores the metadata with an ID and when you change the metadata in the backend, it is not reflected back on the Flow.
Here’s what you need to do in order to fix this –
- You need to delete the step and re-do the step in your Flow
- And now, it will have the latest metadata with the new Metadata ID to it –
Hope this helps!
Here are some Power Automate posts you want to check out –
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform\
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate