Power Automate Trigger for Dataverse Field Changes

The requirement is to trigger a Power Automate cloud flow specifically when the customer account number field changes. In Microsoft Dataverse, the most reliable and standard trigger for reacting to data modifications within a table is the When a row is added, modified or deleted trigger.

Option D, When a row is added, modified or deleted, is the correct choice because it directly monitors the Dataverse table for any update operations on records. This allows the flow to intercept the change, validate the format of the account number, and apply corrections if necessary. It is the native integration point for automating business logic tied to record lifecycle events.

Option A, When a row is selected, is incorrect because this is not a standard Dataverse trigger for automation; it typically refers to UI interactions in canvas apps rather than backend data processing. Option B, When a flow step is run from a business process flow, triggers only when a specific stage or action is manually executed by a user within the BPF interface, not automatically when underlying data fields change. Option C, When an action is performed, is too vague and not a specific trigger name available in the Power Automate Dataverse connector context for this scenario.

A common trap is selecting Option B because the question mentions a Business Process Flow (BPF) is configured. However, the presence of a BPF does not mean all data changes must be handled via the BPF trigger. The BPF trigger is for workflow steps, while data validation on field changes requires the row-level trigger. The question asks for validation upon field change, which is a data event, not a process stage event.