Dataverse Record Change Notifier

Overview

This flow watches a Dataverse table for row-level changes (add, modify, delete) and turns each event into a human-readable notification. When a row changes it classifies the operation, pulls the latest record details, builds a change summary, and posts an adaptive card to Microsoft Teams. If the change touches a critical field, it also emails the data steward so they can review or roll back. The pattern is meant as a reusable demo template — point it at any Dataverse table to get audit-style notifications without building a custom subscriber.

Use Case

Teams that own a business-critical Dataverse table often need to know the moment a record is created, edited, or deleted — and they want context (who, what, when) rather than a raw record link. This flow gives data stewards, ops leads, and integration owners a low-friction way to stand up real-time change notifications: Teams gets a formatted card for everyday awareness, and email is reserved for high-signal changes (deletes or edits to critical columns) that warrant a human review.

The flow is ideal for teams that:

• Data stewards monitoring a critical Dataverse table
• Ops teams that need real-time awareness of record creates/updates/deletes
• Integration owners auditing inbound changes from other systems
• Compliance reviewers who require a change trail for sensitive records

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Narrow the trigger to specific columns

Use the Select columns property on the Dataverse trigger to fire only when the columns you care about change. This cuts noise drastically on chatty tables and avoids burning Power Automate runs on irrelevant edits.

Add a debounce for bulk updates

If the source table is hit by bulk imports or integrations, add a small Delay (or a parallel branch that aggregates by record ID over a short window) before the Teams post so each record produces one consolidated notification instead of a flood.

Log every change to an audit table

Insert an extra Dataverse Add a new row action after the Compose step that writes the change summary to a dedicated audit table. Gives compliance a queryable trail independent of Teams retention.

Tune the critical-field check

Update the flowlibs_CriticalFields env var to match the columns your business actually treats as high signal. The condition is the only gate between 'Teams-only' and 'Teams + email' notifications.

Customize the adaptive card

Edit the JSON in the Post adaptive card action to add quick-action buttons (e.g. Acknowledge, Open in Model-Driven App, Open in Dataverse) so reviewers can act on the change from Teams without context-switching.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

triggerOutputs()?['body/SdkMessage']

triggerOutputs()?['body/ItemInternalId']

triggerOutputs()?['body/_modifiedby_value']

triggerOutputs()?['body/modifiedon']