Skip to content

Note

This flow is self-documenting and should be viewed within Salesforce (Setup > Process Automations > Flows). This document is to support working through a visual flow. Please note: the flow commentary is produced using AI.

Overview#

Flow name: MoveData_Donation_Contact_Duplicate Label: [MoveData] Donation: Contact - Record Match Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This flow performs duplicate detection for contact records by using platform keys to identify existing contacts in Salesforce, enabling proper record matching and preventing duplicate creation.

If there is no match, MoveData will execute the Salesforce Duplicate Detection rules after the flow (if configured).

Purpose#

The flow provides duplicate detection capabilities that:

  • Uses generated platform keys to look up existing contact records
  • Checks the movedata__Contact_Platform_Key__c.movedata__Platform_Key__c field for matches
  • Returns Salesforce Record IDs when duplicates are found
  • Supports both Salesforce Key and Platform Key lookup strategies

Salesforce fields#

This flow interacts with the Contact Platform Key custom object and its related fields. Below is a mapping of all fields utilised:

Field API name Field type Purpose in flow
movedata__Platform_Key__c Text Stores external platform identifier for matching

Input variables#

Variable Type Required Description
SalesforceKey String No Existing Salesforce Record ID (if known)
PlatformKey String Yes Generated platform key for lookup matching

Output variables#

Variable Type Description
Result String Salesforce Record ID of matching contact (if found)

Flow logic#

1. Salesforce key priority check#

The flow first determines the lookup strategy:

  • If SalesforceKey is provided: Returns the existing Salesforce Key immediately
  • If SalesforceKey is null: Proceeds to platform key lookup

2. Platform key validation#

The flow checks if a platform key is available:

  • If PlatformKey is provided: Proceeds to platform key lookup
  • If PlatformKey is null: Flow terminates without returning a match

3. Platform key lookup#

When a platform key exists, the flow performs platform key matching:

  • Uses movedata__PlatformKeyLookupComponent Apex action
  • Searches Contact records by movedata__Contact_Platform_Key__c.movedata__Platform_Key__c field
  • Returns the matching Salesforce Record ID if found

Lookup strategy#

The duplicate detection follows this hierarchy:

  1. Direct Salesforce key: If provided, use immediately (highest priority)
  2. Platform key lookup: Search existing records using platform key matching
  3. No match: Returns null if no duplicate found
  4. Salesforce Duplicate Rules: MoveData will execute the Salesforce Duplicate Detection rules after the flow (if configured).

Dependencies#

  • movedata__PlatformKeyLookupComponent (Apex action)
Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?