Understanding CDS (Current Environment) “When a row is added, modified or deleted” trigger.

Introduction: In this blog, we will understand all the parameters of the “When a row is added, modified or deleted” trigger of CDS (Current Environment)

Change Type: As per your requirement, Power Automate lets you select trigger combination, it also lets you select a combination of conditions in the CDS (Current Environment) connector compared to the CDS Old Connector.

Example: If you want your flow to trigger when record is created or updated than you can select “Create or Update”.

Table Name: select the Dataverse table(entity) on which your flow should be triggered.

Scope: With a scope, you can determine if you want your flow to run when a new record is created or modified by a user within your business unit, or if a new record is created or modified by any user in your organization.

ScopeTrigger
Business UnitAction is taken on a record owned by your business unit
OrganizationAction is taken by anyone within the organization
Parent: Child Business UnitAction is taken on a record owned by your business unit or a child business unit
UserAction is taken on a record owned by you

Column Filter:  For triggering your flow on updates on specific attributes, you can use this parameter to specify those attributes.

Example: If you want Flow should trigger only when Opportunity status or Estimated Revenue field is updated, add column filter as below:

Row Filter: To trigger your flow only on specific conditions, add that condition in this parameter.

Example: Flow should trigger when Opportunity is Won, then add condition like below:

Delay until: If you want your flow should not trigger until a specific date, then add that date attribute in the Delay until parameter.

Example 1:  You want to trigger your flow when the estimated closed date of opportunity is reached; then specify the attribute “estimatedclosedate” in Delay until parameter.

Example 2:  You want to trigger your flow when follow up date of your case is reached.

Let say you have a case with a follow-up date “03-04-2021” and you want your flow should get trigger automatically when the follow-up date of the case is reached i.e. on “03-04-2021”.

Run as: Here you can decide in which users’ context this flow will run.(only applies if invoker connection is specified)

Run asTrigger
Process OwnerOwner of Ms Flow
Record Owner Owner of Record in CDS
Triggering UserUser who triggered the flow

Leave a Reply

Your email address will not be published. Required fields are marked *