Lab 7 · M5 Deep Integration Across Data Sources

Trigger Filters

Stop a Dataverse trigger from firing on every column change — narrow it to one column, then to one specific value, so the flow only reacts when an opportunity actually closes.

20 min Requires Lab 2

Exercises

01
Exercise 1 — Find the column's logical name

Trigger filters reference Dataverse columns by their logical name (e.g. cr977_opportunitystatus), not their display name — you'll need it in Exercise 2.

  1. In https://make.powerapps.com → Tables → Opportunity → Columns, open the Status column.
  2. Expand Advanced options and copy the Logical name. Your prefix will differ from any example shown elsewhere — that's expected, it's tenant-specific.
Task 2.1 — Create the trigger
  1. Select + Create → Automated cloud flow, name it Opportunity Closed.
  2. Search triggers for Dataverse, choose When a row is added, modified, or deleted, select Create.
Task 2.2 — Configure the base trigger
  1. Rename the step to Opportunity changed. Change Type: Modified. Table Name: Opportunities. Scope: Organization.
Task 2.3 — Send the notification
  1. Add Send an email (V2), rename to Notify by email. To: your tenant user ID. Subject: Opportunity closed.
  2. Body: insert dynamic Opportunity Subject, then (via See more) Opportunity Status from Opportunity changed.
Task 2.4 — Narrow to one column
  1. On the trigger, set Select Columns to the logical name from Exercise 1 — this stops the trigger firing on unrelated field edits.
Task 2.5 — Narrow to one value
  1. Set Filter Rows to <your logical name> eq 3 (3 is the Closed choice value from Lab 2). Now the trigger fires only when status changes to Closed.
  2. Select Save.
  1. In https://make.powerapps.com → Tables → Opportunity, change any record's Opportunity status to Closed.
  2. Open Outlook and confirm the "Opportunity closed" email arrived. Changing a different field, or setting status to New/Open, should not trigger anything.