Unanswered

Error creating row: "URL was not parsed due to an ODataUnrecognizedPathException."

(1) Share

Report

Posted on by mrpowergage

234

I am intending to add a row to my custom entity. This simple test is failing with "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL."

how might I solve this? thanks

Categories:

Building flows

I have the same question (0)

All responses (31)

Answers (1)

Verified answer

Expiscornovus 33,183 Most Valuable Professional on at

Like (20)

Report

Hi @mrpowergage,

It looks like your Project field is a lookup to a row from another table. That requires a different formatting to be able to link to it.

You probably need to convert it to projects(guid) or something similar. It needs to be the plural version of the entity schemaname.

Linn Zaw Win has written a nice blogpost about this:
https://linnzawwin.blogspot.com/2019/11/power-automate-how-to-set-lookup-field.html

Below is another example.

In my setup my lookup field was called Account and linked to the Account entity (plural accounts).

Was this reply helpful? Yes No
mrpowergage 234 on at

Like (3)

Report

perfect, thank you!

And how have microsoft released this as production ready in this state??

Was this reply helpful? Yes No
Expiscornovus 33,183 Most Valuable Professional on at

Like (2)

Report

Hi @mrpowergage,

It is OData standard notation. Although it is a bit more difficult to find, they do have documentation about this 😅:

https://docs.microsoft.com/en-us/power-automate/dataverse/relationships#modify-or-add-rows-directly-with-relationships

When you want to create or modify a relationship, use standard OData notation. For example, while creating an account row, you should set the Primary contact column to the OData ID of a contact row like this: contacts(c96be312-4ac1-4358-99b6-1e14e2957b15).

Was this reply helpful? Yes No
Sky_God 12 on at

Like (4)

Report

I had the same issue with "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL." when trying to write a D365 OpportunityProduct line.

I saw that the errors in PowerAutomate (when inspecting the inbound and outbound values of the action) has @OData bind in the URL path (see your Power Automate Action's runtime/error JSON fragment of what it is trying to do). This is how this issue came around and gave me a clue that this special format of adding EntityReferences was needed rather than dropping the fields in directly (as normally works).

My Flow was just adding the field names in the boxes and expecting PowerAutomate should be able to see that it is a reference field and bind it accordingly but no, it would seem extra work is needed.

For reference, I added the same steps in LogicApps and it could deal with the binding no issue and knew how to bind a lookup.

Erroring Flow vs working LogicApp.

And the values which surface upon run are the same...

I have wasted hours on this issue and I think it could have been clearer (as well as the error message). I also thought the point of PowerAutomate was that developer things were not needed, it was available to all.

I wonder if the development team missed checking if the field was a reference field from the outset and can't fix it retrospectively for fear of breaking existing flows.

So my solution in PowerAutomate was to add the three required fields as follows:

Of course you can drop the field value in the field rather than the raw GUID text, this also works...
e.g.

Use the ...(Value) field to get to the GUID.
(Which has _ and value in the name suggesting it is a lookup/reference field
)
If you want to see the plural name of D365 entities to use in your flows
https://yourinstancename.crmX.dynamics.com/api/data/v9.1
(change the base path and version v9.1 accordingly but CRM online should be v9.1 version and above).

You may get use from this also, to find out more detail about the entities in your system:
https://yourinstancename.crmX.dynamics.com/api/data/v9.1/EntityDefinitions

With the entity definition looked up I take the GUID (MetadataID) from the entity definition in I'm interested and put it into the following between the () as per this example.
https://yourinstancename .crmX.dynamics.com/api/data/v9.1/EntityDefinitions(5f2e7ae7-d327-49b5-a343-61d48f1bcd28)?$expand=Attributes so I can find out more about the fields for the entity. For this expand the Attributes node of the returned JSON and you will see the fields and their type.

Was this reply helpful? Yes No
Gus 136 on at

Like (1)

Report

By the way.. Unlike contacts() or accounts() The plurals for orders is salesorders() and for owner is systemusers().

Was this reply helpful? Yes No
mrpowergage 234 on at

Like (0)

Report

note to self for next time:

Need to go and get the scheme from the column, rather than just use the lowercase plural of the field name.

eg
'xx_memberships' (not 'clients' or 'memberships')

Was this reply helpful? Yes No
testasdfasfsafa 309 on at

Like (5)

Report

This is absolutely garbage... I can't even believe that Microsoft took something simple (like the old Dynamics 365 activties) and turned this lookup process into something that takes 10x longer to build and more complex. THIS IS NOT workflow for "everyone"....

To make matters worse, they no longer easily expose the "label" lookup values, in the field picker... Perfect example of going backwards. Very unhappy...

Was this reply helpful? Yes No
dalalnav 21 on at

Like (2)

Report

Use the logical name of the table , and add a s after the logical name , this worked .

Was this reply helpful? Yes No
testasdfasfsafa 309 on at

Like (10)

Report

Actually, the best and most accurate way to do this, is to use the table "set name". I still don't know why MS doesn't automatically retrieve the set name and let user simply input the GUID in Flow to keep things simple.

Was this reply helpful? Yes No
GJones 16 on at

Like (0)

Report

If the error message contained the field name that has the issue would be a huge help.

Was this reply helpful? Yes No