cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
mrpowergage
Advocate III
Advocate III

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

mrpowergage
Advocate III
Advocate III

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
Kudo Collector
Kudo Collector

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 .

testasdfasfsafa
Kudo Collector
Kudo Collector

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.

UserG
Employee
Employee

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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,693)