cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
SharepointAMS
Frequent Visitor

URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL.

Hi

i have trieed all the ways for this lookup of employees but its not working,

it is supposed to work with- employees(dd16f1ef-8bdd-ec11-bb3c-002248d3a871) but its not working,

I have tried all other ways as well

 

SharepointAMS_0-1673584403637.png

 

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
MMMSXEH
New Member

I ran into the same problem. With help of the comment of @powerwood I was able to fix the issue.
You've got to use it like so:

/<table_name>s/<reference_to_object>

 

It'll look like the following in your cloudflow:

MMMSXEH_0-1676463704078.png

 

Pay attention to the added 's'. The table name should be plural.

 

Some tables will have a prefix. That's why it's a good idea to open up your Tables tab and check for the correct Name. For example, if a table has the name 'msd_test'. Then you should enter:

/msd_tests/<guid_of_object>

View solution in original post

Hi all, you need to use this format instead of what the solution said (maybe this was changed over the time):

<table logical collection name>(<GUID_of_lookup_row>)

 

the "logical collection name" is a specific term used in dataverse web api, and it is a property of the table stored in the table's metadata (in short, each table has a unique logical collection name, usually it is just plural of your table name however may not always be). The best way to get it is to use the tool "dataverse metadata browser“ in Xrmtoolbox, you can browser and find your table in question, and then right click, copy "logical collection name". - edited 20/04/2024

for example:

Stevieed_0-1683728846649.png

 

while my Projects and Cost Code is just the GUID of that parent row.

 

Another way to do this is to grabe the correct OData link for the row directly, which you can do by using "List row by ID" to list the parent row that you want to have the new record to lookup to, and then that step will give you the Odata link of that row, then you put it in your lookup column, which is essential the same that gives you <table_name>s(<GUID_of_lookup_row>)

 

View solution in original post

14 REPLIES 14

I'm having the same issue.

 

I'm trying to update a Dataverse Row and I get the same error.

 

My flow does the following, working with three Dataverse Tables - Purchase Orders, PO Items and Projects:

  1. Triggers when a new PO Item row is added
  2. Get a Row - Purchase Orders
  3. Get a Row - Projects
  4. Update a Row - PO Items
    1. Using the Row ID from the trigger
    2. Updates the Project lookup field - this is where I'm having the issue

I have tried the recommendation of putting "Projects(Project ID)" or just straight up Project ID from both the associated Project table or the Purchase Order table. Nothing works.

I dug a little deeper and solved this by taking the full table name and using the new format:

 

"/rab_projects/Project ID from the Get a Row - Projects"

MMMSXEH
New Member

I ran into the same problem. With help of the comment of @powerwood I was able to fix the issue.
You've got to use it like so:

/<table_name>s/<reference_to_object>

 

It'll look like the following in your cloudflow:

MMMSXEH_0-1676463704078.png

 

Pay attention to the added 's'. The table name should be plural.

 

Some tables will have a prefix. That's why it's a good idea to open up your Tables tab and check for the correct Name. For example, if a table has the name 'msd_test'. Then you should enter:

/msd_tests/<guid_of_object>
devcrm
Frequent Visitor

Dear all,

Please help, i run out to the same issue while trying to send emails in dataverse as activities

 

I have tried all configuration of tables as possible but it still run in error

devcrm_0-1680271684658.png

Or

devcrm_1-1680272187893.png

 

But the result is still

devcrm_2-1680272216859.png

Can you please help me solving that?

 

 

 

 

Hi,

 

I also have this error. I followed the accepted solution by using <plural tablename>/GUI identifier. I still get the same error. 

 

pageflourin_0-1683709405355.pngpageflourin_1-1683709415237.png

pageflourin_2-1683709430282.png

 

Hi all, you need to use this format instead of what the solution said (maybe this was changed over the time):

<table logical collection name>(<GUID_of_lookup_row>)

 

the "logical collection name" is a specific term used in dataverse web api, and it is a property of the table stored in the table's metadata (in short, each table has a unique logical collection name, usually it is just plural of your table name however may not always be). The best way to get it is to use the tool "dataverse metadata browser“ in Xrmtoolbox, you can browser and find your table in question, and then right click, copy "logical collection name". - edited 20/04/2024

for example:

Stevieed_0-1683728846649.png

 

while my Projects and Cost Code is just the GUID of that parent row.

 

Another way to do this is to grabe the correct OData link for the row directly, which you can do by using "List row by ID" to list the parent row that you want to have the new record to lookup to, and then that step will give you the Odata link of that row, then you put it in your lookup column, which is essential the same that gives you <table_name>s(<GUID_of_lookup_row>)

 

@Stevieed , the entitySetname worked for me. it was different from the "<table_name>s/" which was not working at all, this tutorial helped me a lot.  to figure it out

Ah I see, yeah as the video suggested, such a simple thing that should work but takes so many effort to make it working! One world to simplify: WTF!

Seriously! Before stumbling upon that video i spent half a day trying out combinations of logic names and all I can think of! 

devcrm
Frequent Visitor

Dear all ,

 

Thanks for your help and i finally find my issue.

It's not the plural name of the table that it is used! It is the entity SET Name which corresponds often to the plural name but sometimes not!!!

I was able to identify it with the add-on Level up for Dynamics 365/Power apps .

This add-on is really fantastic!

 

devcrm_0-1692891216179.pngdevcrm_1-1692891249850.png

Systemusers is the same than plural name 😉

devcrm_2-1692891326199.png

 

 

To be precised, iwas not stucked by the email messages but by the concerned to be linked to and there the table was not correct with plural name

devcrm
Frequent Visitor

Dear powerwood, is your lookup based on a personalized field? if yes, check the schemas collection (plural) name of your field. The plural (collection)  name it self is sometimes not sufficient or not the same than the schema's name.

By using the addon 'level up for Dynamics 365, you can get the metadata of all tables the collection schema's name is the proper one to use.

 

devcrm_0-1695371593178.png

 

Hi pageflourin,

Ideasmaster is probably not the collection schema's name, check the metadata of the tables with "Level Up for Dynamics 365" Add on and chase for the collection schema name.

If this help please like 😉

 

Thanks so much! This work. Was following everything right but didn't know you had to include an 's' at the end of the entity name 🙄

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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.    

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,333)