When implementing Salesforce Shield Platform Encryption with NPSP, there are several key considerations:
Role Name Field on Partial Soft Credit Object:
If the Role Name field on the NPSP Partial Soft Credit object is encrypted, the nightly Soft Credit rollups will fail. This is because the rollup process relies on accessing this field, and encryption can interfere with its functionality.
MergeContacts List Button:
The NPSP MergeContacts list button on Contact list views will fail if the Contact Name is encrypted. The merging process requires access to the Contact Name to identify and merge records accurately, which encryption can prevent.
Custom Unique Id Matching:
NPSP Data Import cannot perform Custom Unique Id matching on Accounts and Contacts if the field used for matching is encrypted. This limitation arises because the encryption prevents the import process from accurately comparing and matching the encrypted values.
These considerations highlight the impact of encryption on certain NPSP functionalities, and it is important to plan accordingly when implementing Shield Platform Encryption.
Reference:
Salesforce Shield Platform Encryption Documentation
Nonprofit Success Pack (NPSP) Documentation on Data Import and Soft Credits