Dynamics 365 Process Workflow Trigger Conditions

Hello Friends,

Welcome back with another post on Dynamics 365. Today, we will learn about the conditions upon which a Processes >> Workflow can be triggered in Dynamics 365.

Automatic Trigger:

Basically, there are 5 options upon which a Processes >> Workflow can be set to trigger automatically. These are-

1. Record is created-
1. If selected, then the workflow will trigger automatically when a new record is created. It always triggers AFTER the creation of record.
2. Record status changes-
1. If selected, then the workflow will trigger automatically when the Status field of an existing record change its value. It can be set to execute either BEFORE the changes or AFTER the changes of Status field. For example, Opportunity status changes to Won, Lost, Close.
3. Record is assigned-
1. If selected, then the workflow will trigger automatically when you Change the Ownership of a record. It can be set to execute either BEFORE the changes applied or AFTER the changes applied.
2. Remember, if you are creating a record for someone else means you are already setting someone else as owner while creating the record, it means you are assigning the record to someone else automatically. This is different case and workflow will not trigger in this case.
4. Record fields change-
1. If selected, it further asks to choose the field(s) you wish to get the workflow triggered upon their value change. You can pick more than one fields. The workflow will trigger automatically when you Change value of a field (selected during setup) of a record. It can be set to execute either BEFORE the changes applied or AFTER the changes applied.
5. Record is deleted-
1. If selected, then the workflow will trigger automatically when a record is deleted. It always triggers BEFORE the creation of record.

On-Demand Trigger:

Apart from automatic trigger, Dynamics 365 Processes >> Workflows can be triggered On-Demand. These are of 2 types.

1. As an on-demand process-
1. If selected, it starts reflecting on record page under Flow >> Run Workflow. You may select and run the workflow.
2. On-Demand workflow can offer bulk function to help eliminate tedious tasks from your workday.
2. As a child process-
1. If selected, it can be further associated with another workflow to get executed. When we click on "Add Step" during creation of workflow steps, we found a step "Start Child Workflow", workflow marked "As a child process" can be associated here.

Dynamics 365 Processes > >Workflows can be triggered in two mode-

1. Synchronous
2. Asynchronous

Dynamics 365 Processes > >Workflows can be triggered under two type of ownerships-

1. The owner of the workflow
2. The user who made the changes to the record

Dynamics 365 Processes > >Workflows supports 4 type of scopes-

1. User
2. Business Unit
3. Parent: Child Business Unit
4. Organization

Related Articles:

1. 7 Workflow Triggers in Microsoft Dynamics 365/CRM You Should Know
   

Disclaimer: This post is for personal use only.

Power Automate Flow vs Dynamics 365 Flow

Hello Friends,

Welcome back with another post. Today, we will discuss a very important comparison which is usually asked during interviews. It's a comparison between-

1. Microsoft Power Automate Flow
2. Microsoft Dynamics 365 Workflow

Let's see the advantages & disadvantages-

Advantages of Power Automate Flow-

1. Power Automate Flows can work with various web-based applications / services. For example - SharePoint, Dataverse, Twitter, Gmail, SQL.
2. Power Automate provide 600+ built-in connectors and custom connectors to connect with various apps / services. For example-
1. You can create a record in CRM based upon a tweet posted in Twitter.
2. You can create a case in CRM based upon an email received on Gmail.
3. You can send notification in Microsoft Teams to notify users when an opportunity is created, or a case is created.
3. Power Automate Flows facilitates to perform CRUD operations upon data.
4. Power Automate provides pre-built templates to create the flow.

Advantages of Dynamics 365 Workflow-

1. Dynamics 365 Workflows can be synchronous as well as asynchronous.
2. Dynamics 365 Workflows are faster than Power Automate Flows.

Additional Comparision:

Feature (Capability)	Power Automate Flow	Dynamics 365 Flow
Conditional Branching (Modeling)	Yes	Yes
Dynamics Content (Composition)	Yes	Yes
Trigger on Field Changes (Execution)	Yes	Yes
Trigger Conditionally on Field Values (Execution) (e.g., On a Certain Date in a Date Field)	No	No
Run On-Demand (Execution)	Yes	Yes
Run-as Scopes (Execution) (e.g., Organization, Business Unit, User)	Yes	Yes
Auditing (History)	Yes	Yes
Solution Support (Authoring & Portability)	Yes	Yes

Feature (Capability)	Power Automate Flow	Dynamics 365 Flow
Looping (Modeling)	Yes	No
Wait Conditions on Fields (Modeling)	No	Yes
Parallel Branch (Modeling)	Yes	No
OOB Connectors to External Systems (Modeling)	Yes	No
Access To Pre-Image of Event Data (Composition)	No	Yes
Run Child Workflows (Composition)	No	Yes
Run CDS Actions Including Custom (Composition)	No	Yes
Run Custom Workflow Activities (Composition)	No	Yes
Group Steps to Run in a Transaction (Composition)	Yes	No
Approval Workflows (Composition)	Yes	No
Trigger on Multiple CDS Entity Events (Execution)	No	Yes
Run on a Schedule (Execution)	Yes	No
Run Synchronously (Execution)	No	Yes
Run Analytics (History)	Yes	No
Modern Designer (Authoring & Portability)	Yes	No
AI Assisted Authoring (Authoring & Portability)	Yes	No

Related Articles:

1. POWER AUTOMATE & DYNAMICS 365 WORKFLOW WHICH/WHEN TO USE?
   

Disclaimer: This post is for personal use only.