We have a flow that uses an "ApproverEmail" field in a SharePoint List that then is used as the Approver in an Approval action. This has been working but a recent submission went to a completely different Approver (both called David but this I think is irrelevant). It seems to have changed at the point of the Approval being sent. A review of the version history of the List item showed no editing of the data prior to the Approval being sent, so this happened within the flow. This is a concern as it is ignoring / changing business logic and could lead to non approved user receiving data that is not appropriate for their role. Has anyone had this experience? Should this be a MS ticket? (see image for context - red dots mark the 2 different recipients - no step between these, so why has it changed?).
Thanks @grantjenkins, sadly that doesn't appear to be the case. We are also not licensed to use the Dataverse connector.
Have you checked both of these users in Active Directory to see if they have the same email listed, or if they were perhaps the same user but changed their name/alias, etc.?
Or perhaps (but unlikely) was reassigned within the approval from the first David to the next David? You'd be able to see this in the Approval Requests table in Dataverse for that particular Approval.
If you know the Approval Id (can get it by going into the flow run) you can use the Dataverse connector, List rows and pass in the Approval Id.
msdyn_flow_approvalrequestidx_approvalid eq 'YOUR_APPROVAL_ID'