top of page
Search

How to Patch Dataverse Lookup Fields in Power Automate (Step-by-Step Guide)

Graphic explaining what you will learn in this article.

Why Lookups Matter

This one’s for the Dataverse people. 👋 When you’re setting up your data model, Lookup fields can play a big role for several reasons. These columns make it much easier to connect your data, keep things consistent, and make your apps feel smarter and more reliable.


Good database design is really the foundation of any successful Power Platform project. But here’s the catch: it’s not just about building the right tables and relationships. It’s also about knowing how the rest of the platform will interact with those choices. And every once in a while, you’ll stumble across something that isn’t as obvious as you’d expect. Patching Lookup fields in Power Automate is a perfect example of that.


The Challenge with Patching Lookup Fields in Power Automate

At first glance, it feels like it should be easy. Getting a record from Dataverse is pretty straightforward: use the Get Row action, drop in the GUID, and you’re good to go.


So naturally, you’d expect updating (patching) a Lookup field to work the same way. But that’s where things get tricky. It turns out that patching a Dataverse Lookup field in Power Automate requires very specific formatting. The good news? Once you know the secret, it’s smooth sailing.


The Solution

While the GUID is important, you also need the Entity Set Name (which is just the Dataverse term for a table name). Luckily, it’s easy to find:

  1. Go to your Dataverse tables overview.

  2. Open the table you want.

  3. In the left panel under Table Properties, click Tools.

    Image of where to find Table Property Tools in Dataverse

  4. Select Copy Set Name (for example, pa911_testdata).

    Table Property Tools options, Copy set name

Now, head back to your Power Automate flow:


  1. In your Create Item or Update Item action, find the Lookup field.

  2. Paste your Set Name, followed by parentheses () (example: pa911_testdata()).

  3. Add the GUID inside the parentheses.

    Code: pa911_testdata(GUID)

It should look like this:

Add the GUID inside the parentheses

 

Your final result should look like this (an actual table is being used for this example)

Power Automate final result of the working code and flow.

































And that’s all there is to it!


You can even pass the GUID through a variable, dynamic content, or inside an Apply to each. As long as the string is formatted properly, it’ll work every time.


Recap

Dataverse Lookup fields are powerful for connecting your data and building a strong data model. But when it comes to patching them in Power Automate, the formatting can trip you up if you don’t know the trick.


Here’s the quick takeaway:

  • You need both the GUID and the Entity Set Name.

  • Format it like: EntitySetName(GUID)

  • Use it directly in your Power Automate flow (variables and dynamic content work too).


With this approach, updating Dataverse Lookup fields in Power Automate becomes simple and predictable. No more guesswork, just smooth automation.


If you're looking for some quick help with Dataverse, Lookups, Power Automate or maybe something else, we are just a click away. Reach out, and let us know how we can help!





bottom of page