How to Fix Relationship Errors in Power Automate’s ‘Update Row’ Action for Dataverse

When trying to establish a relationship in Dataverse using the “Update Row” action in Power Automate, I encountered the error “Error identified in Payload provided by the user for Entity”. Here’s how I resolved it.

For information about how to create relationships, please refer to:

Managing Dataverse Relationships in Power Automate: Using Row ID and OData ID

I've been asked about how to connect and disconnect Dataverse relationships from Power Automate, so here are my notes.Ta...

Error Occurrence Conditions
Solution
Additional Note 1: Record Creation Date is Irrelevant
Additional Note 2: “Associate Row” Action Works with v9.1
Related Articles

Error Occurrence Conditions

While attempting to establish a relationship between a parent table record and a child table record using the “Update Row” action,

The following error occurred:

Here’s the error message:

Error identified in Payload provided by the user for Entity :”, For more information on this error please follow this help link https://go.microsoft.com/fwlink/?linkid=2195293 —-> InnerException : Microsoft.Crm.CrmException: AbsoluteUri – https://orgc523ee4b.crm7.dynamics.com/api/data/v9.1/cr861_parents(38a04bf0-c608-ed11-82e5-000d3a402e18) should contain ServiceRouteUri – https://orgc523ee4b.crm7.dynamics.com/api/data/v9.2

Solution

The critical part of the error message was this line, indicating that v9.2 is required: AbsoluteUri should contain ServiceRouteUri – https://orgc523ee4b.crm7.dynamics.com/api/data/v9.2

Looking at the obtained OData ID, we can see it’s using ‘v9.1’:

After using the replace function to change v9.1 to v9.2:

The operation was successful:

In conclusion, when establishing relationships using the “Update Row” action, it appears that v9.2 must be used going forward.

Additional Note 1: Record Creation Date is Irrelevant

I thought the OData ID might be v9.1 because the previously created Parent record was old (July 2022), so I created a new record:

When attempting to establish the relationship:

The OData ID was still v9.1 and didn’t work.

This confirms that there’s no correlation between the OData ID version and the record creation date.

Additional Note 2: “Associate Row” Action Works with v9.1

Interestingly, when trying to establish the relationship using the “Associate Row” action:

It worked fine with v9.1:

It would be nice if Microsoft could standardize this behavior across different actions…

Managing Dataverse Relationships in Power Automate: Using Row ID and OData ID

I've been asked about how to connect and disconnect Dataverse relationships from Power Automate, so here are my notes.Ta...

Power Apps Dataverse: How to Fix 'Multiple levels of many-to-one relationship expansion aren't supported' Error

When encountering the "Multiple levels of many-to-one relationship expansion aren't supported" message in a canvas app, ...

Complete Guide to Dataverse Formula Columns: Functions, Operators, and Parent Table References

Since calculated columns are being deprecated, I conducted a detailed investigation into formula columns as their replac...