Unanswered

CDS - Relate record in PowerAutomate doesn't work anymore: api/data/v9.1/ instead of api/data/v9.0/

(0) Share

Report

Posted on by openclue

In flow, I create one entity and then try to associate it with another using "Relate records".
I have been receiving the following error for some time:

OData id of the created entity:

https://orgf36dadf6.crm4.dynamics.com/api/data/v9.1/crea2_dekrets(7aa46f40-da83-ea11-a811-000d3aba3562)

Error I receive:

"body": {
 "error": {
 "code": "0x0",
 "message": "The URI 'https://orgf36dadf6.crm4.dynamics.com/api/data/v9.1/crea2_dekrets(75f5b3e4-5a83-ea11-a811-000d3aba3562)' is not valid because it is not based on 'https://orgf36dadf6.crm4.dynamics.com/api/data/v9.0/'.",
 "innererror": {
 "message": "The URI 'https://orgf36dadf6.crm4.dynamics.com/api/data/v9.1/crea2_dekrets(75f5b3e4-5a83-ea11-a811-000d3aba3562)' is not valid because it is not based on 'https://orgf36dadf6.crm4.dynamics.com/api/data/v9.0/'.",
 "type": "Microsoft.OData.ODataException",
 "stacktrace": " at Microsoft.OData.UriParser.UriPathParser.ParsePathIntoSegments(Uri fullUri, Uri serviceBaseUri)\r\n at Microsoft.OData.UriParser.ODataUriParser.ParsePathImplementation()\r\n at Microsoft.OData.UriParser.ODataUriParser.Initialize()\r\n at Microsoft.Crm.Extensibility.OData.CrmEdmEntityReference.CreateCrmEdmEntityReference(Uri link, IEdmModel edmModel, CrmODataExecutionContext context, EntitySetSegment& entitySetSegment)\r\n at Microsoft.Crm.Extensibility.OData.EntityController.UpdateNavigationRefInternal(String entityName, String key, String navigation, Uri link)\r\n at Microsoft.Crm.Extensibility.OData.EntityController.PostNavigationRefImplementation(String entityName, String key, String navigation, Uri link)\r\n at Microsoft.Crm.Extensibility.OData.EntityController.<>c__DisplayClass20_0.<PostNavigationRef>b__0()\r\n at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties)\r\n at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func)\r\n at lambda_method(Closure , Object , Object[] )\r\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)\r\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()"
 }
 }
 }

CDS creates an entity based on api version 9.1 and expects version 9.0 when trying to relate ? How can I solve that issue.

Deos anyone have similar problems ?

Best regards

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

openclue 35 on at

Like (0)

Report

As far as I checked it, "Get record" or "Update Record" returns @odata.id with v9.1 version of API but "Relate records" require v9.0 version....

Was there any update on CDS (curren environment)? If so, why not all actions return or require the same api version?

Is there any way (simplier than replace string) to get @odata.id with specific api version ?

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @openclue,
Which connector are you using? if you're not using the "Common Data Service (current environment)", it is recommended to do so. The connector will be available if you create your Flow via a solution in Maker portal.
Hope this helps!

Was this reply helpful? Yes No
openclue 35 on at

Like (1)

Report

Hi @EricRegnier

Yes, I'm using CDS CE - it is the only one with "Relate records" action as far as I know.

As I wrote, this action requires v9.0 but "Create record" and "Get Record" returns @odata.id in v9.1
I can correct it via string replace or I can generate manually @odata.id but it does not look like a preffered way to go. Am I wrong ?

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

From what I know, that Connector is deprecated hence might be why you are getting errors. Don't think Microsoft is maintaining it anymore. You can relate records with the update Actions. What records are you trying to relate?

Was this reply helpful? Yes No
Florian Zimmer 11 on at

Like (1)

Report

Hi @openclue,

I´ve recognised the same Bug yesterday as well and also came to the same conclusion that /v9.1/ is the issue.
I really don´t know how something like this can happen. Lately, there have been more and more unacceptable Bugs. One must really question whether Microsoft has a solid Product Management approach in place - something they pressure us consultants with by evangelizing a managed Azure Dev Ops deployment process (yet to be seen how this one will work out though). Unfortunately, there is no quick and easy fix to this Bug in my opinion. I´ve also applied String replacements as an emergency solution to go on with testing etc.
I guess I will open a Microsoft Support Case via one of our clients. If I will hear something, I will post it here. However, experience tells that it might take a bit until something happens.

Greetings from Germany!

Was this reply helpful? Yes No