OdataID expecting V9.2 and getting V9.1

(2) Share

Report

Posted on by Gyllentid

894

Hello,

This is an issue I have not encountered before. I am using the action Update Row (Dataverse) and it throws the error

... InnerException : Microsoft.Crm.CrmException: AbsoluteUri - https://xxxx.crm4.dynamics.com/api/data/v9.1/accounts(960b1668-a208-f011-bae4-000d3ab700d6) should contain ServiceRouteUri - https://xxxx.crm4.dynamics.com/api/data/v9.2
at Microsoft.Crm.CrmException.Assert(Boolean condition, String message) ...

I have tried using the replace function for this like this guide suggests "How to Fix Relationship Errors in Power Automate’s ‘Update Row’ Action for Dataverse" but it doesn't help.

I am wondering what is causing this as I have worked with these type of actions and updates for several years and not had the issue.

Kindly thanks

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (0)

Report

Hi @Gyllentid

I believe you are saying in the Power Automate you are using Update Row and since it automatically points to its local DataVerse... you cannot change that.

And... whats happening to you, to me, is definitely a bug, as that means the specific action requires the latest Uri to the D365/Dataverse API.

Weird. I am going to look into this I haven't seen this before.

Was this reply helpful? Yes No
tuhler 14 on at

Like (0)

Report

I came here because I am experiencing the exact issue as the OP. The flow works fine in our production environment. I moved it to our sandbox environment to change some filters and cannot update the rows due to the expecting v9.2 issue.

EDIT

Moments After I created this message I found a solution:

https://community.powerplatform.com/forums/thread/details/?threadid=9969fd36-04bb-ef11-b8e8-7c1e527e6133

Instead of using the odata ID, I used the plural entity name(entity GUID)

In my case it is processstages(guid) and it worked

Was this reply helpful? Yes No