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

[mrpowergage]

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

[Expiscornovus · Accepted solution]

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).

[mrpowergage]

perfect, thank you!

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

[Expiscornovus]

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-...

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).

[HortonHouse]

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=Attribut... 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.

[drummer]

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

[mrpowergage]

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')

[testasdfasfsafa]

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...

[dalalnav]

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

[testasdfasfsafa]

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.

[GJones]

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

[Anonymous]

I have never once tried to create any Urls in my Flow, yet I'm being told there's an error in one! What the heck??????????! Also, how am I supposed to find out which field/column is causing the error when the frick'en error message doesn't tell me!?!?!

Sorry, been dealing with this issue for a couple of days now.  😞

[Anonymous]

I've read this response over and over and I'm still not getting it. Are you saying that if you have a lookup column, you must put a "lookup link" into it or you'll get the error?

Also "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)."

I'd really like to know where you saw that "@Odata" reference because none of the 'results' I'm looking at show any Url, or OData reference.

I mean, here's my JSON fragment, and I see no Url, or OData reference.

{
"error": {
"code": "0x80060888",
"message": "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL."
}
}

To Microsoft I say; "WHAT Url?!", "What 'segment' are you talking about?!?!?!"

Nothing I'm seeing on the error screen of my Flow's Run shows anything that's of any help. 😞 

Any help appreciated!

[drummer]

This error if it is what I was referencing is with lookup fields where you need to add the name brackets around the field for it to work. There is also an issue if lookup is null where flow will fail.  Let me know if that is helpful so you will need to find the field names of lookups. Try flow without the lookup fields and see if it works. 

[Anonymous]

I've removed any/all values from the "lookup" fields and I'm STILL getting the error. (ARG!!)

And if you mean that I should somehow remove the lookup fields from the "Add a row" action, I have no idea how to do that. 

[Anonymous]

Okay, I had totally missed it, but looking at the inputs, I did just find the @OData reference. Now going to try running with nothing in THAT field (/column) and see if that's been the problem.

Thanks everyone!

[WebPortal]

This is ridiculous.

[Drona]

Advocate V 

Thanks. it was worked for me

[WijkagentBraum]

My man I want to personally thank you for this Tools > Copy set Name, it finally solved my problem with a Dutch table name with prefix and totally random plural name. Thank you so much.

[UserG]

I was facing the first problem, I ensured I had the appropriate "Set Name", and the correct GUID (I have had it pasted directly in as well as gathered from "Get row by ID"), but am getting an error that The GUID format needs to be formatted certain way, which it is:

I have tried Formatting the GUID multiple different ways. but nothing seems to work.