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 / oData for Add New Row ...
Power Automate
Answered

oData for Add New Row Action with Dataverse

(1) ShareShare
ReportReport
Posted on by 5
Hi I have a Flow that in one action I get a row from a Dataverse Table that has a field that is a lookup field - so it links to another table.  In that Get Row action I use the following filter:  cr4e0_EstimateID/cr4e0_scopeidtxt eq 'EstimateID'.  EstimateID is a variable that is passed into the flow as an ID.  So in this oData cr4e0_EstimateID is the Schema name of the column in Dataverse and cr4e0_scopeidtxt part is the logical column name in the target lookup table.  This Get Row filter works perfectly fine with no issues.  Now I am trying to add a new row, to the exact same table, and I need to populate the same exact column in the new row, with the exact same Estimate .... so I have put the exact same formula in the EstimateID field in the Add Row Action in the flow.  But the same exact oData reference now throws an error.  What gives??? I have tried several variations, thinking that maybe I don't need the schema name, and just need the logical field from the target table? But that hasn't been the case.  Any help is appreciated.  I am attaching a screen shot in case it helps. 
This filter works:
 
 
This Add Row does not work: 
What am I doing wrong?  Considering that I kinda see a reference to the linked table, I also tried just:  cr4e0_scopeidtxt and /cr4e0_scopeidtxt thinking maybe I no longer need the reference to the schema table?  I also tried the logical name of the field which is:  cr4e0_ScopeIDtxt.  None of these have worked! What am I doing wrong?  Please help! Thanks! 
Categories:
I have the same question (0)
  • Verified answer
    Michael E. Gernaey Profile Picture
    53,963 Moderator on at
     
    You cannot use the same expression to set a lookup value. You have to actually use the proper syntax for a lookup value which would be like this
     
    /cr4e0_estimates(GUIDHere)
    and I cannot see it completely but the point is, the /logical_plural_name_of_entity(GUID) is the syntax.
     
    you are in a loop so, how come?
    But if each new row is supposed to have a different GUID
     
    then you would replace where i put GUID with the item() that is the GUID, or the variable that is the GUID
     

    If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

    Thank you!
    Sincerely, Michael Gernaey
     
     
  • SY-26012325-0 Profile Picture
    5 on at
    Thank you that did it!! Very helpful!

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 801

#2
Valantis Profile Picture

Valantis 602

#3
Haque Profile Picture

Haque 581

Last 30 days Overall leaderboard