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_Recurring_Duplicate Label: [MoveData] Donation: Recurring - Record Match Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This flow performs duplicate detection for recurring donation records by using platform keys to identify existing recurring donations in Salesforce, enabling proper record matching and preventing duplicate creation during data imports.

Purpose#

The flow provides duplicate detection capabilities that:

  • Uses generated platform keys to look up existing recurring donation records
  • Checks the Platform_Key__c field on GiftCommitment records for matches
  • Returns Salesforce Record IDs when duplicates are found
  • Supports Nonprofit Cloud GiftCommitment object integration

Salesforce fields#

This flow interacts with the Nonprofit Cloud GiftCommitment object and its related fields. Below is a mapping of all fields utilised:

Field API name Field type Purpose in flow
Platform_Key__c Text Stores external platform identifier for matching
Id ID Unique record identifier returned when match found

Input variables#

Variable Type Required Description
PlatformKey String Yes Generated platform key for lookup matching

Output variables#

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

Flow logic#

1. Platform key validation#

The flow first validates that a platform key is provided:

  • If PlatformKey is present: Proceeds to perform lookup on GiftCommitment records
  • If PlatformKey is null: Flow terminates without performing lookup

2. Platform key lookup#

When validation passes, the flow performs record matching:

  • Object: Queries GiftCommitment records
  • Filter: Platform_Key__c equals provided platform key
  • Result: Returns ID of matching record if found
  • Null handling: Returns null if no matching record exists

Processing summary#

  1. Platform key check: Verify if platform key is provided
  2. Record lookup: Search GiftCommitment records using platform key matching
  3. Result return: Provide matched Salesforce Record ID or null if no match

Configuration options#

The flow uses a simple, standardised approach with no configuration options, ensuring consistent lookup behaviour across all platform integrations.

Error handling#

Lookup strategy#

The duplicate detection follows a simplified approach:

  1. Platform key lookup: Search existing records using platform key matching (only option)
  2. No match: Returns null if no duplicate found

Data validation#

  • Null key handling: Gracefully handles scenarios where no platform key is provided
  • Record not found: Uses assignNullValuesIfNoRecordsFound=true for clean null handling
  • Single record return: Designed to return single matching record ID

Dependencies#

None

Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?