web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Issue populating a Dat...
Power Automate
Answered

Issue populating a Dataverse lookup field dynamically in Power Automate

(0) ShareShare
ReportReport
Posted on by 9
Hi everyone,
 
I'm having a very specific issue when trying to populate a Dataverse lookup field dynamically from Power Automate.
 
CONTEXT
 
I have a flow triggered from a Dataverse table called Cotizaciones using:
 
 When a row is added, modified or deleted
 
 
Inside the flow, I use Add a new row to create records in another Dataverse table.
 
That target table contains a lookup column:
 
Cotización => lookup to the Cotizaciones table:
 
 
WHAT I NEED TO DO
 
I need to assign the current quotation record (the one that triggered the flow) to that lookup field dynamically.
 
From the trigger, I already have the record ID:
 
@{triggerOutputs()?['body/new_cotizacionesid']}
 
This value is the correct GUID of the current row in Cotizaciones.
 
PROBLEM
 
When I use that value to populate the lookup field in Add a new row, the flow fails with this error:
 
{
  "error": {
    "code": "0x80060888",
    "message": "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment 'GUID' provided in the URL."
  }
}
 
So the issue seems to be specifically related to how the lookup field expects the related record ID to be passed.
 
MY QUESTION
 
What is the correct way to populate a Dataverse lookup field dynamically in Power Automate?
 
More specifically:
- Is the GUID from the trigger enough?
- Should it be passed in another format?
- Should I use dynamic content, an expression, or an OData reference?
- What is the correct way to make a lookup field accept the current row ID from the trigger?
 
IMPORTANT NOTE
 
The relationship itself is correctly configured in Dataverse.
The issue is not the data model itself, but specifically how to populate the lookup field dynamically in the flow.
 
Any help would be greatly appreciated. Thanks in advance
I have the same question (0)
  • Verified answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     
    Why the error message is misleading; This part confuses many people:
         Resource not found for the segment 'GUID'
    Dataverse is essentially saying:
         “I expected a web-style entity reference like /cotizaciones(<id>), but you gave me just <id>”
    So it’s a format issue, not:
         Missing record
         Broken relationship
         Invalid GUID
         Permission issue

    Dataverse lookup fields cannot be populated with a raw GUID. Instead, Power Automate requires the lookup value to be passed using the @odata.bind format, referencing the related table’s entity set and record ID (for example:
    /cotizaciones(<GUID>)). The correct approach is to populate the lookup using an expression or advanced option that sets the lookupcolumn@odata.bind property, ensuring Dataverse correctly resolves the relationship during record creation. This resolves the OData parsing error and allows the flow to dynamically link the triggering record.
     
    Use the advanced field name for the lookup and set an expression.
    1)In Add a new row
    Do not use the visible lookup field
    Click “Show advanced options”
    You will see a field like this:
         cotizacion@odata.bind

    ⚠️ The prefix (cotizacion) is the schema name of the lookup column (not the display name)

    2)Paste this exact expression
    concat( /new_cotizacionesid'],  '/cotizaciones(',  ')')
    That’s it.
     
    What this does
    It tells Dataverse: “Bind this new child record to the Cotizaciones row with this ID”
    Dataverse requires this resource‑style reference:
         /entitysetname(GUID)
     
    How to verify names (important)
    Entity set name --> plural name (cotizaciones)
    Lookup schema name --> cotizacion
    You can confirm these in:
    Dataverse --> Table --> Columns --> Lookup column --> Advanced properties
     
    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.
  • GP-27031152-0 Profile Picture
    9 on at

    Thank you very much for the help!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard