Free Nonprofit-Cloud-Consultant Questions Attempt

To track specific funds associated with gifts from individuals and organizations in NPSP, the consultant should create General Accounting Unit (GAU) records for each of the funds and associate them with the Opportunity by GAU Allocation record amounts.

Steps:

Log in to Salesforce: Access the Salesforce org with NPSP installed.

Create GAU Records:

Navigate to the App Launcher and search for "General Accounting Units".

Click "New" to create a new GAU record for each fund.

Fill in the necessary details such as GAU Name, Description, and any other relevant information.

Save the GAU records.

Associate GAUs with Opportunities:

Navigate to the Opportunity related to the donation.

In the Opportunity record, find the "GAU Allocations" related list.

Click "New" to create a new GAU Allocation.

Select the appropriate GAU record from the lookup field.

Enter the allocation amount and any other necessary details.

Save the GAU Allocation record.

Reporting: Use standard or custom reports to track and report on GAU Allocations for reconciliation with the finance system.

References:

CertGod Nonprofit Cloud Consultant Guide

A common cause of the NPSP (Nonprofit Success Pack) upgrade failing when run in Production, despite no issues in the sandbox, is not having adequate test code coverage. This is essential for successful deployments in Salesforce environments.

Test Code Coverage:

Salesforce requires a minimum of 75% test code coverage for deploying Apex code to a production environment.

This means that automated tests must cover at least 75% of the codebase, ensuring that most functionalities are validated and reducing the risk of errors during deployment.

Sandbox vs. Production Differences:

Sandbox environments often have less data and different configurations compared to production, which might not fully mimic real-world scenarios.

In production, there could be additional triggers, validation rules, or workflows that are not present or not active in the sandbox.

Mitigating Upgrade Failures:

Ensure that all custom code, including Apex triggers, classes, and batch processes, has adequate test coverage.

Review and test all dependent packages and configurations in a full sandbox environment that closely replicates the production setup.

Additional Considerations:

Conduct a comprehensive review of all customizations and integrations.

Run the NPSP Health Check Tool and Salesforce Optimizer in sandbox before the actual upgrade to identify potential issues.

References:

CertGod Nonprofit Cloud Consultant study guide: "Not having adequate test code coverage"​​.

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.

Person Accounts were not designed to work with the Nonprofit Success Pack (NPSP) and are not supported for use with NPSP. The best practice is to avoid using Person Accounts in NPSP. Here’s why:

Incompatibility with NPSP Features:

NPSP is designed to use the Household Account model to manage individual donors and contacts.

Person Accounts can conflict with NPSP’s data model and features, such as customizable rollups and relationship management.

Limited Support:

Salesforce and the NPSP community provide limited support for Person Accounts within the NPSP context.

Using Person Accounts may result in difficulties obtaining support and resolving issues that arise.

Best Practices for Nonprofits:

Nonprofits are encouraged to use the Household Account model to track individual contributors and volunteers.

This model offers better integration with NPSP’s built-in functionalities, such as donation tracking, engagement plans, and reporting.

Data Model Alignment:

Aligning with the Household Account model ensures data consistency and full utilization of NPSP features.

It simplifies data management and reporting by adhering to the NPSP’s standardized structure.

References:

Salesforce NPSP Documentation: Account Models

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics