Power Automate Flow How to handle Empty Lookup Fields in Dynamics 365

I have seen a lot of complicated Power Automate Flows to handle Empty Lookup Values when trying to Update records.

As you know setting a lookup field with empty value is going to cause the Power Automate Flow to error out.

Example:

Setting Lookup = accounts()

We are going to work with a scenario where we are going to retrieve Parent Account field value and populate it on another Account.

To handle this issue, we are going to declare a variable that hold the Lookup Value (String)

Then we are going to analyze if the source record has Parent Account populated or not

If the Parent Account has Value then we are going to set the variable with accounts(ParentAccount)

Otherwise we are going to set the value to null

The last thing to do here is to populate the field on your Update

This is going to save us time on our Power Automate Flow development and keep the flow clean and concise at the same time.

Comments

Azure DevOps Fork Repos between two Organization

Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organization,

Power Platform Tool for Visual Studio 2019/2022

Power Platform Tool for Visual Studio 2019/2022 We have a new Visual Studio Extension Power Platform Tool. Creation and deployment of Plugins, Custom Workflows and WebResources is going to be easy and time saving. This article is going to focus on how to connect to your environment and create your Visual Studio Solution. In a subsequent article I will try to cover on how to Create and deploy your components to your environment. Installation is straight forward go to Tools→ Manage Extensions→ Search for Power Platform Tools You will Need Visual Studio 2019 or later version Subsciption to Pawer App/Dataverse or trial .Net Framework 4.6.2 Now we will go over how to create a Project and connect it to your Environment Open Visual Studio 2019 →New Project Search for Power Platform Solution Template Add Project Name and Location → Create Click on Start from Dataverse to connect to your environment Enter the following and → Login

How to use Formatted Values in Power Automate Flow Dynamics 365

How to use Formatted Values in Power Automate Flow Dynamics 365 If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.

Michael Ghebremedin Dynamics 365 Notes

Search This Blog