Salesforce Shield Platform Encryption provides high-level security, but it has significant "functional trade- offs" because the system cannot "read" encrypted data in the same way it reads plain text for certain automated processes.
Three Critical NPSP Considerations:
* Soft Credit Rollup Failure (C): NPSP's Customizable Rollups often use the Role Name on the Partial Soft Credit object to determine how to aggregate credits. Because encryption prevents the database from performing "Group By" or "Where" queries on that field effectively, the nightly rollup jobs will fail to process those credits.
* Merge Contacts Failure (D): The NPSP Contact Merge tool relies on identifying and comparing names. If the Contact Name is encrypted, the SOSL/SOQL queries used by the "Merge" button cannot properly index or find the records, rendering the specialized NPSP merge interface unusable.
* Data Import Matching (E): The NPSP Data Importer relies heavily on "Matching Rules." If you are trying to match a legacy donor ID or a custom unique ID that has been encrypted, the system cannot perform the "Exact Match" check needed to prevent duplicates during the import process.
Why other options are incorrect:
* Option A: Standard address fields on Account/Contact can be encrypted with Shield, so this is not a limitation.
* Option B: The Data Import object does not support "all fields" for encryption; like most objects, it has specific supported field types and limits.