Known Issues Between NPSP Template and Validity Tools
DISCLAIMER: Customers with NPSP implementation should run their own tests in their environments to accurately determine issues that may arise. Testing for NPSP was done on the household account model only.
General Notes:
- Household Accounts are automatically created when a Contact is inserted.
- Merging Contacts and Accounts (both in DemandTools and DupeBlocker) works using Salesforce’s API Merge call
- Merging Accounts that result in duplicate Contacts can result in “incorrect” formal/informal greetings
- When merging Contacts, non-master Contact Household Account is NOT deleted but rather renamed “Anonymous Household”
- Can be safely deleted after the merge
- Multiple Email (Personal Email, Work Email & Alternate Email) and Phone Fields (Home phone, Other Phone, Mobile and Work Phone)
- Need to ensure the correct/desired ones are used for matching.
- If the associated NPSP workflow rule is activated, then the standard Email/Phone field is auto-populated to whichever email is selected as the “Preferred Email”.
Known Issues by Product:
DupeBlocker
- Contact Insert: Unformatted message in red (not the typical formatted blocking message) and “Bypass Block” button not available when an auto-created Household Account is blocked via an Account Scenario
- Contact Insert: Will not trigger the “Match on Insert Action” (regardless of whether it is created on an existing Account or not)
- Account auto-merge fails due to an NPSP trigger when a Household Account is created automatically from a Contact insert
PeopleImport
- Requires a column in the input file that specifies the Household Account name (mapping to the Account Name is required)
- The “Household” Account record type will also need to be mapped, unless it is the users default record type on their profile
DemandTools
- Lead Conversion will create any new Accounts using the Lead Company field vs. auto-creating a Household Account for each new Contact
- NPSP does have its own Lead Conversion button that can be used to convert Leads to NEW Contacts and Household Accounts.
- Single Table Dedupe Email/Phone based Field Rules may not perform as expected due to NPSP auto updating these fields via workflow rules
Additional Resources:
- Full NPSP documentation
- More information on how Formal/Informal greetings work in NPSP
- More information on the NPSP custom merge button (available in Lightning only and UI only):
- More information on NPSP’s custom convert button
