Dataverse Record Change Mobile Alert
When a critical Dataverse record (e.g., high-value opportunity) is modified, send a push notification with the changed fields.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
Dataverse Record Change Mobile Alert monitors a configurable Dataverse table for record modifications and sends a mobile push notification when a critical record exceeds a defined threshold. Designed for sales teams and operations staff who need instant awareness of high-value changes — such as an opportunity's estimated value surpassing a key financial threshold — without watching dashboards.
The flow ships Off (Stopped). Turning it on requires only connection authorization and environment variable configuration for your specific table, threshold field, and notification recipient.
Use Case
A sales manager wants instant mobile alerts whenever a high-value opportunity is updated. By setting the threshold field to estimatedvalue and the threshold value to 100000, any modification to an opportunity worth $100K+ triggers an immediate push notification to their phone via the Power Automate mobile app.
Other use cases: monitoring critical incident records, tracking high-priority accounts, or alerting on contract value changes.
Flow Architecture
When a Record Is Modified
Dataverse WebhookFires on any row update in the configured table (Organization scope).
Init varTableName
Initialize VariableBinds the `flowlibs_DvAlertTableName` environment variable to a variable. Runs in parallel with the other three Initialize Variable actions.
Init varThresholdField
Initialize VariableBinds the `flowlibs_DvAlertThresholdField` environment variable to a variable. Runs in parallel.
Init varThresholdValue
Initialize VariableBinds the `flowlibs_DvAlertThresholdValue` environment variable to a variable. Runs in parallel.
Init varNotificationRecipient
Initialize VariableBinds the `flowlibs_AdminNotificationEmail` environment variable to a variable. Runs in parallel.
Compose Threshold Field Value
ComposeExtracts the threshold field value dynamically from the trigger body using `triggerBody()?[variables('varThresholdField')]`.
Check If Record Is Critical
If conditionCompares `float(outputs('Compose_Threshold_Field_Value'))` against `float(variables('varThresholdValue'))` to determine whether the changed record qualifies as critical.
- Compose Alert Message — Builds notification text with table name, field value, threshold, modifier name, and modification timestamp.
- Send Mobile Push Notification — Sends a mobile push via the Power Automate Notifications connector to the flow owner.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_DvAlertTableName | String | opportunity | Logical name of the Dataverse table to monitor. |
| flowlibs_DvAlertThresholdField | String | estimatedvalue | Column logical name evaluated against the threshold. |
| flowlibs_DvAlertThresholdValue | String | 100000 | Minimum numeric value that qualifies a record as critical. |
| flowlibs_AdminNotificationEmail | String | admin@contoso.com | Notification recipient address (shared across FlowLibs solutions). |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Microsoft Dataverse | shared_commondataserviceforapps | When a Record Is Modified (trigger) |
| Notifications | shared_flowpush | SendNotification |
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.
- Change the monitored table
- Update flowlibs_DvAlertTableName to any Dataverse table logical name (e.g., account, incident, contact).
- Change the threshold field
- Update flowlibs_DvAlertThresholdField to any numeric column on the target table (e.g., revenue, budgetamount, prioritycode).
- Adjust the threshold
- Update flowlibs_DvAlertThresholdValue to the minimum value that should trigger alerts.
- Add a notification link
- Expand 'Show all' on the Send Mobile Push Notification action's Advanced parameters to add NotificationDefinition/notificationLink/uri pointing to your model-driven app record URL.
- Filter trigger scope
- Add a Filter Rows expression to the trigger (e.g., statecode eq 0) to limit which records fire the flow.
- Add column filtering
- Add Select Columns to the trigger to fire only when specific columns change.
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.
EXPR.01Dynamic field access
Accesses a Dataverse column whose name is stored in a variable, allowing the monitored field to be configured via environment variable.
EXPR.02Numeric comparison
Converts the dynamic field value to a float so it can be numerically compared against the threshold.
EXPR.03Alert message concatenation
Builds a rich notification message containing table name, field value, threshold, modifier, and timestamp.
Customize & download
Generate a ready-to-import copy of this solution with your environment-variable values baked in — available on Base, Pro, or Team.
Upgrade to customize
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.