The NPSP template can be installed in any org (i.e. Developer or Partner Enterprise) from the Salesforce AppExchange.
NPSP: DupeBlocker
Feature or Triggering Action | Issue |
Scenario Rules |
Multiple Email and Phone fields
|
Deployed Account Scenario with Match on Insert Action: “Do Not Insert”
Inserting a Contact that results in a duplicate Account being created |
|
Insert Action will not trigger for new Contacts |
As part of the Contact insert a “Household” Account is automatically inserted and the Contact is associated with that new Account. Since DupeBlocker will only fire for the first object created in the same Apex Batch, it will not trigger for the Contact, since the Account is created first. It also seems that even when you add a new Contact to an EXISTING Household Account DupeBlocker will still not fire for the Contact as an update is done for the Account (Number of Household Members and Formal/Informal Greeting fields updated).
More details can be found in the following Validity Community post: |
Merging Contacts from a Warning |
When merging Contacts, when the non-master Contact is deleted the Account the Contact was associated with will be renamed “Anonymous Household” vs. being deleted.
This DOES not happen however when using the custom NPSP merge option only available in Lightning POSSIBLE WORKAROUND: Simply look for the Anonymous Household Account after the merge is complete, should see it at the top of the list of recent items, then manually delete it. |
Auto-Merging Accounts |
NPSP trigger is causing Auto-merge to fail with the following error for Household Accounts created automatically when a Contact is inserted. Even if this did work, it could result in the Contact NOT being created. *** Exception Message: Merge failed. First exception on row 0 with id 001f200001XX3q1AAD; first error: DELETE_FAILED, npsp.TDTM_Account: execution of AfterDelete caused by: System.DmlException: Update failed. First exception on row 0 with id 001f200001XX3q1AAD; first error: SELF_REFERENCE_FROM_TRIGGER, Object 001f200001XX3q1AAD is currently in a merge operation, therefore a trigger can not update it.: [] POSSIBLE WORKAROUND: Will need to change the “Match on Insert” action to Report Duplicate. Could also change to “Do Not Insert” but then will get the unformatted block message as noted in item #2 above. NOTE: If wanting auto-merge to work for NON Household accounts could add an object filter where Account Name “does not end with” household. This would stop the errors from being sent when the Auto-Merge fails for Household Accounts. |
NPSP: PeopleImport
Function | Issue |
General |
PeopleImport is designed to work with the standard B2B Salesforce model. When importing Contacts an Account Name needs to be mapped so that an Account can be created to associate the new Contact with. The “Household” Account recordtype will also need to be mapped, unless it is the users default record type on their profile. Since the NPSP model automatically creates an Account when inserting a new Contact, NPSP users would typically NOT have an Account Name or recordtypeid in their input file, and therefore would not be able to use PeopleImport to import new Contacts. POSSIBLE WORKAROUNDS:
|
NPSP: DemandTools
Module | Issue |
All Maintenance Modules |
Should work
|
Lead Conversion |
Note: If opting to NOT use Lead Conversion to process conversions it can still be used to find matches then the results can be exported to a file so that the user knows which records to convert in the UI with the NPSP custom convert option. |
Find/Report ID's | Should work |
Single Table Dedupe |
When merging Contacts, when the non-master Contact is deleted the Account the Contact was associated with will be renamed “Anonymous Household” vs. being deleted.
NOTE: Donations are moved from any non-master contacts to the master contact, so the Anonymous Household created after merging WILL NOT contain any donations and can be deleted. Anonymous Households are also created when Contacts are directly deleted that contain donations. Attempts to delete an Anonymous Household that contains donations will be blocked by Salesforce. POSSIBLE WORKAROUNDS:
|
Single Table Dedupe Field Rules on Email or Phone Fields |
Users may get unexpected results when using Field Rules to update the standard email or phone field due to Workflows that auto-populate these fields based on the “Preferred Email”.
|