Study guide
9.2 Dataverse Connector Triggers & Operational Filters
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
9.2 Dataverse Connector Triggers & Operational Filters
Key Takeaways Explain This Topic AI
The flagship Dataverse trigger 'When a row is added, modified or deleted' supports granular Change types: Added, Modified, Deleted, Added or Modified, Added or Deleted, Modified or Deleted, and Added, Modified or Deleted.
Trigger Scope determines the organizational boundary for event interception: Organization (tenant-wide), Business Unit (same BU), Parent: Child business units (BU plus descendants), or User (owned records only).
The 'Select columns' property is vital for performance and preventing infinite trigger loops when a flow updates the same record that triggered it.
Filter Rows uses OData filter syntax (e.g., statuscode eq 1 and revenue gt 50000) to pre-filter events at the Dataverse database layer before a flow run is instantiated.
The 'Run as' property controls the security execution identity of the flow: Flow owner (default), Triggering user (calling context), or Modifying user/Record owner.
Last updated: August 2026
Dataverse Connector Triggers & Operational Filters
The Microsoft Dataverse connector provides the primary integration pipeline between Microsoft Dataverse and Power Automate cloud flows. Unlike generic polling connectors, the unified Dataverse connector integrates directly with the Dataverse Event Execution Pipeline via high-performance, asynchronous webhooks. For the PL-200: Microsoft Power Platform Functional Consultant exam, you must demonstrate mastery over trigger event types, organizational scope boundaries, OData query filters, schema attribute filtering, execution security contexts, and custom action triggers.
1. The Dataverse Trigger Architecture
The core trigger for Dataverse automation is When a row is added, modified or deleted . This trigger replaces legacy Common Data Service (CDS) and Dynamics 365 connectors, providing native support for solutions, connection references, and enterprise security models. +-----------------------------------------------------------------------------+
- | DATAVERSE EVENT PROCESSING PIPELINE |
- | |
- | [DATAVERSE DATABASE EVENT] (Create / Update / Delete) |
- | | |
- | v |
- | +---------------------------------------+ |
- | | 1. SCOPE FILTER | <-- Evaluates User / BU / |
- | | Is record owner within target scope? | Parent-Child / Org scope |
- | +---------------------------------------+ |
- | | (Pass) |
- | v |
- | +---------------------------------------+ |
- | | 2. SELECT COLUMNS | <-- Did any specified columns |
- | | Were targeted attributes modified? | change? (Prevents loops!) |
- | +---------------------------------------+ |
- | | (Pass) |
- | v |
- | +---------------------------------------+ |
- | | 3. FILTER ROWS | <-- Evaluates OData expression |
- | | Does record meet OData criteria? | (e.g., statuscode eq 1) |
- | +---------------------------------------+ |
- | | (Pass) |
- | v |
- | +---------------------------------------+ |
- | | 4. TRIGGER CONDITIONS | <-- Evaluates WDL expressions |
- | | Do advanced @settings expressions pass| in trigger Settings tab |
- | +---------------------------------------+ |
- | | (Pass) |
- | v |
- | [INSTANTIATE CLOUD FLOW RUN] (Under configured 'Run as' identity) |
- +-----------------------------------------------------------------------------+
- Change Types
The Change type parameter determines which database lifecycle events activate the trigger:
Added : Fires when a new record is inserted (Create event).
Modified : Fires when an existing record is updated (Update event).
Deleted : Fires when an existing record is deleted (Delete event).
Added or Modified : Fires on both creation and subsequent updates (Upsert event).
Added or Deleted : Fires when records are inserted or removed.
Modified or Deleted : Fires on record updates or removals.
Added, Modified or Deleted : Universal trigger firing on all database state changes.
2. Trigger Scope Configuration
The Scope parameter defines the organizational boundary within the Dataverse business unit hierarchy where record modifications will be intercepted. +-----------------------------------------------------------------------------+
- | DATAVERSE TRIGGER SCOPES |
- | |
- | [ORGANIZATION] ---> Triggers tenant-wide across ALL BUs |
- | |
- | [PARENT: CHILD BUSINESS UNITS]---> Triggers in user's BU & ALL child BUs |
- | |
- | [BUSINESS UNIT] ---> Triggers ONLY in user's direct BU |
- | |
- | [USER] ---> Triggers ONLY on records owned by |
- | the flow owner / triggering user |
- +-----------------------------------------------------------------------------+
- Scope Hierarchy & Security Boundaries
Scope Option Evaluated Record Ownership Architectural Use Case
Organization Any record across the entire environment, regardless of owner or business unit. Global enterprise workflows (e.g., ERP synchronization, centralized compliance auditing, cross-department notifications).
Parent: Child business units Records owned by users/teams in the flow runner's business unit OR any subordinate descendant business unit. Regional supervisor automations (e.g., an East Coast VP overseeing regional sales branches).
Business Unit Records owned by users/teams within the exact same business unit as the flow runner. Department-isolated processes (e.g., HR onboarding workflows confined to a single branch).
User Records owned directly by the user identity executing the flow. Personal productivity automations and user-specific tasks.
Caution
Scope Mismatch Failures: If a flow is configured with Scope set to Business Unit or User , and a record is created by a user in a different business unit, the flow will NOT trigger, even if the flow owner has System Administrator privileges. Default to Organization scope for enterprise-wide background automations unless strict departmental isolation is required.
3. Operational Filtering: Select Columns & Filter Rows
High-volume Dataverse environments require precise operational filtering to optimize platform throughput, reduce API consumption, and prevent catastrophic infinite trigger loops.
Select Columns (Attribute-Level Trigger Filtering)
When a flow monitors the Modified or Added or Modified change type, Dataverse triggers by default whenever any column on the record is updated. This introduces two major risks:
Unnecessary Executions: Updating an unrelated column (e.g., updating a phone number) triggers a flow meant only to process credit limit increases.
Infinite Trigger Loops: If Flow A triggers on Account modification, and Action Step 3 updates the Account's LastProcessedDate column, the update action causes Dataverse to fire Flow A again, creating an infinite recursive execution loop.
To resolve this, populate the Select columns property with a comma-separated list of schema column names: statuscode,creditlimit,telephone1,cr123_approvalstage
With Select columns configured, Dataverse fires the trigger only if one or more of the specified columns were modified during the transaction.
Filter Rows (Server-Side OData Query Filtering)
The Filter rows property evaluates standard OData v4 expressions at the Dataverse database layer before instantiating a cloud flow run. If the expression evaluates to false, Dataverse discards the event without consuming Power Automate run quota. // Example 1: Active Accounts with Revenue exceeding 100,000
statecode eq 0 and revenue gt 100000
- // Example 2: Specific Choice Column Value (Approved status)
- statuscode eq 864500001
- // Example 3: Text column starts with prefix and lookup is populated
- startswith(accountnumber, 'CORP') and _primarycontactid_value ne null
- // Example 4: Date comparison (Created on or after specific date)
- createdon ge 2026-01-01T00:00:00Z
- Common OData Operators for PL-200
- Operator Meaning Example Syntax
- eq Equal to statuscode eq 1
- ne Not equal to statecode ne 1
- gt / ge Greater than / Greater than or equal revenue ge 50000
- lt / le Less than / Less than or equal creditlimit lt 10000
and / or / not Logical conjunction / disjunction / negation statuscode eq 1 and (revenue gt 100000 or creditlimit gt 50000)
- null Null check (Lookup columns use _columnname_value ) _parentcustomerid_value ne null
- startswith String begins with prefix startswith(name, 'Contoso')
- contains String contains substring contains(emailaddress1, '@contoso.com')
- Trigger Conditions (Settings Tab)
In addition to Filter Rows, makers can configure Trigger Conditions in the trigger's Settings > Trigger Conditions pane using Power Automate Workflow Definition Language (WDL) expressions: @equals(triggerOutputs()?['body/statuscode'], 864500001)
@and(greater(triggerOutputs()?['body/revenue'], 50000), not(empty(triggerOutputs()?['body/emailaddress1'])))
All configured trigger condition lines must evaluate to true for the flow to execute.
4. Run-As Execution Identity & Security Context
When a Dataverse-triggered flow executes downstream actions (such as reading sensitive records or updating related tables), the permissions evaluated by Dataverse depend on the trigger's Run as configuration. +-----------------------------------------------------------------------------+
- | DATAVERSE 'RUN AS' EXECUTION IDENTITIES |
- | |
- | [FLOW OWNER (DEFAULT)] |
- | - Runs under the identity and security roles of the flow creator/owner |
- | - Uniform execution regardless of who triggered the change in Dataverse |
- | - Ideal for system-level integrations and automated data transformations |
- | |
- | [TRIGGERING USER] |
- | - Impersonates the exact user who performed the database modification |
- | - Actions respect that user's specific Dataverse security roles and depth |
- | - Write/Update actions tag the triggering user in 'Modified By' columns |
- | |
- | [RECORD OWNER] / [MODIFYING USER] |
- | - Impersonates the user assigned as the owner of the modified row |
- | - Ideal for routing tasks and activities on behalf of account managers |
- +-----------------------------------------------------------------------------+
Important
Security Implications of Triggering User: When Run as is set to Triggering user , if User A modifies a record that triggers a flow containing an action to read a restricted financial table, the flow will FAIL with an AccessDenied error if User A does not possess Read privileges on that financial table. Ensure security roles are appropriately assigned when using user impersonation.
5. The 'When an action is performed' Trigger
Beyond basic table row mutations, Microsoft Dataverse allows developers and functional consultants to define custom business operations called Custom Process Actions and Custom APIs . Cloud flows can intercept these invocations using the When an action is performed trigger. +-----------------------------------------------------------------------------+
- | 'WHEN AN ACTION IS PERFORMED' ARCHITECTURE |
- | |
- | [DATAVERSE CUSTOM API / ACTION INVOCATION] |
- | (Called via JavaScript, C# Plug-in, Power Pages, or External REST API) |
- | | |
- | v |
- | [TRIGGER: When an action is performed] |
- | - Catalog: Core / Custom Business Domain |
- | - Category: Sales, Service, or Custom Category |
- | - Table name: (Optional: Bound to Account/Contact or Unbound/Global) |
- | - Action name: contoso_CalculateCreditRiskScore |
- | | |
- | v |
- | [ACCESS ACTION INPUT & OUTPUT PAYLOADS] |
- | - Parses complex JSON parameters passed into the action |
- | - Executes downstream logic and returns calculated results |
- +-----------------------------------------------------------------------------+
- Bound vs. Unbound Actions
Bound Actions: Tied to a specific Dataverse table (e.g., contoso_ApproveInvoice bound to Invoice ). The trigger requires selecting the Table Name and provides the targeted row GUID ( Target/accountid ).
Unbound (Global) Actions: Not associated with any specific table (e.g., contoso_SendTenantBroadcast ). The Table Name is set to (none) , and the action accepts global parameters.