Dynamics 365 customer engagement - Web api - url ... is not valid because it is not based on.

(0) Share

Report

Posted on by Kjeld Poulsen

180

My angular app, was suddenly giving strange errors when i used web api put to assign a lookup value on the entity using web api:

The URI 'MYTENANT.crm.dynamics.com/.../kipon_staffs(d3dd9b93-1b0b-e811-80ee-00505694498c)' is not valid because it is not based on 'https://MYTENANT.crm.dynamics.com/api/data/v8.2/'.

The reason turned out to be very simple. I was using the v9.0 endpoint in the url, but due to use of generic libraries, the odata link in the body of the request, was still pointing to the 8.2 endpoint

I know for sure this has been working without any problems, but suddenly it was an issue. The fix was simple. Use the same version in the url as in the @odata.id value.

I have the same question (0)

All responses (5)

Answers (1)

Pedro Cadavez de Fr... on at

Like (0)

Report

Hello Kjeld,

Hope you are well.

Is this something you need help with or was it to share with the community?

Let us know.

Was this reply helpful? Yes No
Verified answer

Kjeld Poulsen 180 on at

Like (1)

Report

just to share with the community. I really like when others are posting valueable searchable findings when developing on top of dynamics 365, so i try do the same.

Was this reply helpful? Yes No
Pedro Cadavez de Fr... on at

Like (0)

Report

Thank you then for your contribution!

Wish you all the success!

Was this reply helpful? Yes No
karenmoen 5 on at

Like (0)

Report

This issue just surfaced with a Flow that I am using against Dynamics 365 CDS. Here is the error I am getting in the Flow:

URI 'dynamicsreadminess.crm.dynamics.com/.../ is not valid because it is not based on dynamicsreadminess.crm.dynamics.com/.../

The Flow has been running fine, but all of of a sudden is throwing this error. I believe that the D365 instance was updated, and that this is causing the problem.

The Flow is erroring out using the "Relate Records" action against CDS. The URL entry within the Relate Records action is "body/@odata.id".

You mention in your solution to use the same version in the URL, as in the @odata.id. Do you know how I may be able to change the version within the Flow? Any guidance is greatly appreciated.

Was this reply helpful? Yes No
Suggested answer

Kjeld Poulsen 180 on at

Like (0)

Report

I haven't work with flow and dynamics web api, so i am not 100% sure how to solve, but basically flow have to make an http request somehow, and in the body of the request you will have a data payload with a odata reference, ex.

request url: yourinstance.crm4.dynamics.com/.../v9.0/somethingdependingonwhatyouaredoing

and in the body of the request you will have som data in json format:

{

'regardingid@odata.id : 'yourinstance.crm4.dynamics.com/.../v9.1/accounts(guid-on-account)'

}

The above example will throw that exception, because the url fired against dynamics 365 is version 9.1, while the version used in an entity ref.

in the payload is version 9.0.

in this article:

dynamicconsultantsgroup.com/.../

I can see the the request url is being setup when creating the flow in the action. I would assume you just have to adjust the url in the action to be the same as the url in the datapayload.

If you have url references in Uri and in Body with Web api version references, they need to be the same.

Was this reply helpful? Yes No