Create Item with Lookup Field in Power Automate: Dataverse

Angelo Gulisano has penned down an insightful article about creating items with Lookup field in the Power Automate secure platform, namely, Microsoft Dataverse. This platform is widely utilized for management and storage data needed by business apps. The blog also sheds light on how to create or update a row with lookup field possibly helping those endeavouring in this direction.

The initial situation presented includes two tables- 'Customers' and 'CustomerContacts'. The 'CustomerContacts' table comprises two fields: 'Name' and 'Customer'; the latter is a lookup column referring to the 'Customer' table. The author elaborates on creating records for the customer.

For the purpose of the tutorial, the assumption is made that the end-user needs to create customer contacts through Power Automate from an Excel file. The discussion progresses to the resultant Flow that is utilized for this purpose. More specifically, the Microsoft Dataverse actions are employed for both Dataverse and Dataverse for Teams.

The process involves importing Excel File for each row, wherein the "Add new row" action is utilized to create a row. However, it is brought to note that the intended action does not work due to an ODataUnrecognizedPathException error. The problem is that one cannot create a row using a text field from Excel in Lookup field. For more information about this problem, click here.

The author progresses to the resolution of setting the lookup field value. The logical name of the table and the RowId of the record to be referred need to be used in this process. The Flow can now be updated to implement this construct using Row ID, or by using @odata.id directly.

To retrieve the row id, accurate items need to be referred. Therefore, the logical name of the field must be found. As a result, your newly updated flow will include writing into the 'Customer' field as follows:

first This operation fetches the first row from "List row actions" using the @data.id value. 


 Supplementary Note 

 Microsoft Dataverse offers a powerful solution to businesses allowing them to automate processes, structure and secure data, and ultimately enhance productivity. Power Automate permits you to create automated and intelligent workflows between your favorite apps and services, keeping your business stay ahead of the curve. A lookup field in Microsoft Dataverse is beneficial for storing relationships. Here, the author has touched on a familiar predicament related to lookup fields in Dataverse (for Teams), teaching us a valuable way to steer clear of certain trapdoors. 



Read the full article Dataverse – Create Item with Lookup field in Power Automate


Learn about Dataverse – Create Item with Lookup field in Power Automate

The Power Automate Dataverse is a secure platform tailored for the storage and management of data utilized by business apps. If you aim to master the creation or updates of rows with a lookup field in Dataverse, this article will be beneficial. We are going to explore the initial creation phase, some common errors, and methods of resolving these issues. 

We start with a situation involving two tables named Customers and CustomerContacts. The latter has two fields namely; Name and Customer. The Customer field is a Lookup Column referring to the Customer table. At first, three records were created for the customer leaving the Table CustomerContracts empty.

Presumably, our aim is to create Customer Contacts through the Power Automate imported from an Excel File. At this point, we encounter an error while implementing the 'Add new row' action for each row derived from our Excel file. This issue originates from the inability to create rows using the text field from Excel in the Lookup field. Consequently, the complexity of this problem calls for a resolution in setting up the Lookup field value. 

In dealing with this predicament, it would help if we had the logical name of the table and RowId of the record to reference. This step should be followed by updating our flow to use this construct employing Row ID, cr3e4_customers([ROW_ID]) or alternatively @odata.id directly. The row id is obtained by sourcing items that correctly refer. This process should be preceded by finding the logical name of the field. Once all this is done, our flow's structure will transform. 

Lastly, the Customer field should be noted as follows: 
first(body('List_rows')?['value'])?['@odata.id']

This command is used to attain the first row from the "List row actions" which is filtered by customer name and subsequently use @data.id value. 

Understanding these intricacies of Power Automate Dataverse can be a significant step towards mastering the platform. This knowledge could immensely help streamline your data management activities in business applications, making them a lot more efficient. Got questions? Feel free to reach out. Enjoy your day!
More links on about Dataverse – Create Item with Lookup field in Power Automate
Solved: How do I include Dataverse lookup records in a new...
Aug 11, 2021 — I am trying to add a new record to the Dataverse and populate two lookup columns using dynamic content from Dataverse tables.
How to update Dataverse lookup column with Power ...
Nov 16, 2022 — Get the table entity name and update the column · Run the flow and check the 'Compose' action in the run history. · Enter the url in the browser ...
Keywords
Dataverse, Create Item, Lookup Field, Power Automate, Power Automate Process, Dataverse Lookup, Flow Creation, Automate Dataverse, Power Automate Dataverse, Dataverse Item Creation