Update and Add Lookup column in Dataverse using Power automate | How to write to the complex column

In this video you will learn how you can add a row or update a row in Dataverse using power automate which seems to be very simple but it will eat your head while executing because it is too difficult.
To do it you end up needing to know a hidden API end point.
Don't worry once you know the process or way of doing it , you will not struggle again.

Remember to use the URL you have to change the ORG to be your ORG and the other pieces to be your entity/table.

Join this channel to get access to various Power Platform functionality:

Learn PowerApps, Power Automate and Power Portal Page in one-to-one session with me
Get assistance on your project .

Charges are applicable as per requirement.

[PoojaMore-jw]

You are too good. Keep posting such videos. I was stuck with Look up column formatting for half day. And you came in my life like an angel. Thank you very much for such an informative video.

[Wolasch]

The only working tutorial for me!! Thanks!

[korebreach]

I was stuck on one thing, but after following your video to fix my flow, it works! The problem is, I don't know *why* it works. Here's my setup: I have an Excel spreadsheet with two columns, "Name" and "Calc". I have a Dataverse table with two fields, "Name" (which is populated with the same names as the Excel spreadsheet), and "Number", which is blank. The goal is, for each row in the Dataverse table (that is, each "Name"), get the matching row (by "Name") on the Excel sheet to get the Calc value. Then, use the Dataverse action, "Update a row" to put that "Calc" value in the "Number" field. My issue was in the "Update a row" action, what to use for the "Row ID" parameter. My intuition was that the Row ID parameter should contain something that identified the particular row I wanted to update. However, your video showed that I should use the "unique identifier for the entity (table)". Although it works now, I don't know why. It would seem that my "Row ID" should be something to identify the row, not something to identify the table. My guess is that because this is all happening inside an "Apply to each" loop, somehow, by specifying the ID of the table, the row is already known, since the loop contains just one row at a time.

[jagarapusivanagendrakumar]

Looking forward to watching similar kind of videos

[antoniokimble]

Appreciate you making this video! I was on the right track when it came to structuring my flow. I've already loaded my data but I couldn't pull in any of the lookup column info. I'll go ahead and use Power Automate to update all the records using the Excel spreadsheet to reference each entry correctly, but after that I'm gonna clear all the data and experiment to see if I can pull everything in one go.

[jagarapusivanagendrakumar]

Thank you very much for such an informative video

[DasunPrasanna-lp]

Thank you very much. ❤
Clearly described

[rakaeagles]

Can you show how to get value form other than primary column

[Xrusader]

The legacy Dataverse connector was fairly straightforward. The new Dataverse connector is an absolute mess. Completely unusable. Hope they fix this before the old connector is shut down.

[sreeniv]

Appreciate your effort! but Very confusing ! very disorgnised going here going to other screen and no flow!

[rakaeagles]

Very confusing.
Do home work before making video