Nonprofit Cloud Consultant Nonprofit-Cloud-Consultant Book

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.

References:

Salesforce Shield Platform Encryption Documentation

Nonprofit Success Pack (NPSP) Documentation on Data Import and Soft Credits

To allow prospective volunteers to fill out their volunteer application online:

Set up the Volunteers for Salesforce Volunteer Signup Form: This form can be embedded on the nonprofit's website, allowing prospective volunteers to submit their information directly into Salesforce.

This approach leverages the existing Volunteers for Salesforce functionality, making it easy to capture and manage volunteer applications.

References:

Salesforce Volunteers for Salesforce Documentation

Salesforce Trailhead: Setting Up Volunteers for Salesforce

When setting up a sandbox strategy for a nonprofit implementation project involving two major development initiatives, it is essential to use separate sandboxes for different purposes. The key purposes include Quality Assurance, Staging, and Development. Here’s why:

Quality Assurance (QA):

QA sandboxes are used to test new features and functionalities to ensure they work as expected.

This environment helps identify and fix bugs before the changes are moved to production.

Staging:

A staging sandbox is a replica of the production environment.

It is used for final testing and validation of new features, configurations, and data migrations.

Ensures that everything works correctly in an environment that closely mimics production.

Development:

Development sandboxes are used by developers to build and test new features.

Each developer can have their own sandbox to avoid conflicts with others’ work.

Using separate sandboxes for these purposes ensures a clear and organized development process, reduces the risk of conflicts, and helps maintain a stable production environment.

References:

Salesforce Documentation: Sandbox Types and Templates

Salesforce Trailhead: Developing in Sandboxes

To allow volunteers to log their own hours in Volunteers for Salesforce, the consultant should propose setting up the Volunteers Personal Site or adding a Log Volunteer Hours section on the nonprofit’s website.

Volunteers Personal Site:

This site allows volunteers to log in and manage their hours directly within Salesforce.

Steps to Set Up:

Navigate to Setup > Sites.

Create a new site and configure it to use the Volunteers for Salesforce functionality.

Add the Volunteers Personal Site tab and configure the permissions.

Direct volunteers to use this site to log their hours.

Log Volunteer Hours Section on Website:

Create a section on the nonprofit’s website where volunteers can log their hours.

Steps to Set Up:

Design a web form that captures the volunteer's job or shift and the hours worked.

Use Salesforce Web-to-Case or Web-to-Lead to capture this data and create records in Salesforce.

Direct volunteers to this section to submit their hours.

Both solutions provide a user-friendly way for volunteers to log their hours without requiring manual entry by staff.