Flow fails to publish or turn on

(1) Share

Report

Posted on by PŠ-03101246-0

Hello recently I updated a flow and I get error with this error message. Did anyone meet with this error and where you able to solve the problem?

Flow save failed with code 'MultipleErrorsOccurred' and message 'The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntity' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: {"error":{"code":"XrmApiRequestFailed","message":"Request to XRM API failed with error: 'Message: Parse Json error when deserializing XRM API response payload.\nCode: \nInnerError: '.","extendedData":{"message":"Parse Json error when deserializing XRM API response payload."}}};The dynamic operation request to API 'commondataserviceforapps' operation 'GetMetadataForGetEntity' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: {"error":{"code":"XrmApiRequestFailed","message":"Request to XRM API failed with error: 'Message: Parse Json error when deserializing XRM API response payload.\nCode: \nInnerError: '.","extendedData":{"message":"Parse Json error when deserializing XRM API response payload."}}}'.

This flow is in solution.
This flow doesn't use Parse Json action only Dataverse actions, Compose, Filter array, Office 365 users connection, Office 365 groups connection.
I tried changing the connection on all actions for a fresh one that is in the solution didn't help.
I also tried selecting the table on the action which required for me to add the input field and should update the schema of the actions. Can you help me?

BR regards

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Valantis 6,526 on at

Like (1)

Report
Copy link

Link copied!

Hi @PŠ-03101246-0,

This error means Power Automate can't load the metadata for a Dataverse table in one of your actions. It's not a Parse JSON action issue it's the connector trying to refresh the table schema and failing.

try:

1. Open each Dataverse action and re-select the table from the dropdown even if it looks correct. This forces a metadata refresh.
2. Check if any table was recently modified, renamed, or had a failed solution import. That would break the schema binding.
3. If re-selecting doesn't help, delete the failing Dataverse action and recreate it from scratch.
4. Last resort: export the flow, delete it, reimport. Forces a clean metadata fetch.

If still failing after all this, raise a support ticket with the table logical name.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 3,038 on at

Like (0)

Report
Copy link

Link copied!

The most likely cause is that one Dataverse action contains stale metadata for a table or column that was recently modified, and Power Automate cannot

deserialize the metadata during save validation.

My recommendation would be to focus on any Dataverse action that references a table or column that was recently changed and recreate that action entirely

rather than simply updating its configuration.

Was this reply helpful? Yes No
Valantis 6,526 on at

Like (1)

Report
Copy link

Link copied!

Hi @PŠ-03101246-0,

Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

Thanks and have a great day!

Was this reply helpful? Yes No