Overview#

Flow name: MoveData_Donation_Donation_Post Label: [MoveData] Donation: Donation - Post Upsert Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This flow handles comprehensive post-processing operations after donation (opportunity) records are created or updated, including campaign member creation, matching gift relationship management, and opportunity contact role processing for soft credits.

Purpose#

The flow performs post-upsert operations that:

• Attempt to clean up opportunity naming conflicts with NPSP triggers
• Create campaign member records for donors with hierarchical status management
• Establish bidirectional matching gift relationships between donations
• Process opportunity contact roles for soft credit attribution across campaign hierarchies
• Support complex fundraising attribution scenarios with fundraiser and team-based campaigns

Salesforce fields#

This flow interacts with the Salesforce Opportunity object and its related fields. Below is a mapping of all fields utilised:

Input variables#

Core donation data#

Campaign member configuration#

Campaign hierarchy structure#

Soft credit configuration#

Advanced soft credit roles#

Output variables#

Flow logic#

1. NPSP name field cleanup#

Problem resolution: NPSP triggers automatically generate opportunity names based on donor and amount information. When MoveData sets custom names during mapping, this can create conflicts with NPSP's naming logic.

Solution process:

1. Detection: Checks if the opportunity record has a Name field that was set during processing
2. Field clearing: Uses ClearFieldFlowComponent to remove the Name field from the record
3. NPSP integration: Allows NPSP triggers to generate appropriate names post-commit

Technical implementation:

IF Record.Name WasSet THEN
  Add "Name" to FieldList
  Clear Name field from Record

2. Campaign member management#

Prerequisites validation: The flow validates all required conditions before creating campaign members:

• Campaign exists with valid ID
• Contact exists with valid ID
• Campaign member creation is enabled

Campaign member status initialisation:

InitialiseCampaignMemberComponent Parameters:
- CampaignId: DonationCampaign.Id
- DeleteOtherCampaignMemberStatuses: Config setting
- Status Labels: All configurable member status labels

Hierarchical status management: The flow establishes a prioritised hierarchy:

1. Team Leader (highest priority)
2. Fundraiser
3. Recurring Donor
4. Donor (target status for this flow)
5. Prospect (lowest priority)

Campaign member creation logic:

• Attempts to assign "Donor" status to the contact
• Respects existing higher-priority statuses (Team Leader, Fundraiser, Recurring Donor)
• Upgrades lower-priority statuses (Prospect)
• Uses CreateCampaignMemberComponentWithLogs for detailed logging

3. Matching gift relationship processing#

Matching gift detection: The flow identifies when a donation is part of a matching gift relationship:

IF Record.npsp__Matching_Gift__c WasSet AND
   Record.npsp__Matching_Gift__c IsNotNull

Bidirectional relationship establishment:

Step 1 - Retrieve matched donation:

• Queries the matched donation record by ID
• Retrieves current matching gift relationship fields

Step 2 - Validate relationship direction:

• Checks if matched donation already links back to current record
• Prevents circular or duplicate relationship creation

Step 3 - Update matched donation:

• Sets npsp__Matching_Gift__c on matched donation to point to current record
• Creates bidirectional matching gift relationship

NPSP matching gift fields:

• npsp__Matching_Gift__c: Links to the related donation
• npsp__Matching_Gift_Account__c: Employer account
• npsp__Matching_Gift_Employer__c: Employer name
• npsp__Matching_Gift_Status__c: Matching gift status

4. Opportunity contact role soft credit processing#

Multi-level campaign attribution: The flow supports complex campaign hierarchies with three levels:

• Top campaign: Overall campaign or cause
• Team campaign: Team or group within the campaign
• Fundraiser campaign: Individual fundraiser within team

Contact role assignment logic: The OppContactRoleSoftCreditFlowComponent processes multiple scenarios:

Scenario 1 - Direct donor:

• Primary donor gets "Donor" role
• Most common scenario for individual donations

Scenario 2 - Single-level attribution:

• Campaign organiser gets "Soft Credit" role
• Team leader gets "Soft Credit" role
• Individual fundraiser gets "Soft Credit" role

Scenario 3 - Multi-level attribution:

• Supports combinations of campaign/team/fundraiser
• Uses specialised role configurations for complex scenarios
• Prevents duplicate role assignments

Role configuration matrix: The flow uses different role labels based on campaign hierarchy complexity:

Soft credit prevention:

• Config_DonationSoftCredit_PreventDel: Prevents deletion of existing contact roles
• Preserves manually created contact role assignments

Error handling#

NPSP integration protection#

• Field clearing prevents naming conflicts with NPSP triggers
• Matching gift relationships use NPSP standard fields
• Contact role assignments follow NPSP soft credit patterns

Relationship validation#

• Validates matching gift relationships before creation
• Prevents circular references in matching gifts
• Checks for existing relationships before updates

Campaign member deduplication#

• Uses hierarchical status system to prevent duplicate statuses
• Respects existing higher-priority campaign member statuses
• Provides detailed logging for status assignment decisions

Dependencies#

Apex components#

• movedata__ClearFieldFlowComponent: Field cleanup for NPSP integration
• InitialiseCampaignMemberComponent: Campaign member status setup
• CreateCampaignMemberComponentWithLogs: Campaign member creation with logging
• OppContactRoleSoftCreditFlowComponent: Complex soft credit role processing

Related articles#

• Donation mapping flow
• Donation record match flow
• Donation post-upsert flow (Non-Profit Cloud)
• Fields and objects