Overview#

Flow name: MoveData_Donation_Recurring_Mapping Label: [MoveData] Donation: Recurring - Mapping Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This flow handles the mapping and transformation of recurring donation data from external donation platforms into Salesforce Nonprofit Cloud GiftCommitment records with support for comprehensive donor management and name pattern generation.

Purpose#

The flow processes incoming recurring donation data and maps it to appropriate Salesforce Nonprofit Cloud fields while handling:

• Donor relationship management (Contact/Account assignment)
• Anonymous donor configuration and lookup
• Recurring donation status mapping
• Fee calculation and amount adjustments
• Start date conversions to local timezone
• Campaign associations
• Name pattern generation using configurable templates
• Platform key tracking

Salesforce fields#

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

Input variables#

Core recurring donation data#

Platform integration#

Related records#

Fee calculation#

Configuration variables#

Output variables#

Flow logic#

1. Donor assignment#

The flow determines the primary donor relationship using this hierarchy:

Anonymous contact handling#

For anonymous donations:

• Configuration check: Validates Config_AnonymousContactId is provided
• Contact lookup: Retrieves anonymous contact record
• Error handling: Sets appropriate errors if configuration missing or contact not found

2. Date processing#

Converts start date from DateTime to local date:

• Component: Uses ConvertToLocalDateFlowComponent
• Assignment: Sets EffectiveStartDate field
• Configuration: Respects Config_RecurringSuppressStartDate and Config_RecurringIgnoreStartDateNotEmpty

3. Status mapping#

Maps external platform statuses to Nonprofit Cloud values:

4. Amount calculation#

Calculates the final amount using the formula:

CalculatedAmount = IF(Config_DonationAmountSubtractFeePlatform, Amount - FeePlatform, Amount)

Fee calculation hierarchy:

1. FeePlatformPublic (if provided)
2. Donation_FeePlatformPublic (if provided)
3. FeePlatform (if provided)
4. Donation_FeePlatform (if provided)
5. 0 (default)

5. Campaign association#

Campaign assignment logic:

• Skip: If Config_RecurringSuppressCampaign is true
• Assign: If DonationCampaign is provided and has valid ID
• Ignore: Otherwise

6. Name generation#

The flow uses configurable name patterns based on donor type:

Pattern selection#

• Contact donors: Uses Config_RecurringNameContact template
• Account donors: Uses Config_RecurringNameAccount template
• Fallback: Uses ASCII-encoded default patterns if configuration is empty

Name pattern processing#

• Component: Uses NamePatternParserComponent for template processing
• Variables: Supports Contact, Account, Amount, and date placeholders
• Fallback: Uses calculated name formula if pattern parsing fails

Default name patterns#

• Contact: {!Contact.Name} - {!Amount} - {!EffectiveStartDate}
• Account: {!Account.Name} - {!Amount} - {!EffectiveStartDate}

7. Record finalisation#

Final processing steps:

• Schedule type: Sets to "Recurring"
• Platform key: Assigns for future record matching

Processing summary#

1. Donor evaluation: Determine donor assignment strategy
2. Anonymous handling: Process anonymous contact configuration if needed
3. Date conversion: Convert start date to local timezone
4. Status mapping: Map external status to Nonprofit Cloud values
5. Campaign assignment: Associate with campaign if provided
6. Name generation: Create record name using patterns or fallback
7. Record finalisation: Set schedule type and platform key

Configuration options#

Donor management#

• Anonymous contact: Config_AnonymousContactId specifies fallback contact for anonymous donations

Field processing control#

• Suppress campaign: Skip campaign assignment entirely
• Suppress start date: Skip start date processing
• Suppress name: Skip name generation
• Conditional start date: Only set if field is currently empty

Name pattern configuration#

• Contact template: Configurable pattern for contact-based donors
• Account template: Configurable pattern for account-based donors
• Default fallback: ASCII-encoded patterns used when configuration is empty

Fee processing#

• Platform fee subtraction: Optionally subtract fees from donation amount
• Fee hierarchy: Supports multiple fee sources with priority ordering

Error handling#

Anonymous contact errors#

• Missing configuration: Error when anonymous contact ID not configured
• Contact not found: Error when configured contact cannot be retrieved

Name generation errors#

• Pattern parsing failure: Falls back to calculated name formula
• Error logging: Logs pattern parsing failures for troubleshooting

Data validation#

• Null value handling: Graceful handling of missing donor information
• Existing record preservation: Protects existing donor relationships

Dependencies#

• movedata__ConvertToLocalDateFlowComponent (Apex action)
• movedata__NamePatternParserComponent (Apex action)
• movedata__WriteToLogFlowComponent (Apex action)
• movedata__MoveDataLogEntry (Apex class)

Related articles#

• Recurring Platform Key Flow
• Recurring Record Match Flow
• Recurring Post Upsert Flow
• NPSP Recurring Mapping Flow
• Non-Profit Cloud fields and objects