Which Dataverse Trigger Fires on a Custom API Action?

Why the Answer Is Correct

Option A, "When an action is performed," is the Dataverse trigger purpose-built to fire when a specific action — including a custom API action such as SubmitForReview — is invoked. Because the requirement is that the flow runs every time the SubmitForReview action is run, an action-scoped trigger matches that contract exactly and scopes the trigger to the named action rather than to general data mutations. Custom API actions are exposed in Dataverse as actions, so the action trigger can be filtered to that action and will not react to ordinary row writes.

Why the Other Options Are Wrong

Option B, "When a row is added, modified, or deleted," is row-scoped: it fires on any insert, update, or delete across the table, so it would trigger on unrelated record updates and directly violates the requirement to avoid them. Option C, "When a row is selected," is a selection-oriented trigger tied to user interaction with a row, not to execution of a server-side action, so it would never fire when apps or services call the custom API. Option D, "When a row is added," only reacts to record creation and would still trigger on unrelated inserts while missing the action invocation itself, since the action's internal record creation is an implementation detail rather than the contract the flow must observe.

Community Comment Notes

A single learner comment supported the same conclusion, selecting answer A with "When an action is performed" as the reasoning. No dissenting comments were posted, so the community view aligns with the technical design of Dataverse action triggers, though the vote count is too small to serve as independent evidence on its own.