PowerDynamics

Introduction- In this blog we will walk through all date and time expressions in power automate / cloud flow Explanation- For examples we have considered input as UTC. Format is optional in most of the expressions.

Introduction- In this blog we will understand the "Add to time" action of power automate/ cloud flow. Explanation- Add to time will add a integer number of a specified unit of time to the timestamp passed. Example- We can add 1 day/ second/minute/year/month to the passed time stamp. Syntax- addToTime('timestamp',interval,'timeUnit','dateFormat') Date format is optional. Output-  Note- This action adds the mentioned value however it does not validate the output date. There is a possibility of the output being a non existent date time value.

  Introduction- In this blog we will understand the Action Merge from a Plugin (SDK message) perspective. Problem Statement: 1) We want to retrieve data once the Merge is performed on two records. 2) We want to merge 2 records using a plugin (C# code). Solution: For the first statement, We shall be triggering a plugin on the message "Merge". While using the plugin registration tool, select message as Merge. Below code is to be used-   if ( context . InputParameters . Contains ( "Target" ) && context . InputParameters . Contains [ "Target" ] is EntityReference ) {     EntityReference Master = ( EntityReference ) context . InputParameters [ "Target" ];     Guid duplicate = ( Guid ) context . InputParameters [ "SubordinateId" ];  } For the second problem statement, we will invoke/ use the Merge method. Below is the code-       var target = new EntityReference ();       target . Id = Recordid ; //master recor...

Introduction- In this blog we will understand the Trigger and Action available for Merge Action in Power automate (Cloud Flow). Problem Statement: 1) We want to retrieve data once the Merge is performed on two records. 2) We want to merge 2 records using flow. Solution: For the first statement, we will be triggering a flow on Merge Action. Note- Table name will differ as per the requirement, here for example I have considered Lead. The output of the trigger is a JSON body that needs to be parsed, below is the schema.      { "type" :  "object" ,      "properties" : {          "InputParameters" : {              "type" :  "object" ,              "properties" : {                  "Target" :...