Cross-System Record Reconciliation Checker

Overview

A scheduled reconciliation flow that treats Dataverse as the source of truth and verifies that each row has a matching record in Salesforce. It runs daily, iterates every row in the configured Dataverse table, looks up the corresponding Salesforce record by external ID, and flags two kinds of exceptions: Missing (no Salesforce record exists for the external ID) and Mismatch (the Dataverse display name does not equal the Salesforce record's Name). A single HTML report is emailed to admins so data-integrity issues between the two systems surface the next morning instead of during a quarter-end audit.

Use Case

Multi-system environments (MDM patterns, CDP backends, hybrid CRM deployments) frequently drift between Dataverse and Salesforce because each system has its own maker tools. Manual reconciliation is slow, inconsistent, and usually too late. This flow turns reconciliation into a daily background job powered by standard connectors, so Admins and Developers see a full exception list in their inbox without running SOQL or fetchXML by hand.

The flow is ideal for teams that:

• Salesforce is the customer system of record but Dataverse is the source for a subset (e.g. field-service accounts).
• A nightly ETL writes Dataverse but Salesforce receives writes from a different integration, so drift is expected.
• Audit/compliance requires a daily "are-we-in-sync" log without granting integrators direct DB access.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Re-target a different Salesforce object (e.g. Account)

Update flowlibs_SalesforceObjectType to Account and flowlibs_SalesforceExternalIdField to whatever field on Account is marked as External ID (e.g. AccountNumber__c). No flow edits required — the Salesforce action reads both from variables bound to env vars.

Re-target a different Dataverse source table (e.g. accounts)

Update flowlibs_DataverseSourceTableSet to accounts (display/reporting only), and set flowlibs_DataverseExternalIdColumn / flowlibs_DataverseDisplayNameColumn to the matching account columns (e.g. accountnumber and name). Also edit the List_Dataverse_Source_Records action's entityName parameter from contacts to the new entity set name — it is hard-coded per the FlowLibs "Zero Flow Checker errors" rule.

Compare more than just display name (e.g. phone, email)

In If_Record_Mismatch_Found, replace the single not(equals(...)) expression with an or containing one not(equals(...)) per field you want to diff. Extend the mismatch row in Append_Mismatch_Row_To_Report to print each differing field.

Change cadence

Edit the trigger — frequency, interval, or schedule.hours / schedule.minutes

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

item()?[variables('varDataverseExternalIdColumn')]
item()?[variables('varDataverseDisplayNameColumn')]

@{string(coalesce(item()?[variables('varDataverseExternalIdColumn')], ''))}

{
  "not": {
    "equals": [
      "@toLower(trim(string(coalesce(item()?[variables('varDataverseDisplayNameColumn')], ''))))",
      "@toLower(trim(string(coalesce(body('Get_Salesforce_Record_By_External_Id')?['Name'], ''))))"
    ]
  }
}

@{if(empty(variables('varMismatchRowsHtml')),
     '<tr><td colspan="4" style="...">No exceptions found - Dataverse and Salesforce are in sync.</td></tr>',
     variables('varMismatchRowsHtml'))}

"If_Record_Missing_In_Salesforce": {
  "runAfter": { "Get_Salesforce_Record_By_External_Id": ["Failed", "Skipped", "TimedOut"] },
  "expression": { "equals": [1, 1] }
}