Dataverse Connector > "Update a row" is broken with "Error fetching manifest":

(3) Share

Report

Posted on by DO-29090853-0

Dataverse Connector > "Update a row" is broken and trying to use this connector shoots this message while saving based on "Error fetching manifest":

Action failed to serialize. Failed Action id: 'Update_a_row'. Inner error: 'The API operation 'updateonlyrecord' could not be found in API 'commondataserviceforapps'.'

I relogged, reconnected, reopened a new flow (also in a new tenant and environment), and the issue remains persistent. Who else has seen this?

Regards

Categories:

Using connectors

I have the same question (7)

All responses (5)

Answers (0)

Sort by

Michael E. Gernaey 53,969 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @DO-29090853-0

I have read from people even on LinkedIn that it is currently broken. The people were from other regions of the world than me, but others also have noted it.

Can I ask what region of the world you are in?

1 people found this reply helpful.

Was this reply helpful? Yes No
CoreySutton 18 on at

Like (1)

Report
Copy link

Link copied!

I'm having this issue with the same "Update a Row" action, and can replicate the issue with other Dataverse actions.

Does anyone have new information about this issue?

1 people found this reply helpful.

Was this reply helpful? Yes No
Flury 62 on at

Like (1)

Report
Copy link

Link copied!

I'm encountering the same issue on all my environments, the actions "Update a row" are currently all displayed as "Request failed with status code 404". This means a ton of our productive flows are now broken. I noticed, that "Upsert a row" is still working and so for the absolutely business-critical flows I'm thinking about using this connector instead. However since the "Update" action simply doesn't exist anymore I have no way of knowing what values or expressions were used to fill the attribute fields.

1 people found this reply helpful.

Was this reply helpful? Yes No
DO-29090853-0 11 on at

Like (0)

Report
Copy link

Link copied!

It's a peculiar disfunction - I used upsert for the current flow as s workaround, and might never use "Update a row" again as i even noticed that the desktop flow entirely do not also have the "Update a row".

What is peculiar is that i have another tenant in region (Kenya) where the "Update a row" works, but it will not work in the tenant in region Switzerland.

Very painful for process critical flows - if you must not touch a flow, i suggest you don't touch until this is resolved. My troubles begun when i tried to save a flow that I had edited. Premium tears!

Was this reply helpful? Yes No
Suggested answer

CU30091241-0 8 on at

Like (1)

Report
Copy link

Link copied!
I had the same problem. I followed the following steps and my issue is resolved now.

Opended the Dataverse conenection in the list of connections

Clicked on the Switch Account and re-authenticated with the same account

Opended the flow again and the issue was resolved.

I'm not sure if the above steps resolved the issue or it is resolved by Microsoft.

Was this reply helpful? Yes No