Unanswered

Dataverse flow not using correct @odata context

(0) Share

Report

Posted on by StewC

116

I'm getting an error in a flow that retrieves the odataID for a row from one Dataverse table (Dockets) to enter into another (Requests). The Update Row operation fails with this error message:

AbsoluteUri - https://orgbbxxxxxx.crm.dynamics.com/api/data/v9.1/msnfp_dockets(52756073-6f7f-ef11-ac21-6045bda6d6ad) should contain ServiceRouteUri - https://orgbbxxxxxx.crm.dynamics.com/api/data/v9.2

Indeed, when I look at the output of the Get Dataverse Row action, it is returning the context string around v9.1

That sounds like I've failed to install an update somewhere. But I've checked all my D365 apps and installed any available updates. What else am I missing? Is there a Power Automate update that I've missed?

thx

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

KT-07052127-0 15 on at

Like (1)

Report

Hi,

I've seen this when I'm trying to relate or connect two records.

You have to use the plural name of the entity on the form.

Was this reply helpful? Yes No
StewC 116 on at

Like (0)

Report

@KT-07052127-0, Thanks! Yes, that works. To make it clear to others: use the plural table name with the Row ID, not the full OData ID, in the parens.

Another solution I came up with (before your reply) is to build a revised OData ID using Compose with a static context string (the 'https://...api/data/v9.2/contacts()') and inserting the row ID. But your solution is safer than using a static string.

thx

Stew

Was this reply helpful? Yes No