#Advanced Mapping0 diskutieren mit

I've had a bash at the #Advanced Mapping​ Recurring Donations Recipe. This brings in the Recurring Donations and the first Opportunity is created by the NPSP Data Import.

Recurring Donations Recipe

Attach a Recurring Donation to Contact1

To link a Recurring Donation to Contact1, follow the steps below.

1. Prepare Salesforce for the Recurring Donations Object Group, and create these fields on the NPSP Data Import object:

• Recurring Donations Imported (lookup)
  • Recurring Donations Import Status (text)

1. Add at all the fields to map on the NPSP Data Import object. Make sure the field type matches the type on the Recurring Donations Object, such as:

• Recurring Donations Type  (Text)

1. In NPSP Settings, create a new Object Group for Recurring Donations 1 with the following information:

• Group Name: Recurring Donations
  • Object Name: Recurring Donations
  • Is Child/Parent: Child
  • Of This Mapping Group: Contact 1
  • Through This Field: Contact
  • Link to Field: Recurring Donations Imported
  • Import Status: Recurring Donations Import Status

1. Add Field Mappings for the Recurring Donations  Object Group:

• Select Recurring Donations Type (Recurring_Donations_Type__c), and map it to Recurring Donations Type (npsp__Recurring_Donations_Type__c)
  • Repeat for all fields to be mapped.

Notes:

• You will need to create another Object Group and mapping if you wish to import to Account1.
• I would recommend setting a value and mapping for Recurring Donation Name field else it will default to the Recurring Donation ID.

I also have screenshots if they would be helpful.

Nonprofit Success Pack version 3.162 will begin being pushed to production orgs tonight. Full release details are available at https://github.com/SalesforceFoundation/Cumulus/releases/tag/rel/3.162

Critical Changes

• Updates the NPSP Data Import page layout to include the new Advanced Mapping GAU Allocation and Opportunity Contact Role (for soft credits) fields. See the documentation for more information about adding these fields to your NPSP Data Import page layout: https://powerofus.force.com/s/article/NPSP-Setup-Before-You-Begin#ariaid-title5

Changes

• To support future pilot programs, we added support for feature enablement.
• We removed a duplicate aura component. Thanks to Chris Duncan for identifying this duplication!
• Batch Data Entry has been replaced by Batch Gift Entry, and the link to BDE was removed from NPSP Settings. For more information see https://powerofus.force.com/s/article/NPSP-Batch-Data-Entry-Statement.
• In order to prevent an error, we updated the execution order of the REL_Relationships_Con_TDTM class to 2 and the CON_ContactMerge_TDTM class to 3.
• We now display the NPSP Settings page and run Health Check when a trigger handler has an undefined action. Thank you Manik for your contribution!

NPSP Data Import Enhancements

• We updated an NPSP Data Import processing or Dry Run error message to be clearer about why a record didn't process correctly.
• We updated the information on the NPSP Data Import and Advanced Mapping screens to make them clearer.
• Users can now navigate to other Salesforce tabs while a new Field Mapping is being created.
• We updated Field Mapping in Advanced Mapping so an NPSP Data Import picklist must have boolean values if it’s mapping to a checkbox field. When a user selects a picklist as the NPSP Data Import field that maps to a checkbox on the target object, the picklist options must be True or False.
• We fixed a bug in NPSP's automation to create a reciprocal Relationship. Now with Advanced Mapping, users can create a Relationship record between two Contacts.

Issues Closed

#1663: As a user, when I use the data importer to associate contact2 with contact1's household, I'd like to be able to specify a relationship between contact1 and contact2

#2742: Trigger Handler Null Pointer Exception when the Trigger Action is empty

#4291: Component dataProviderInterface duplicated

#4482: When syncing a Payment Allocation back to the Opportunity there shouldn't be a percent on the Default GAU for the Opportunity Allocation.

New Metadata

Apex Class:

• TDTM_ObjectDataGateway_TEST

Deleted Metadata

• dataProviderInterfaceInterface.intf
• dataProviderInterfaceInterface.intf-meta.xml

github.com