Setting the Scope of a process is essential when creating automatic workflows in Microsoft Dynamics 365/CRM.
Ledgeview finds that Scope is one of the most important pieces of Microsoft Dynamics 365/CRM Workflows that no one really knows much about.
Scope records are affected by Workflows you set up in Dynamics. They default to User whenever you set them up in a new Workflow.
99 times out of 100, you usually want to set them up to run on all records within your organization.
This is key for future troubleshooting. Follow this expert advice to avoid pulling out your hair with Dynamics in the future.
There are four options that can define your scope:
The Workflow will only affect records owned by the owner of the Workflow. Therefore, it’s almost set up like an individual Workflow.
When you elect this Scope, it means it will only run on the records owned by the same user as the Workflow user.
2. Business Unit
The Workflow will only affect records for all owners that are in the same business as the Workflow owner.
3. Parent: Child Business Unit
Enabling this Scope means the Workflow will only affect records for all owners that are in the same business unit and any child business units of the business unit Workflow center.
Consider you have six parent units and five child units that look up to a single parent unit.
If that child is in a parent unit, any records owned by individuals within that unit will be affected by the Workflows.
The Workflow will affect all records within your CRM Organization. It is the Scope used most often by Users.
It may seem like a “Click and Set” for an Organization but if you ever want to set this up to affect the Workflow the unit is in, there are actually options for that too.
Get more Workflow Setup Tips and Tricks! Watch Ledgeview’s On-Demand webinar below: