How do I include Dataverse lookup records in a new Dataverse record?

[arpost]

I am trying to add a new record to the Dataverse and populate two lookup columns using dynamic content from Dataverse tables. Every time I try to add a new record, I get a "Resource not found for the segment XXXXX" message. My flow is configured as follows:

The Get Created Model is a "Get by Row ID" and the "Get Default Forecast Values" is a "List rows" step, so I'm wanting to create a new record for each Forecast Value and link to the Fee Type and the ForecastModel from the previous steps.

Anyone have any ideas? About to pull my hair out.

[arpost · Accepted solution]

So I figured it out with the help of this blog post (https://linnzawwin.blogspot.com/2019/11/power-automate-how-to-set-lookup-field.html). I saw some similar posts in the Community forum as well but didn't quite make sense of it until I found this article.

To summarize, it appears that the current Dataverse connector STILL expects users to input the plural name of the Dataverse field and then enclose the dynamic GUID content block in parens:

Why? I have no idea... I've heard it was "by design," but this literally took hours for me to figure out, so I hope the Microsoft team will resolve that behavior as it turns the "low-code/no-code" nature of the Power Platform into "low-code/no-code/hope-you-can-stumble-across-a-solution-code"! 😞

[testasdfasfsafa]

I just wasted a ton of time on this issue. I don't know why Microsoft took something simple (like selecting the GUID) and forcing a user to find the logical name or internal name and make it plural, etc...   This is NOT "workflow for everyone" as Microsoft claims.

[andybarker1]

@arpost thanks for sharing - you saved me hours - I never would have figured that out.

[arpost]

You’re welcome! Glad it helped.

[manishhada1985]

This plural thing really a problem and it wasted lots of my time. 

[testasdfasfsafa]

This is terrible design...  the previous Dynamics 365 and legacy dataverse doesn't need this kind of complicated input.  Just you put the lookup id and you were done.   Going backwards...  This product is so messy on so many ways, it's frustrating. Please change the leadership team...

[Roger_Ullilen]

Hola, coincido  con Tigo , para las cargas masivas o insertar en diferentes tablas es muy tedioso sin embargo he encontrado una forma de hacerlo y espero que te pueda servir 

🚀como realizar una carga masiva a Dataverse sin flujos - YouTube