As we all know that Microsoft Flow is also known as Power Automate.
So, it has some limitations as well. Like Request limit, Flow limits, etc. to know more about Limits and configuration in Power Automate,, click here.
Another important point about power automate is that it is priced based on the number of times the flow has been triggered.
So, today we will learn how can we restrict/filter our power automate trigger.
Here is the scenario, I have a custom entity(Blog Note) of activity type and I want my power automate to trigger on create of blog note record when it’s is created from the Contact entity.
Now, under the timeline section, I can see an extra activity entity named Blog Note under Account, Contact, Lead, and so on.
I have the power automate ready with me, which triggers whenever a record is created within the Blog Notes entity from any entity like account, contact, lead, and so on.
I want to restrict my flow run so that it triggers only when a user creates the blog notes from the Contact entity. If a blog notes is created from some other entity like account or lead then the flow should not trigger.
To handle this we need to go to the trigger step(Trigger on create of BlogNotes) setting.
This is how we check if the regardingid is a contact entity then only the power automate trigger else it won’t.
Today, we will learn how to check an empty value on a variable under Power Automate.
I had a requirement where I need to push my Lead record data from Dynamics CRM to another application.
To fulfill this requirement, I thought of going with power automate. Which would trigger whenever a record is created under the Lead entity and then push the data to another application.
Here I have a field Due Date which is an optional field on a form. So now it is a user who chooses to enter data or not.
I have a child flow where I need to pass the data of Due Data as well. Below is the JSON schema for Child Flow. We can see that the due date is of string type, therefore if we pass null value it would throw us an error: Invalid type. Expected String but got Null
To handle this scenario, we can use an empty expression:
Expression: syntax: if (empty(duedate), ”, duedate)
expression used to check field(duedate) was empty:
if (empty(string(triggerOutputs() ? ['body/duedate'])), '', triggerOutputs() ? [' body/duedate'])
How the expression work is it checks whether the field is empty or not, which means if the value is null or empty then it returns true which will pass ” not null. This is accepted as a string. Else, if the field contains a value then it would pass the field value.
The expression replaces the option set value with the given label. Example, whenever we get the loan type as ‘43260000’, using the expression I will get the result as “HomeLoan”.
Moving ahead, we can use the set variable step under our flow. Where we can use the expression based on the output we receive for the above steps.
Additionally on top of the above requirement handling process, I went into another scenario where the option set field was coming null. Reason, the field was marked as optional field. So, now its a user choice to enter data for option set field or leave it as null.
So, whenever I was getting the null value for the option set field records, I was getting an error as: Invalid type. Expected String but got Null.
Therefore for handling the null value exception, I went using empty expression:
Today, let’s learn how to calculate a person’s age using Power Automate.
There are multiple ways to calculate a person’s age. The DOB field which I have is of string type. So, I thought of using Power Automate to achieve this.
Search for Common Data Service and the trigger should be When a record is created, updated, or deleted as shown in the below image. Next, enter the required details like the environment and the entity name.
Then we will add a condition to our flow, where we will check whether the Date of Birth field is null or not.
If the Data of Birth field is not null then we will calculate the age. For that when the condition is met the flow would go under IF yes condition, where we will have to provide the entity name and field under which the calculated age needs to be populated.
Let’s learn about how to fetch data from Cosmos DB using Power Automate and push into Dynamics CRM.
For retrieving the data from Azure Cosmos DB we will need a few details from Azure:
1. URI 2. Primary Key
Let’s jump to Power Automate and start adding the necessary component for achieving this activity.
I have used a manual trigger for reading the data from Azure Cosmos DB and pushing it into Dynamics CRM. Chose an action –> Search for Azure Cosmos DB, then under action select Get all documents.
We will use the Azure Cosmos DB detail for establishing the connection as shown in the below image. Access Key to your Azure Cosmos DB account here we have to enter Primary Key as shown under Figure 1. Hit Create button.
Select the desired database under the Database ID and table under the Collection ID field and hit the + New step button.
After the connection has been successfully established. Search for Parse JSON and add Documentsunder the Contentfield. Paste the JSON output under the schema. Hit the + New step button.
Next, we will search for a control Apply to each.
Under, Select an output from previous steps field pastes the Bodyfrom the Dynamic content and click Add an action button.
The above action is needed as it will allow us to map the value coming from JSON to be stored inside Dynamics CRM entity attributes.
Now, we need to test our flow with a few more clicks to be performed. Click on the Test button which would appear on the right top of the screen.
The flow will start executing, once the flow has run successfully we will get the below screen.
Now, go into CRM and we will see the records have been created under the expected entity.
Scrolling down the page you will find few sets of services. If the service for which you are looking for is not present in the list, click on See all option. This will navigate you to the page where you can find all the services which are currently present with Microsoft.
Click on the service and select the template.
If the required template is not present. You can create your template from My flows.
Today I am going to create a flow which will send an email notification whenever an account is created in Microsoft Dynamics 365 application.
Clicking on Create form blank option will redirect you to the page where you can find multiple triggers. Choose a trigger to get started with the flow.
Select the CRM Organization under Organization Name field. This will populate all the entities respective to the selected organization under Entity name field.
Choose the CRM entity under Entity name. The flow would only trigger whenever a record is created under the selected CRM entity.
Click on add New step button.
I am going to receive email notification on my outlook account therefore I am searching for Outlook, select the mail option Outlook.com
Now, select Send an email option for sending the notification when an account is created in CRM.
Enter the Email address in “To” field which would get the email notification for every Account which gets created in CRM. Enter the Email Subject in the “Subject” field.
Microsoft flow provides you the ability to add the dynamic content by clicking on the Add dynamic content option as shown below:
Click on Show advanced options and select Yes under Is HTML field.
Go to mail Body and enter the text as shown in the below image: