Keep an append-only decision history instead of overwriting the only approval outcome on the request.
Implementation approach
Create a related Approval History table with Request lookup, Stage, Assigned Approver, Outcome, Comments, Decision Date, and Flow Run ID. When an approval completes, create a history row and update the parent request’s current status. Restrict update/delete permissions on history rows and enable Dataverse auditing where required. Avoid storing secrets or unnecessary personal information. This history table complements platform audit logs; define retention and access policies with the data owner.
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.
