Online Nonprofit-Cloud-Consultant Questions Video

When a nonprofit organization creates a custom Opportunity name for all organization donations, the consultant should discuss the following considerations:

Using the "Refresh Name" Action (B):

The organization should use the "Refresh Name" action to change existing Opportunities to the new naming convention. This action ensures that the custom naming convention is applied correctly.

Navigate to the Opportunity record.

Click on the "Refresh Name" button to update the Opportunity name according to the new naming convention.

Using the "Refresh All Opportunity Names" Button in Bulk Data Processes (C):

For bulk updates, the organization should use the "Refresh All Opportunity Names" button available in Bulk Data Processes.

Go to NPSP Settings.

Under Bulk Data Processes, find the "Refresh All Opportunity Names" button.

Click on it to update all existing Opportunities to the new naming convention in bulk.

These methods ensure that the custom naming convention is applied consistently across all existing Opportunity records, maintaining data integrity and consistency within the Salesforce org​​.

When encountering an error at run time indicating that a record couldn't be updated during a Customizable Rollup operation, it is often due to validation rules on the target field that prevent the update.

Check the Target Field for Validation Rules:

Navigate to Setup > Object Manager.

Select the object that contains the target field.

Go to Fields & Relationships and find the target field.

Review any validation rules associated with this field to ensure they are not causing the update to fail.

Modify or Disable Validation Rules:

If a validation rule is causing the issue, consider modifying it to allow updates during the rollup operation.

Alternatively, temporarily disable the validation rule, perform the rollup operation, and then re-enable the validation rule.

Test the Rollup Operation:

After addressing any validation rules, rerun the Customizable Rollup operation to ensure that the error is resolved.

Monitor the operation to confirm that the updates are processed correctly without triggering validation errors.

By ensuring that validation rules on the target field do not interfere with the rollup operation, the consultant can resolve the error and ensure smooth data processing.

References:

CertGod Nonprofit Cloud Consultant Guide

When setting up Volunteers for Salesforce in an international context, it's important to ensure that volunteer jobs and shifts reflect the local time zones accurately. Here’s how to configure this:

Navigate to Volunteers for Salesforce Settings:

Go to Setup.

Type "Volunteers for Salesforce" in the Quick Find box and select it.

Configure Volunteer Jobs:

Create Volunteer Jobs for each country.

For each job, set the "Website Time Zone" field to the local time zone where the job will take place.

Adjust Volunteer Shift Times:

When creating volunteer shifts, ensure the start and end times are set according to the local time zone.

Update Website Information:

Inform volunteers about the time zone settings on the volunteer signup pages if necessary.

References:

"Volunteers for Salesforce Setup Guide" from Salesforce Help: Volunteers for Salesforce

"Managing Volunteer Shifts and Jobs" from Salesforce.org: Volunteer Management

To transition from Person Accounts to the Household Account model in NPSP and avoid interacting with Person Accounts, the recommended approach is to migrate to a new Salesforce NPSP org. Here’s how:

Apply for a New Salesforce NPSP Org:

Contact Salesforce to apply for a new NPSP org.

Ensure the organization qualifies for the NPSP and request the necessary licenses.

Request License Transfer:

Work with Salesforce support to transfer existing licenses from the current org to the new NPSP org.

Export Data from Current Org:

Export all Person Account data, including Contacts, Accounts, Opportunities, and any other relevant records.

Use Salesforce Data Loader or another export tool to ensure a complete data export.

Prepare Data for Import:

Clean and prepare the exported data for import into the new org.

Map Person Account data to the appropriate fields in the Household Account model.

Import Data into New NPSP Org:

Use the NPSP Data Importer or Data Loader to import the cleaned data into the new org.

Ensure that all relationships and references are correctly mapped and maintained during the import process.

This method ensures a clean transition to the Household Account model without the complications of dealing with Person Accounts in the original org.

References:

Salesforce NPSP Documentation: Account Models

Salesforce Trailhead: Data Import Strategies