Design an approval process that starts in a canvas app, stores requests in Dataverse, and routes decisions through Power Automate.
Implementation approach
Create a Dataverse table named Expense Request with Requester, Amount, Business Justification, Approval Status, Approver, and Decision Comments. In the canvas app, validate the form and create the request with status Pending. Trigger an automated cloud flow when a row is added or modified, filtered to the Pending status. Use Start and wait for an approval, then update the same Dataverse row with Approved or Rejected and the responder’s comments. Keep the Dataverse row as the system of record; the approval response is an orchestration result, not your only record.
Recommended validation
- Build the flow inside a solution and use connection references.
- Test with real Dataverse security roles and least-privilege connections.
- Handle retries, duplicate triggers, timeouts, and connector failures.
- Keep business status and audit data in Dataverse.
- Verify the complete process in a non-production environment before deployment.
