cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

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

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

mrpowergage_1-1661849760555.png

how might I solve this? thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Expiscornovus
Most Valuable Professional
Most Valuable Professional

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

 

lookup_differententity.png

 

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


View solution in original post

31 REPLIES 31
Expiscornovus
Most Valuable Professional
Most Valuable Professional

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

 

lookup_differententity.png

 

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


perfect, thank you!

 

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

Expiscornovus
Most Valuable Professional
Most Valuable Professional

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



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


HortonHouse
Regular Visitor

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.

HortonHouse_2-1662378349652.png

 

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

 

HortonHouse_3-1662378464828.png

 

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:

HortonHouse_0-1665480577985.png

 

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

e.g.

HortonHouse_5-1662378587501.png

 

Use the ...(Value) field to get to the GUID.

HortonHouse_0-1662382762172.png

(Which has _ and value in the name suggesting it is a lookup/reference field 

HortonHouse_1-1662382834464.png)

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

 

HortonHouse_1-1662631898424.png

 

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
Advocate II
Advocate II

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

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

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
Frequent Visitor

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

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.

testasdfasfsafa_0-1678458397584.png

 

GJones
Frequent Visitor

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

Anonymous
Not applicable

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
Not applicable

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!

 

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
Not applicable

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
Not applicable

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
Impactful Individual
Impactful Individual

This is ridiculous.

Advocate V 

Thanks. it was worked for me

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.

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:

 

UserG_1-1693004363877.png

 

UserG_2-1693004376585.png

 

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

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,984)