Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (SU24) Questions and Answers

https://powerofus.force.com/s/article/NPSP-Configure-Automated-Soft-Credits#ariaid-title6

To automatically credit the spouse for a donation in NPSP, the consultant should recommend enabling Automatic Soft Credit for household members in the NPSP settings. This setting ensures that any donation made by a household member is automatically soft credited to other members of the household.

Steps to Enable:

Navigate to NPSP Settings:

Go to Setup -> NPSP Settings.

Enable Automatic Soft Credits:

Under Donations -> Soft Credits, enable the option for Automatic Soft Credit for Household Members.

Verify Soft Credits:

Check the Opportunity records to ensure that soft credits are correctly applied to household members.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Manage Soft Credits in Nonprofit Success Pack (NPSP)

Top of Form

Bottom of Form

To automatically add donors to the Capital Campaign when they contribute to the Capital Fund, the following steps should be taken:

Populate the Primary Campaign Source Field:

The Primary Campaign Source field on the Opportunity record links the donation to a specific Campaign.

This ensures that donations are tracked under the correct Campaign and allows for accurate reporting and analysis.

Enable Automatic Campaign Member Management:

NPSP (Nonprofit Success Pack) provides a feature for automatic campaign member management.

This feature automatically adds donors to Campaigns based on their donations, streamlining the process and reducing manual work.

To enable this, navigate to NPSP Settings -> Donations -> Automatic Campaign Member Management and activate the feature.

Steps to Implement:

Step 1: Ensure that the Primary Campaign Source field is populated on the Opportunity record whenever a donation is made to the Capital Fund.

Step 2: Enable the Automatic Campaign Member Management feature in NPSP settings to automate the addition of Campaign Members.

Benefits:

Efficiency: Reduces the need for manual updates, saving time and effort.

Accuracy: Ensures that all relevant donations are correctly attributed to the appropriate Campaign, improving reporting and donor management.

References:

CertGod Nonprofit Cloud Consultant study guide: "Enable the Automatic Campaign Member Management in NPSP settings and populate the Primary Campaign Source field on the Opportunity record"【22:8†source】.

When using Marketing Cloud Connect and enabling tracking, the type of data available for reporting using Salesforce reports includes Email Studio Send details. Here’s why:

Marketing Cloud Connect:

Marketing Cloud Connect integrates Marketing Cloud with Salesforce, enabling data synchronization and reporting.

This integration allows Salesforce to pull tracking data from various Marketing Cloud modules into Salesforce reports.

Email Studio Send Details:

Email Studio Send details include data such as email opens, clicks, bounces, and other email performance metrics.

This data is critical for understanding the engagement and effectiveness of email campaigns, and it is available for reporting within Salesforce.

References:

Salesforce Marketing Cloud Connect Documentation

Salesforce Email Studio Reporting Guide

Salesforce recommends using V2MOM (Vision, Values, Methods, Obstacles, and Measures) with customers in the requirements-gathering phase of a project to achieve organizational alignment. Here’s how V2MOM helps:

Vision:

Define what you want to achieve. This provides a clear direction for the project.

Values:

Identify what is important about the vision and why it matters. This aligns the project goals with the organization's core values.

Methods:

Outline the steps to achieve the vision. This ensures everyone understands the approach and processes to be followed.

Obstacles:

Recognize potential challenges and how to address them. This prepares the team to handle issues proactively.

Measures:

Determine how success will be measured. This provides clear criteria for evaluating progress and outcomes.

Using V2MOM ensures that all stakeholders are aligned with the project’s goals, values, methods, challenges, and success metrics, fostering a unified approach to project execution.

References:

Salesforce V2MOM Framework: Marc Benioff’s V2MOM

Salesforce Trailhead: Define Your Vision with V2MOM

To retain the legacy system's 150 donation appeal source codes as historical data in NPSP, you should follow these steps:

Create Campaigns for Each Legacy Source Code:

Navigate to the Campaigns tab in Salesforce.

Create a new Campaign for each of the 150 legacy source codes.

Name the Campaigns according to the source codes for easy identification.

Prepare Your Import Data:

Ensure that your import data includes a column for Campaigns, where you can map each donation to the corresponding legacy source code Campaign.

Import Contacts and Opportunities:

Use the Data Import Wizard or Data Loader to import your Contacts and Opportunities.

During the import process, map the source code field in your data to the appropriate Campaign in Salesforce.

Relate Contacts and Opportunities to Campaigns:

Ensure that each Contact and Opportunity record is related to the correct Campaign representing the legacy source code.

By organizing your legacy source codes into Campaigns and mapping your import data accordingly, you can effectively retain and manage historical donation appeal source codes in NPSP.

References:

Nonprofit Success Pack (NPSP) Data Import documentation.

Salesforce documentation on Campaigns and data import processes.

To allow a fundraiser to easily track and update her gift asks for donation solicitations, using Path is a suitable solution in Salesforce. Here’s how to configure and use Path for this requirement:

Enable Path:

Navigate to Setup and type "Path" in the Quick Find box.

Click on Path Settings and enable Path if it is not already enabled.

Create a Path:

Click New Path and follow the steps to create a new Path.

Select the Opportunity object since you want to track donation solicitations.

Define the stages of your solicitation process (e.g., Identification, Cultivation, Solicitation, Stewardship).

Configure Key Fields and Guidance:

For each stage, specify key fields that the fundraiser should complete.

Add guidance for success to provide tips and best practices for each stage.

Assign the Path to a Record Type:

If using record types, ensure the Path is assigned to the correct record type for your donation solicitations.

Use Path:

On the Opportunity record page, the fundraiser can now see the Path at the top of the record.

She can track her progress, update fields, and follow the guidance provided at each stage.

Using Path helps the fundraiser to visualize the stages of the solicitation process, ensuring she can track and update gift asks effectively.

References:

Salesforce Path Documentation: Path in Salesforce.

To streamline the import of donations made by nonprofit volunteers using NPSP Data Import features, the following steps are recommended:

Create a Batch and Map Opportunity Primary Contact on First and Last Name:

When creating a data import batch, you can map the Opportunity Primary Contact based on the First and Last Name. This ensures that the donation is linked to the correct contact in Salesforce.

Create a Batch and Match Contact on First and Last Name:

During the import process, create a batch and use the matching criteria based on the Contact's First and Last Name. This helps in accurately matching the donations to the existing contacts in Salesforce, reducing duplicate records and maintaining data integrity.

Steps to Implement:

Navigate to NPSP Data Import.

Create a new Batch.

Map the fields appropriately, ensuring the Opportunity Primary Contact and Contact matching criteria are based on First and Last Name.

Validate the mapping and run the batch to import the donation data.

These features help automate and streamline the data import process, ensuring accurate and efficient data management.

References:

Nonprofit Success Pack (NPSP) Documentation: Data Import

Salesforce Help: Managing Batches and Data Import

To create a report that shows Opportunity and General Accounting Unit (GAU) custom field data for gifts to the "General Fund" GAU and adds filters to show only the gifts connected to the "Annual Campaign," the consultant should use the "GAU Allocations with Opportunity" report type. This report type allows for filtering on both Opportunity and GAU Allocation fields.

Steps to Create the Report:

Select Report Type:

Go to the Reports tab and create a new report using the "GAU Allocations with Opportunity" report type.

Add Filters:

Filter on the Opportunity object for the Primary Campaign Source = "Annual Campaign."

Filter on the GAU Allocation object for General Accounting Unit = "General Fund."

Customize Report:

Add the necessary fields from both the Opportunity and GAU Allocation objects to the report layout.

Save and run the report to view the desired data.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Create and Customize Reports in Salesforce

To configure Salesforce to handle recurring volunteer schedules, the Volunteer Recurrence Schedules feature in Volunteers for Salesforce (V4S) is the ideal solution. Here's a step-by-step guide:

Install Volunteers for Salesforce: If not already installed, you need to install the Volunteers for Salesforce package from the Salesforce AppExchange.

Navigate to Volunteer Jobs: Go to the Volunteers tab and create or select a Volunteer Job that requires a recurring schedule.

Set Up Volunteer Recurrence Schedules:

In the Volunteer Job record, find the "Recurrence Schedules" related list.

Click "New Volunteer Recurrence Schedule."

Define the recurrence pattern, such as weekly, and specify the start and end times for the volunteer shifts.

Assign Volunteers to Recurrence Schedules:

Once the recurrence schedule is created, assign volunteers to this schedule.

Volunteers assigned to a recurrence schedule will automatically be registered for the specified shifts without the need to sign up repeatedly.

Review and Manage:

Periodically review the schedules to ensure they align with any changes in volunteer availability or job requirements.

By using Volunteer Recurrence Schedules, the nonprofit can efficiently manage volunteers who work on a regular basis without needing them to sign up for each shift manually. This feature ensures that the volunteer management process is streamlined and volunteers have a consistent schedule.

References:

Salesforce Volunteers for Salesforce Documentation: This official documentation provides detailed instructions on setting up and managing volunteer schedules. Salesforce V4S Documentation.

To quickly query data across multiple systems and get insights on any device about the impact the nonprofit is having, the consultant should recommend:

CRM Analytics (formerly known as Tableau CRM or Einstein Analytics):

CRM Analytics allows for advanced data analysis, visualization, and reporting. It can integrate data from multiple Salesforce objects and external sources, providing comprehensive insights across systems. It is designed to work seamlessly on various devices, ensuring accessibility and usability.

To create a report of all memberships that will expire in exactly 30 days, the consultant should filter the report on Membership End Date using the condition "Membership End Date equals NEXT 30 DAYS and does not equal NEXT 29 DAYS." This ensures that the report includes only those memberships expiring exactly on the 30th day, excluding those that expire earlier or later.

References:

Salesforce Reporting and Dashboards Guide

Salesforce Nonprofit Cloud Consultant Study Guide

https://trailhead.salesforce.com/content/learn/modules/program-management-with-nonprofit-cloud/manage-nonprofit-programs-with-salesforce

To track each program and the status of youth enrolled in the program using the Program Management Module (PMM) in Salesforce, the consultant should use the "Programs" and "Program Engagements" objects.

Key Features:

Programs: This object represents the various programs offered by the nonprofit. Each program can have multiple engagements and activities associated with it.

Program Engagements: This object tracks the involvement of individuals (youth in this case) in specific programs. It allows the nonprofit to monitor the status and progress of each participant within the program.

Steps to Implement:

Set Up Programs:

Navigate to the Programs tab.

Create records for each after-school program offered by the nonprofit.

Track Engagements:

Navigate to the Program Engagements tab.

Create records for each youth enrolled in the programs, linking them to the appropriate program and tracking their status.

References:

Salesforce Program Management Module Documentation

Salesforce Trailhead: Program Management for Nonprofits

To track grant lifecycles using the Nonprofit Success Pack (NPSP), including assigning actions to staff members, tracking applications, reporting deadlines, and summarizing the total amount awarded with payments, the consultant should model the components as follows:

Payments = Opportunities with Payments:

Use the Opportunities object in Salesforce to track each grant awarded.

For each Opportunity, create related Payment records to track individual disbursements or installments of the grant amount.

Applications = Deliverables:

Utilize the Deliverables object to track the application process for grants.

Create Deliverable records to capture key details such as submission deadlines, requirements, and statuses.

Reporting Deadlines = Deliverables:

Similar to applications, use the Deliverables object to track reporting deadlines.

Create Deliverable records for each required report, specifying due dates and completion statuses.

Actions = Activities:

Use the Activities object to assign tasks and actions to staff members.

Create Task records for actions related to the grant, such as follow-ups, meetings, and communications.

This configuration ensures that all aspects of the grant lifecycle are tracked effectively within Salesforce, leveraging NPSP's capabilities to manage opportunities, payments, deliverables, and activities.

References:

Salesforce Nonprofit Success Pack Documentation: Detailed instructions on using Opportunities, Payments, Deliverables, and Activities in NPSP.

Salesforce Help Documentation: Opportunities, Activities, Payments, Deliverables.

Top of Form

Bottom of Form

https://www.freecram.com/question/Salesforce.Nonprofit-Cloud-Consultant.v2020-09-19.q37/the-development-director-at-a-nonprofit-needs-to-track-grant-lifecycles-using-the-npsp-including-assignin

https://trailhead.salesforce.com/content/learn/modules/project-risk-management-for-partners/identify-ass ess-address-risk

In project management, the three elements impacted by change that cause risk are cost, quality, and time. These elements are often referred to as the project management triangle or triple constraint.

Elements Impacted by Change:

Cost: Changes can lead to increased project costs, affecting the budget and financial resources.

Quality: Changes can impact the quality of the project deliverables, potentially leading to rework or reduced standards.

Time: Changes can affect the project timeline, causing delays and extending the project schedule.

Steps for Risk Mitigation:

Identify Potential Risks:

Conduct a risk assessment to identify potential changes that could impact cost, quality, or time.

Develop Mitigation Strategies:

Create plans to mitigate identified risks, including contingency plans and resource allocations.

Monitor and Control:

Regularly monitor the project for changes and adjust plans as necessary to manage risks effectively.

References:

Salesforce Project Management Best Practices

Salesforce Trailhead: Risk Management in Project Management

When preparing for an upcoming NPSP release and wanting to validate customizations, the consultant can take the following approaches:

Test Customizations in an Updated Sandbox (A):

Update the sandbox to the latest release of NPSP.

Deploy the customizations to the updated sandbox and thoroughly test them to ensure compatibility with the new release.

Configure a Scratch Org with NPSP Dependency and Test Customizations (D):

Set up a new scratch org using Salesforce DX and include the NPSP dependency.

Deploy the customizations to the scratch org and test them to validate their functionality with the latest NPSP release.

Steps to Implement:

Update Sandbox:

Refresh the sandbox and ensure it is on the same version as the upcoming NPSP release.

Deploy and test the customizations in the sandbox environment.

Set Up Scratch Org:

Use Salesforce DX to create a scratch org with the necessary NPSP configurations.

Deploy the customizations to the scratch org and perform testing.

References:

Salesforce Developer Documentation on Sandboxes and Scratch Orgs

Salesforce Trailhead: Salesforce DX and Development Environments

To ensure that the membership rollups in NPSP (Nonprofit Success Pack) work properly for managing a membership program, the consultant needs to configure the following items:

Select the membership record type for membership rollups:

This involves defining which Opportunity record types are used for membership donations. This configuration allows the NPSP to properly identify and roll up membership donations.

V2MOM (Vision, Values, Methods, Obstacles, and Measures) is a framework used by Salesforce to align teams and ensure successful project outcomes. The recommended elements for a V2MOM include:

Vision:

Defines what you want to achieve.

It sets the direction and purpose of the project or initiative.

Example: "To increase donor engagement by 20% over the next fiscal year."

Metrics (Measures):

Describes how you measure success.

Includes quantifiable indicators that help track progress toward the Vision.

Example: "Number of new donors acquired, donor retention rate, total funds raised."

Values:

Although not explicitly listed as an answer option, values are an integral part of the V2MOM framework. They define what is important and guide the behaviors needed to achieve the Vision.

Methods:

Specifies the actions and steps needed to achieve the Vision.

Example: "Implement a new donor management system, conduct quarterly donor engagement surveys."

Obstacles:

Identifies potential challenges and how to overcome them.

Example: "Limited staff resources, data migration issues."

Inclusion of Metrics and Vision:

Metrics and Vision are critical as they set the overall goal and how success will be measured, ensuring clarity and alignment across the team.

References:

CertGod Nonprofit Cloud Consultant study guide: "Vision and Metrics are essential components of a Salesforce-recommended V2MOM"【22:5†source】.

myTrailhead is the best solution for a nonprofit organization that wants to train and test its employees on various skills such as brand messaging, creating support cases for IT, and publishing online videos. myTrailhead provides a customized learning experience that can be tailored to specific needs and allows for interactive and engaging training modules. This solution also includes testing capabilities to assess employee understanding and track progress over time.

References:

Nonprofit Cloud Consultant Guide: myTrailhead is recommended for creating customized and engaging training modules that can be tracked and assessed over time​​​​.

For tracking and reviewing scholarship applications and recording scholarship recipients, award amounts, and dates, the consultant should recommend setting up the Outbound Funds Module. This module is designed for managing funds that are disbursed, such as grants and scholarships. By connecting the Funding Request to Contacts for the recipient, the nonprofit can effectively manage and track all related information in a structured and organized manner.

References:

Salesforce Outbound Funds Module Documentation

Salesforce Nonprofit Cloud Consultant Study Guide

The likely cause of encountering a 500 server error when trying to map additional objects and fields with Advanced Mapping is attempting to map to an unsupported field type. Advanced Mapping in Salesforce has specific requirements and limitations regarding the types of fields that can be mapped.

Key Considerations:

Supported Field Types: Ensure that the target fields are of supported types, such as text, currency, number, date, or address fields.

Field Compatibility: Unsupported field types, such as certain complex formula fields or picklists, can cause errors during the mapping process.

Steps to Resolve:

Review Field Types:

Verify the field types of the target fields you are trying to map to ensure they are supported.

Check Documentation:

Refer to Salesforce documentation on Advanced Mapping to confirm the supported field types and any limitations.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Help: Configure Advanced Mapping for Data Import

https://powerofus.force.com/s/article/NPSP-Merging-Contacts

When using the NPSP Contact Merge functionality, any empty Household Accounts that do not have associated Contacts or Opportunities are automatically deleted. This is likely the cause of the reduction in the number of household accounts noticed by the system administrator.

Steps to Verify:

Check Merge Settings:

Review the settings and configuration of the NPSP Contact Merge process to understand its behavior regarding empty Household Accounts.

Review Audit Logs:

Check the Salesforce audit logs to see the details of the merge operations and confirm that empty Household Accounts were deleted.

Restore if Necessary:

If the deletion of empty Household Accounts was unintended, use data recovery options to restore any necessary records.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Merge Duplicate Records in Nonprofit Success Pack

When finalizing the plan for new features during a Salesforce major seasonal release window:

Verify Sandbox Release:

Check if the sandbox is on the same release as production to ensure consistency. Navigate to Setup -> Company Information in both environments to verify the release versions.

Review Sandbox Preview Instructions:

Salesforce provides sandbox preview instructions before a major release. Review these instructions to understand the new features and changes. Go to the Salesforce Release Readiness & Feature Adoption group on the Trailblazer Community for the latest updates.

Prepare Change Sets:

Create and validate change sets in the sandbox environment. Ensure all components are tested and ready for deployment after the production instance is upgraded.

Monitor Release Window:

Keep track of the Salesforce release window schedule to plan the deployment timing accordingly. Avoid deploying changes during the release window to prevent conflicts or unexpected issues.

References:

Salesforce Release Readiness & Feature Adoption Documentation

Salesforce Sandbox Preview Instructions

Salesforce Trailblazer Community for Release Updates

When encountering governor limit errors on a particular job in NPSP, the consultant should decrease the batch size for that job. Here's why:

Batch Size:

Salesforce has strict governor limits to ensure efficient resource usage. When a batch job hits these limits, it often indicates that the batch size is too large.

Decreasing the batch size reduces the number of records processed in each batch execution, thereby minimizing the chances of hitting governor limits.

This approach helps in completing the job successfully without exceeding platform limits.

References:

Salesforce Batch Apex Documentation

Salesforce Governor Limits Guide

These solutions provide precise and effective steps to address common issues and configuration needs within the Salesforce Nonprofit Cloud environment.

When an international nonprofit adds a translated Relationship picklist value but both Relationship records are displaying incorrectly, the likely cause is that the reciprocal relationship value is missing in the NPSP Settings tab.

Reciprocal Relationship Setup:

In NPSP (Nonprofit Success Pack), relationships between contacts often need to be reciprocal. For example, if Contact A is listed as "Parent" of Contact B, then Contact B should be automatically listed as "Child" of Contact A.

https://sfdo-docs.s3-us-west-2.amazonaws.com/npsp_reports.pdf

Reporting snapshots in Salesforce allow you to capture and store data at specific intervals, providing a way to track changes over time. However, they do not work retroactively, meaning you cannot use them to capture historical data before the snapshot was created. The snapshots only start capturing data from the point they are set up moving forward.

To address the development director's request, the consultant should consider alternative methods, such as creating reports with historical data that has already been captured or using a different tool that can analyze historical data for trends.

References:

Salesforce Help: Create Reporting Snapshots to Report on Historical Data

Salesforce Trailhead: Reporting Snapshots

https://trailhead.salesforce.com/en/content/learn/modules/search_solution_basics/search_solution_basics_optimizing

To improve search performance when migrating a large volume of donation data into the Nonprofit Success Pack (NPSP) for a nonprofit, the consultant should consider implementing Skinny Tables and Custom Index. Here is a detailed explanation:

Skinny Tables:

Skinny tables are a performance optimization technique in Salesforce used to improve the performance of read-only operations.

They are highly effective in environments with large volumes of data, such as the scenario described with 20 years of donation data and over 200,000 donations each year.

A skinny table contains frequently accessed fields and can significantly reduce query time.

Skinny tables are maintained by Salesforce and do not require changes to the custom object schema or existing queries.

They are particularly useful for scenarios involving complex reports and list views.

Custom Index:

Custom indexes enhance the performance of search queries in Salesforce.

Creating custom indexes on fields that are frequently used in search filters and conditions can drastically improve search performance.

Salesforce allows up to 25 custom indexes per object, which can be leveraged to optimize searches on key fields such as donor names, donation dates, and amounts.

Custom indexes should be applied to fields involved in frequently used WHERE clauses in SOQL queries.

References:

Salesforce documentation on Skinny Tables: Skinny Tables

Salesforce documentation on Custom Index: Custom Index

To pull a report showing all students in the program and their primary parent/guardian with the parent/guardian's cell phone and email, the consultant should use the "Contacts with or without Relationships" custom report type:

Custom Report Type:

Create a custom report type for "Contacts with or without Relationships."

This report type allows you to include related records, such as relationships between students (Contacts) and their primary parent/guardian.

Include Relevant Fields:

In the report, include fields for the student (Contact Name), their primary parent/guardian (related Contact), and the parent/guardian's cell phone and email.

Use the Relationships object to link students to their primary parent/guardian.

Filters and Sorting:

Apply necessary filters to ensure only relevant records are included.

Sort and group the data as needed to provide a clear view of students and their primary parent/guardian information.

References:

Salesforce Help: Custom Report Types

Nonprofit Success Pack (NPSP) Documentation: Managing Relationships

To allow volunteers to update their contact information on the nonprofit's website using Volunteers for Salesforce (V4S), follow these steps:

Access Setup:

Navigate to Setup in Salesforce.

Enable Guest User Permissions:

Go to Sites and Domains > Sites.

Click on the site label for your volunteer portal.

Click on Public Access Settings.

Under Field Permissions, make sure the necessary fields (like Contact fields) have the correct read and write permissions for the guest user profile.

Grant Guest Users Update Access:

Ensure that "Grant Guest Users Update Access" is checked. This setting allows guest users, typically those who access your site without logging in, to update certain fields like their contact information.

Test the Configuration:

As a volunteer, navigate to the relevant page on the nonprofit's website.

Test updating the contact information to ensure that the changes are correctly reflected in Salesforce.

This configuration allows volunteers to update their contact details directly from the website, ensuring that the information in Salesforce is always up-to-date.

References:

Salesforce Help Documentation: Sites and Public Access Settings.

https://powerofus.force.com/s/article/NPSP-BP-Getting -Started-Program-Management#week4

When migrating client and program data to the Program Management Module (PMM) in NPSP, it is important to use the appropriate tools for data import and deduplication to ensure data integrity and avoid duplication. The NPSP Data Importer is specifically designed for importing client information, including deduplication against existing records. The Data Import Wizard can be used for uploading program data, which may not require the same level of deduplication as client data.

Steps:

Prepare the client data, ensuring all necessary fields are included and formatted correctly.

Use the NPSP Data Importer to upload the client information, which includes built-in deduplication features to match against existing records.

Prepare the program data similarly, ensuring proper formatting and completeness.

Use the Data Import Wizard to upload the program data. This tool is suitable for handling bulk data uploads and does not inherently include deduplication, which is less critical for program data compared to client data.

References:

CertGod Nonprofit Cloud Consultant Guide: Discusses best practices for data migration and the tools available in NPSP for importing and deduplicating data​​.

Salesforce Documentation on NPSP Data Importer and Data Import Wizard: Provides detailed instructions on using these tools for data import.

https://powerofus.force.com/s/article/NPSP-Disable-Trigger-Handlers#ariaid-title3

When periodically importing a structured list of event registrations, it is crucial to ensure that the process is efficient and does not trigger unnecessary automation. Disabling TDTM (Table-Driven Trigger Management) for specific users is a recommended approach.

TDTM Overview:

TDTM allows for managing and controlling the execution of triggers in NPSP.

It provides flexibility to disable specific triggers or exclude certain users from trigger execution during bulk data imports.

Disabling TDTM for Specific Users:

By disabling TDTM for specific users, the import process can be streamlined without triggering unnecessary automation.

This approach ensures that data imports are efficient and reduces the risk of hitting system limits or performance issues.

Steps to Implement:

Navigate to NPSP Settings -> System Tools -> TDTM.

Add the usernames of the users who will be performing the imports to the "Usernames to Exclude" field.

Save the changes to ensure that TDTM triggers are disabled for these users during the import process.

Benefits:

Efficiency: Reduces the load on the system during bulk imports, ensuring faster and more reliable data processing.

Control: Maintains control over which triggers are executed, preventing unintended automation from affecting the imported data.

Additional Considerations:

Ensure that other necessary validations and processes are manually checked or re-enabled after the import if needed.

Monitor the data import process to ensure that it completes successfully without triggering unnecessary automation.

References:

CertGod Nonprofit Cloud Consultant study guide: "Disable TDTM for specific users"【22:18†source】.

To present active volunteer sites on a map that should be visible without logging in, the nonprofit can use Tableau Public. Here’s why:

Tableau Public:

Tableau Public is a free platform that allows users to create and share interactive data visualizations online.

It supports publishing maps and other visualizations that can be accessed publicly without requiring login credentials.

This tool is ideal for sharing information like volunteer site locations with a broad audience.

References:

Tableau Public Documentation

Salesforce and Tableau Integration Guide

(https://trailhead.salesforce.com/en/content/learn/modules/contact-and-account-settings-in-nonprofit-success-pack/merge-duplicate-contacts-and-accounts-npsp)

When encountering errors while trying to merge contacts using the NPSP Contact Merge tab, the following issues are likely causes:

Delete Access to Contacts:

The user needs to have delete access to the contacts being merged. Without the necessary permissions, the user will not be able to complete the merge operation.

Ensure that the user's profile or permission set includes delete permissions on the Contact object.

Unique External ID:

If a unique external ID is retained from the non-master contact, it can cause conflicts during the merge process. The system expects unique external IDs to remain unique, and retaining an ID from a record that is being merged (and effectively deleted) can create issues.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Merge Contact Permissions Guide

In the NPSP Data Import Template, the Account fields should contain:

Household-related data:

This data includes information pertinent to the household of the contacts, such as household name and address. Household-related data is crucial for managing and segmenting contacts within the NPSP.

To record the donation and credit it correctly in Salesforce Nonprofit Success Pack (NPSP):

Create a Relationship:

Ensure there is a relationship defined between the board member and the high-net-worth individual in Salesforce.

Go to the individual’s contact record.

Click on the "Related" tab and then on "New Relationship."

Fill in the board member's details as the related contact and specify the type of relationship (e.g., Introducer, Board Member).

Create the Donation Opportunity:

Go to the individual's contact record.

Click on the "New Opportunity" button.

Fill in the necessary details about the donation, such as amount, date, and any specific campaign or appeal it relates to.

Save the opportunity.

Add a Soft Credit Contact Role:

After saving the opportunity, go to the Opportunity record.

Click on "Related" and find the "Contact Roles" related list.

Click "New" to add a new contact role.

Select the board member’s contact.

Choose "Soft Credit" as the role type.

Save the contact role.

Verify Relationship and Soft Credit:

Ensure that the relationship between the board member and the individual is correctly recorded.

Verify that the soft credit for the board member is showing up correctly in the Opportunity record.

By following these steps, you ensure that the individual receives the hard credit for the donation while the board member receives a soft credit, allowing for proper tracking of the contribution's origin and recognition of the board member’s influence on the donation.

References:

Salesforce Nonprofit Success Pack (NPSP) documentation on managing donations and credits

CertGod Nonprofit Cloud Consultant guide​

Before installing Nonprofit Cloud Case Management into its production org, a nonprofit should consider the following prerequisites:

Enable My Domain:

My Domain is required for many Salesforce features, including those in Nonprofit Cloud Case Management.

Enabling My Domain allows customization of the Salesforce URL, enhances security, and is a prerequisite for some Salesforce features.

Ensure Appropriate Licenses Are Provisioned:

Nonprofit Cloud Case Management requires specific licenses to be available in the org.

Ensuring that the appropriate licenses are provisioned is crucial for enabling users to access the features and functionalities of Case Management.

References:

Salesforce Nonprofit Cloud Case Management Installation Guide

Salesforce My Domain Documentation

When using the Data Import Wizard with the NPSP Data Importer and noticing that the Mailing Street address field was missing on all records after import, one likely cause is incomplete data in the CSV file. Here’s a detailed explanation:

Check the CSV File:

Open the CSV file that was uploaded.

Verify if the Mailing Street address column contains complete and properly formatted data for all rows.

Ensure Completeness:

Ensure that there are no missing values or improperly formatted addresses in the Mailing Street column.

Even a single missing value can cause the entire column to be skipped during import.

Re-import Data:

Correct any incomplete or missing data in the CSV file.

Use the Data Import Wizard again to re-import the corrected file.

Verify Field Mappings:

During the import process, ensure that the Mailing Street field is correctly mapped to the appropriate Salesforce field.

By ensuring the completeness and correctness of the data in the CSV file, you can avoid issues where fields are missing after import.

References:

Salesforce Data Import Wizard Guide: Data Import Wizard.

To configure the Program Management Module (PMM) to record services provided to families, follow these steps:

Create Program Engagement Records:

Navigate to the "Program Engagements" tab.

Click "New" to create a new Program Engagement record.

Fill in the necessary details, ensuring to select the head of the household for the "Contact" field. This links the engagement to the primary contact within the family.

Select the Program:

In the Program Engagement record, select the relevant program that the family is engaged in. This helps in categorizing the services under specific programs.

Specify the Services:

Use the "Service Deliveries" related list to add services provided to the family. Click "New Service Delivery" and select the appropriate service. This ensures each service provided is tracked and recorded against the Program Engagement.

References:

Salesforce Nonprofit Cloud Consultant Study Guide

Salesforce Program Management Module Documentation

Salesforce NPSP (Nonprofit Success Pack) Resources

Install NPSP:

Ensure that NPSP is installed in your Salesforce instance. You can download it from the AppExchange or install it directly from the NPSP Installer page​​.

Configure Acknowledgement Settings:

Navigate to NPSP Settings.

Under “Donations,” find the “Acknowledgements” settings.

Configure the settings to define when and how acknowledgements should be sent.

Set Up Email Templates:

Go to Setup > Classic Email Templates.

Create a new email template or modify an existing one to suit your acknowledgment needs.

Ensure the template includes merge fields to personalize the emails with donor information.

Create Automation with Process Builder:

Use Process Builder to automate the sending of acknowledgment emails.

Create a new process on the Opportunity object.

Set criteria to trigger the process when a new donation is recorded.

Add an action to send an email using the previously created template.

Testing:

Test the process by creating a test donation record and verifying that the acknowledgment email is sent automatically.

Monitoring and Refinement:

Monitor the process to ensure it is working correctly.

Refine the email templates and automation rules based on feedback and evolving needs.

By utilizing the NPSP, nonprofits can streamline their donation acknowledgment process, ensuring timely and personalized communications with donors, ultimately enhancing donor satisfaction and retention.

In the Nonprofit Success Pack (NPSP), managing various relationships such as siblings, deceased, and divorced spouses involves using the Relationship object. This object is specifically designed to track and manage the different types of personal relationships between Contacts.

Relationships in NPSP:

The Relationship object allows you to define and track various types of personal connections between Contacts.

This includes familial relationships such as siblings, as well as marital statuses such as deceased and divorced spouses.

Adding Relationships Manually:

Navigate to the Contact record where you want to add a relationship.

In the Relationships related list, click "New Relationship."

Fill out the necessary fields, including the Related Contact and the Relationship Type (e.g., Sibling, Deceased Spouse, Divorced Spouse).

Save the relationship record.

Why Manual Entry:

Manual entry ensures accuracy and allows customization for each specific relationship.

Automated or bulk processes might not accurately capture the nuances of each relationship type.

Use Cases:

For siblings, you would manually create a Relationship record linking the two sibling Contacts.

For deceased or divorced spouses, create a Relationship record and select the appropriate relationship type to reflect the status.

Benefits:

Provides a clear and structured way to manage complex personal relationships.

Enhances reporting and analysis of donor and constituent relationships.

References:

CertGod Nonprofit Cloud Consultant study guide: "Add them as Relationship entries manually"​​.

To capture and analyze wealth scoring for donors in Salesforce, leveraging an AppExchange application is the most effective approach. These applications can provide comprehensive wealth data and insights to support donor cultivation efforts. Here’s how to do it:

Identify Suitable AppExchange Applications:

Search the Salesforce AppExchange for wealth screening and donor prospecting tools (e.g., WealthEngine, DonorSearch).

Install the Application:

Follow the installation instructions provided by the selected application.

Ensure necessary permissions and configurations are set up.

Configure Wealth Scoring:

Set up the application to pull in wealth data for your donor contacts.

Use the provided features to rank and score donors based on their wealth data.

Integrate with NPSP:

Ensure the wealth data integrates with your existing NPSP setup.

Create reports and dashboards to visualize and analyze donor wealth information.

References:

"WealthEngine for Salesforce" on AppExchange: WealthEngine

"DonorSearch for Salesforce" on AppExchange: DonorSearch

For a large nonprofit organization functioning like a for-profit corporation and needing to manage Leads and track its Opportunity pipeline:

Salesforce Account Model without NPSP: This model is suitable as it aligns with for-profit business processes, focusing on managing business accounts, leads, and opportunities. The Household Account Model in NPSP is more suited for organizations managing individual donors, which is not applicable here.

Using the standard Salesforce Account Model allows the organization to leverage Salesforce’s CRM capabilities tailored for B2B interactions.

References:

Salesforce Account Model Documentation

Salesforce Trailhead: Managing Leads and Opportunities

Under the Household Account model in Salesforce NPSP, a Contact's Account represents where they live, essentially their Household. The Primary Affiliation, on the other hand, indicates where they work or are affiliated professionally.

Household Account:

This is used to group individuals living at the same address into a single account.

All contacts associated with a Household share the same Account record, representing their home address and family unit.

Primary Affiliation:

This is a special relationship field in NPSP that links a Contact to an Organization or company where they work or have a significant relationship.

It allows nonprofits to track where their constituents are employed or connected professionally, separate from their residential information.

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 compare giving at consistent points in time from year to year, the best solution is to set up a Reporting Snapshot on Opportunities. A Reporting Snapshot allows you to capture data at specific points in time and then compare it across different periods. Here are the steps to set this up:

Create the Report:

Create a report on Opportunities that includes the relevant data you want to capture (e.g., donation amounts, dates).

Ensure the report filters are set to capture data for the specific time frames you are interested in.

Create a Custom Object:

Create a custom object to store the snapshot data.

Add fields to this custom object that correspond to the fields in your report.

Set Up the Reporting Snapshot:

Navigate to Setup.

In the Quick Find box, type "Reporting Snapshots" and select "Reporting Snapshots".

Click "New Reporting Snapshot".

Name the snapshot and select the source report you created.

Select the target object (the custom object you created).

Map the fields from the report to the fields in the custom object.

Schedule the Reporting Snapshot:

Set up a schedule for when the snapshot should run (e.g., daily, weekly, monthly).

Save and activate the schedule.

By capturing the data at regular intervals, you can generate historical reports that compare giving over different years at consistent points in time.

References:

"Set Up Reporting Snapshots" from Salesforce Help: Reporting Snapshots

"Salesforce Reporting Snapshots for Nonprofits" from Salesforce.org: Salesforce.org Guide

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

To track all donations that go to a specific, designated fund, the consultant should create a GAU Allocation record for the designated fund. Here’s how to set it up:

Create GAU Records:

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

Create a new GAU record for each designated fund.

Link Donations to GAUs:

When entering or importing donations (Opportunities), use the GAU Allocation section to allocate the donation amount to the relevant GAU.

Specify the amount or percentage of the donation that should be allocated to each GAU.

Set Up GAU Allocation:

In the Opportunity record, scroll to the GAU Allocations related list.

Click "New" to create a new GAU Allocation.

Select the appropriate GAU and enter the allocation amount.

Reporting on GAUs:

Create reports to track donations by GAU.

Use the GAU Allocation object in your report to filter and summarize donations by designated funds.

By using GAU Allocations, the nonprofit can effectively manage and report on restricted funds, ensuring that donations are tracked according to donor intent.

References:

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Manage General Accounting Units (GAUs)

Before importing a large volume of data into an NPSP org, it’s crucial to ensure data quality and optimize performance. Here are the steps:

Check if the Data is Clean, Structured, and in its Final Format:

Review the data to ensure it is free of duplicates, correctly formatted, and complete.

Clean data before importing to avoid data quality issues.

Disable Certain Apex Classes Using TDTM:

Navigate to NPSP Settings in Salesforce.

Under "Settings", find "TDTM (Table Driven Trigger Management)".

Temporarily disable non-essential Apex classes that might interfere with the data import process. This helps improve the import performance and reduces the risk of errors.

By following these steps, you can ensure that the data import process is smooth and that the imported data maintains high quality.

References:

"Preparing for Data Import in NPSP" from Salesforce Help: Data Import Preparation

"Managing TDTM in NPSP" from Salesforce.org: TDTM Management

When installing NPSP (Nonprofit Success Pack) in an existing Salesforce org for a nonprofit organization that plans to use the memberships feature, the consultant should create a Membership Opportunity record type. This step is crucial because it allows the organization to effectively track and manage membership-related opportunities distinctly from other types of opportunities.

Steps:

Log in to Salesforce: Access the Salesforce org where NPSP will be installed.

Navigate to Object Manager: Go to Setup and search for "Object Manager".

Select Opportunity Object: From the Object Manager, select the Opportunity object.

Create a New Record Type:

Click "Record Types" under the Opportunity object.

Click "New" to create a new record type.

Enter "Membership" as the Record Type Label.

Provide a description such as "Record type for tracking membership opportunities".

Select the existing record type to clone from (e.g., "Master").

Assign this record type to appropriate profiles.

Click "Save".

Customize Page Layouts: Assign and customize page layouts for the new Membership record type as needed.

Verify and Test: Ensure that the Membership record type is correctly set up by creating a test membership opportunity.

References:

CertGod Nonprofit Cloud Consultant Guide

To record the most recent Opportunity close date on Contact records and ensure the field is overwritten every time a new Opportunity meets the criteria, use NPSP Customizable Rollups:

NPSP Customizable Rollups: This feature allows users to define rollup fields that aggregate data from related objects (e.g., Opportunities) to a parent object (e.g., Contacts).

Most Recent Opportunity Close Date: Configure a rollup summary to track the most recent close date. This ensures the field on the Contact record is updated whenever a new Opportunity with a qualifying close date is added.

Using NPSP Customizable Rollups ensures the process is automated and tailored to nonprofit needs.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Customizable Rollups in NPSP

After migrating to a Nonprofit Success Pack (NPSP) Salesforce org, it's essential to ensure that all migrated Accounts are consistent with the chosen account model. The Data Quality Analysis Dashboard is a vital tool for this purpose.

Data Quality Analysis Dashboard:

This dashboard provides comprehensive insights into data quality across the org.

It helps identify inconsistencies, missing data, and discrepancies in Account records.

Steps to Ensure Consistency:

Run the Data Quality Analysis Dashboard:

Navigate to NPSP Settings and select the Data Quality Analysis Dashboard.

Review the results to identify any Accounts that do not conform to the expected account model.

Address Identified Issues:

Correct any identified discrepancies by updating the Account records to align with the chosen model (e.g., Household Account Model).

Regular Monitoring:

Schedule regular runs of the Data Quality Analysis Dashboard to maintain data integrity over time.

Benefits of Consistency:

Ensures accurate reporting and analytics.

Improves data integrity and usability across the organization.

Facilitates better donor and constituent management.

Complementary Tools:

While the Data Quality Analysis Dashboard is primary, tools like the NPSP Health Check Tool and Salesforce Optimizer can provide additional insights into overall org health and performance.

References:

CertGod Nonprofit Cloud Consultant study guide: "Run the Data Quality Analysis Dashboard"​​.

To determine if an acknowledgment letter was sent for a donation, the best approach is to check the "Acknowledgement Status" picklist value on the Opportunity object. Here's how you can do it:

Navigate to the Opportunity Object:

Go to the App Launcher and find Opportunities.

Add the Acknowledgement Status Field:

Ensure that the "Acknowledgement Status" field is included in the Opportunity page layout.

Navigate to Setup.

In the Object Manager, select Opportunity.

Go to Page Layouts and add the "Acknowledgement Status" field to the relevant layout if it is not already there.

Review the Acknowledgement Status:

Open the Opportunity record for the donation in question.

Look for the "Acknowledgement Status" field to see if it indicates that the acknowledgment letter has been sent.

Automate Tracking (Optional):

Use workflows or Process Builder to update the "Acknowledgement Status" automatically when certain conditions are met, such as when a task related to sending an acknowledgment letter is marked complete.

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation: Managing Acknowledgments

Salesforce Trailhead: Opportunities and Donations

To automatically generate an Opportunity whenever a Lead is converted in NPSP, the consultant should enable the "Create an Opportunity on Lead Convert" option in the NPSP Settings. This option ensures that an Opportunity is automatically created as part of the lead conversion process.

Navigate to NPSP Settings:

Go to the App Launcher, search for "NPSP Settings", and select it.

Enable Lead Conversion Setting:

In NPSP Settings, expand the "Leads" section.

Find the "Lead Conversion" settings.

Check the box for "Create an Opportunity on Lead Convert".

Save the settings.

This configuration streamlines the process, ensuring that Opportunities are consistently created during lead conversion, without requiring additional custom code or third-party applications.

References:

CertGod Nonprofit Cloud Consultant Guide:

When troubleshooting the issue of Recurring Donation Opportunities having close dates at the end of the month instead of the 15th, the consultant should check if the "Always use last day of the month" field is selected. This field setting overrides other close date settings and defaults the close date to the last day of the month.

Log in to Salesforce: Access the Salesforce org where NPSP is installed.

Navigate to NPSP Settings: Go to the App Launcher, search for "NPSP Settings", and select it.

Find Recurring Donations Settings:

In NPSP Settings, expand the "Donations" section.

Click on "Recurring Donations".

Check the "Always use last day of the month" Field:

Locate the "Always use last day of the month" setting.

Verify whether this checkbox is selected.

If selected, uncheck this option if you want the close date to follow the Day of the Month picklist value.

Save the Settings: Save any changes made and verify that new Recurring Donations reflect the correct close date.

By ensuring this field is not selected, the system will correctly use the 15th of the month as specified in the Day of the Month picklist.

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.

To categorize donors into Gold, Silver, and Bronze based on the total gift amount for the year, the NPSP Levels feature should be utilized. This feature allows the organization to automatically categorize donors based on specified criteria.

Define Levels in NPSP:

Navigate to NPSP Settings > Levels.

Create three new Levels: Gold, Silver, and Bronze.

For each Level, specify the range of the total gift amount for the year. For example:

Gold: $10,000 and above

Silver: $5,000 to $9,999

Bronze: $1,000 to $4,999

Configure Level Criteria:

Set the criteria for each Level to be based on the "Total Gifts This Year" field.

Ensure the system is tracking the total gifts correctly by verifying the Customizable Rollups settings.

Assign Levels to Donors:

The system will automatically evaluate donors and assign them to the appropriate Level based on their total giving for the year.

This categorization can be used in reports, dashboards, and donor segmentation for targeted communication and recognition.

References:

CertGod Nonprofit Cloud Consultant Guide:

To automatically add donors who give to the Capital Fund to the Capital Campaign:

Enable Automatic Campaign Member Management in NPSP Settings: This feature allows automatic management of Campaign Members based on criteria defined in NPSP settings.

Populate the Primary Campaign Source Field on the Opportunity Record: By setting the Primary Campaign Source on the Opportunity record, donors can be automatically added to the associated Campaign.

These steps ensure that any donor contributing to the Capital Fund is automatically linked to the Capital Campaign, streamlining the process and ensuring accurate tracking.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Managing Campaigns in NPSP

When using the NPSP Data Importer for Contacts, if some Account records are not being automatically created, the consultant should check:

Required Fields in the Import: Ensure that all required fields for creating an Account are included in the data import file. Missing required fields can prevent Account creation.

Required Fields on the Account: Verify that the Account object does not have custom required fields that are not being populated by the import process. Custom fields marked as required at the field level or in page layouts can block record creation if not provided.

Checking these factors ensures that the import process has all the necessary information to create Account records successfully.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Importing Data with NPSP Data Importer

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

Establishing a Center of Excellence (CoE) addresses the governance function of the application development lifecycle. A CoE provides leadership, best practices, and oversight to ensure consistent and effective use of Salesforce across the organization:

Governance: Ensures that there are clear policies, standards, and guidelines for managing and using Salesforce.

Best Practices: The CoE promotes best practices for development, deployment, and ongoing management of Salesforce applications.

By focusing on governance, a CoE helps maintain the integrity, quality, and strategic alignment of Salesforce initiatives within the nonprofit.

References:

Salesforce Governance Framework Documentation

Salesforce Trailhead: Center of Excellence

If a nonprofit organization has enabled Person Accounts in its Salesforce org and now wants to install NPSP while completely removing all Person Account features, the best approach is to apply for a new Salesforce organization and request a license transfer. Here’s why and how to do it:

Apply for a New Salesforce Organization:

Create a new Salesforce instance without enabling Person Accounts.

This approach avoids the complexities and potential issues of removing Person Accounts from an existing instance.

Request a License Transfer:

Contact Salesforce support to request a transfer of licenses from the old org to the new one.

Provide the necessary details and justification for the transfer.

Install NPSP in the New Org:

Install the Nonprofit Success Pack (NPSP) in the new Salesforce org.

Follow the standard installation and post-installation steps to set up NPSP properly.

Migrate Data:

Plan and execute a data migration from the old org to the new org.

Use data import tools like Data Loader to transfer Contacts, Accounts, Opportunities, and other relevant data.

Ensure data integrity and mapping during the migration process.

By creating a new org and transferring the licenses, the organization can start fresh without the complexities of removing Person Accounts and ensure a smooth transition to using NPSP.

References:

"Salesforce Nonprofit Success Pack Installation" from Salesforce Help: NPSP Installation

"Managing Person Accounts" from Salesforce Help: Person Accounts

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 an international nonprofit organization adds a translated relationship picklist value, and the reciprocal relationship record is not displaying correctly, it is typically due to the system administrator not adding the reciprocal relationship value in the NPSP Settings tab.

Steps:

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

Navigate to NPSP Settings: Go to the App Launcher, search for "NPSP Settings", and select it.

Find Relationship Settings: In the NPSP Settings, expand "People" and then "Relationships".

Add Reciprocal Relationship:

Click "Reciprocal Method Settings".

Ensure that the new reciprocal relationship values are added and correctly configured.

Check both the primary and reciprocal relationship values to ensure they are set correctly.

Save and Test: Save the settings and test to confirm that the reciprocal relationships display correctly.

References:

CertGod Nonprofit Cloud Consultant Guide

To track various funds and report on restricted donations, General Accounting Units (GAUs) in NPSP should be used. Here’s a step-by-step guide:

Set Up General Accounting Units (GAUs):

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

Create GAUs:

Create new GAU records for each fund you need to track.

Provide names and descriptions that clearly identify each fund.

Link GAUs to Donations:

When creating or updating an Opportunity (donation), scroll to the GAU Allocations section.

Allocate the donation amount to the relevant GAU(s). This ensures that each donation is correctly attributed to the specific fund.

Run Reports on GAU Allocations:

Create reports that include GAU Allocation data to see how funds are being utilized and to ensure that restricted donations are tracked correctly.

Automate Allocations (Optional):

Use NPSP settings to define default GAU allocations for specific types of donations to automate this process.

By using GAUs, the nonprofit can effectively manage and report on restricted funds, ensuring compliance and transparency.

References:

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Overview

A Salesforce-recommended V2MOM includes key components that guide an organization’s strategic planning and execution. The two sections that should be included are:

Vision:

This section defines what you want to achieve. It sets the overall direction and purpose of the plan. For example, "Increase donor engagement and retention by 20% over the next fiscal year."

Metrics:

This section includes the measures of success. Metrics help track progress and determine if the vision and goals are being met. For example, "Track the number of new donors, donor retention rate, and total donations received."

Including these sections ensures that the organization has a clear direction (Vision) and a way to measure success (Metrics), which are critical for strategic planning and execution.

References:

"V2MOM: Vision, Values, Methods, Obstacles, and Measures" from Salesforce Blog: V2MOM Framework

To ensure data hygiene and maintenance in Salesforce, it’s essential to follow best practices that help in keeping the data clean and organized. Here are the detailed steps:

Organize Reports into Appropriate Folders:

Navigate to the Reports tab.

Create folders for different types of reports (e.g., Fundraising, Program Management).

Move existing reports into these folders for better organization.

Run Health Check:

Navigate to Setup.

In the Quick Find box, type "Health Check".

Run the Health Check to evaluate your org’s security settings against Salesforce security baseline.

Review the findings and follow the recommendations to improve data security and compliance.

References:

"Organize Reports and Dashboards" from Salesforce Help: Organize Reports

"Salesforce Health Check" from Salesforce Help: Health Check

To avoid manually entering information twice and ensure it appears on both the Opportunity record and the Payment record, follow these steps:

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to "Donations" and select "Payment Mappings".

Create mappings to ensure that relevant fields from the Opportunity record are automatically populated in the Payment record.

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Create custom fields that correspond to the Opportunity fields you want to map.

Ensure the field types match those on the Opportunity object to facilitate accurate data transfer.

These steps automate the data transfer between Opportunities and Payments, reducing manual entry and ensuring consistency across records.

References:

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields

To efficiently enter and de-duplicate donor information received from a vendor's monthly spreadsheet, the NPSP Data Importer is the recommended tool. This tool helps in importing data and associating individuals with Opportunities and Campaigns while handling deduplication. Here’s how to do it:

Prepare the Spreadsheet:

Ensure the spreadsheet contains columns for donor information, donation amounts, and solicitation campaign details.

Access NPSP Data Importer:

Go to the App Launcher.

Search for and open "NPSP Data Importer".

Configure the Data Importer:

Map the columns in your spreadsheet to the corresponding fields in Salesforce, such as Contact, Opportunity, and Campaign fields.

Ensure the NPSP Data Importer settings are configured to check for duplicates based on criteria like email or name.

Upload the Spreadsheet:

Upload the prepared spreadsheet to the NPSP Data Importer.

Review and confirm the data mapping.

Run the Import:

Run the import process.

The Data Importer will create new records and update existing ones, associating Opportunities with Contacts and linking them to the appropriate Campaigns.

Verify and Clean Up:

Use the NPSP Contact Merge tool to handle any potential duplicates that might have been missed.

Verify that all data has been imported correctly.

References:

"NPSP Data Importer" from Salesforce Help: NPSP Data Importer

"Managing Duplicates with NPSP" from Salesforce.org: Managing Duplicates

For a volunteer manager to search for volunteers with specific skills and availability using Volunteers for Salesforce, the following steps can be advised:

Use the Find Volunteers Tab:

Click on the "Find Volunteers" tab in Salesforce.

Filter Criteria:

Fill in the Volunteer Status, Volunteer Availability, and Volunteer Skills tabs with the required values:

Volunteer Status: Select the appropriate status (e.g., Active, Available).

Volunteer Availability: Specify the dates and times the volunteer is available.

Volunteer Skills: Include landscaping or other required skills.

Hit Search:

Click on the "Search" button to retrieve the list of volunteers matching the criteria.

Review and Contact Volunteers:

Review the list of volunteers who meet the criteria.

Use the contact information provided to reach out to the suitable volunteers for the specific task.

This method leverages the built-in search functionalities in Volunteers for Salesforce, providing an efficient way to find and manage volunteers based on specific needs.

References:

Volunteers for Salesforce Documentation: Finding and Managing Volunteers

Salesforce Trailhead: Volunteers for Salesforce

To load 45,000 records into Salesforce from a single flat file:

Data Loader: This tool is designed for bulk data import and export, handling large volumes of records efficiently. It supports complex data mappings and transformations required for importing donor, donation, and payment processing records.

Large Volume Handling: Data Loader can process up to millions of records, making it suitable for the task at hand.

Using Data Loader ensures that the records are imported accurately and efficiently, with the ability to handle data transformations as needed.

References:

Salesforce Data Loader Documentation

Salesforce Trailhead: Data Management Tools

To protect sensitive data like a government-issued ID number, encrypting the field and carefully managing access permissions is crucial. Here's a step-by-step guide on implementing this security solution:

Create the Custom Field:

Navigate to Setup.

In the Object Manager, select the relevant object (e.g., Contact).

Click on Fields & Relationships.

Create a new Text field for the government-issued ID number.

Enable Classic Encryption for Custom Fields:

In Setup, search for "Encryption Policy".

Enable "Encrypt Custom Fields".

Select the custom field you created for the government-issued ID and mark it for encryption.

Set Permissions:

Navigate to Setup.

Go to Profiles or Permission Sets.

Ensure only the necessary profiles/permission sets have the "View Encrypted Data" permission:

Click on the relevant Profile or Permission Set.

In System Permissions, enable "View Encrypted Data".

Assign this permission only to those users who need to interact with the government ID data.

Adjust Field-Level Security:

In the Object Manager, select the custom field for the government ID.

Click on "Set Field-Level Security".

Ensure the field is visible only to the necessary profiles.

Remove the field from page layouts for users who should not access it.

Test the Setup:

Log in as a user with access to the encrypted data to verify they can view and interact with the data.

Log in as a user without access to ensure they cannot see the encrypted field.

By following these steps, you ensure that the government-issued ID number is encrypted and only accessible to authorized personnel, thereby protecting sensitive client data effectively.

References:

Salesforce Security Guide: Classic Encryption for Custom Fields

Salesforce Permission Sets: Managing Permissions

To correctly upload donors' employment information into the NPSP Affiliations object, the data should be imported in a specific order. Here’s how to do it:

Insert Organization Accounts:

Start by inserting records for the employers (Organization Accounts).

Ensure each employer has a unique Account ID.

Insert Contact Records:

Next, insert the Contact records for the donors.

Make sure each Contact record has a unique Contact ID and is associated with the correct Account (if applicable).

Insert Affiliation Records:

Finally, insert Affiliation records to link the Contacts to their respective Organization Accounts (employers).

Include fields like Contact ID, Account ID (employer), and other relevant details such as role and status.

By following this order, you ensure that all necessary data relationships are correctly established in Salesforce.

References:

"Managing Affiliations in NPSP" from Salesforce Help: Affiliations

"Data Import Best Practices" from Salesforce.org: Data Import

The correct order for importing data into Salesforce, considering multiple mailing addresses for donors, is:

Account: Import accounts first to establish the primary records.

Address: Import address records to link them to the appropriate accounts.

Contact: Import contacts next to associate them with the correct accounts and addresses.

Campaign: Import campaign records to track the event (gala) details.

Opportunity: Finally, import opportunities to record the donations linked to the appropriate contacts and campaigns.

This order ensures data integrity and correct relationships between the imported objects.

References:

Salesforce Data Import Best Practices

Salesforce Trailhead: Data Import Wizard and Data Loader

Pardot is the recommended automation method for sending out automated renewal emails on a 30/60/90 day schedule, with different email templates based on members' website visits. Pardot is a powerful marketing automation tool that integrates seamlessly with Salesforce, providing advanced capabilities for email marketing, lead nurturing, and segmentation. Here’s how to set this up:

Integrate Pardot with Salesforce:

Ensure that Pardot is connected to your Salesforce instance. This allows seamless data synchronization between the two systems.

Create Email Templates in Pardot:

Design and create the different email templates in Pardot that you want to use for the 30, 60, and 90-day renewal reminders.

Personalize the email content based on the members’ interactions and website visits.

Set Up Automation Rules:

Use Pardot’s automation rules to create rules that trigger emails based on the members' renewal dates and website activity.

Define the criteria for each rule (e.g., 30 days before renewal date, 60 days before renewal date, etc.).

Create Engagement Programs:

Use Engagement Studio in Pardot to create automated drip programs that send out the renewal emails at the specified intervals.

Add logic to the engagement program to select different email templates based on the members' website visits and interactions.

Track and Analyze:

Use Pardot’s reporting and analytics features to track the performance of the email campaigns, monitor open rates, click-through rates, and engagement metrics.

By leveraging Pardot’s advanced automation capabilities, the organization can efficiently manage and personalize its renewal email campaigns, improving member retention and engagement.

References:

"Getting Started with Pardot" from Salesforce Help: Pardot Setup Guide

"Pardot Engagement Studio" from Salesforce Help: Engagement Studio

When a consultant is about to begin a data project with a nonprofit to clean up Opportunity data and needs to temporarily disable NPSP Triggers for performance reasons, it is typically necessary when uploading a large volume of records, such as 1 million new Contact records.

Steps:

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

Navigate to NPSP Settings: Go to the App Launcher, search for "NPSP Settings", and select it.

Disable Triggers:

In the NPSP Settings, expand "Bulk Data Processes" and then "TDTM".

Find the specific triggers related to the data being uploaded.

Disable the relevant triggers by unchecking the "Active" checkbox.

Save the changes.

Perform Data Upload:

Use a data loader or similar tool to upload the 1 million Contact records.

Ensure data integrity and verify successful upload.

Re-enable Triggers:

After the data upload is complete, go back to the NPSP Settings.

Re-enable the previously disabled triggers by checking the "Active" checkbox.

Save the changes.

Verify and Test: Confirm that the triggers are working correctly and that the data has been uploaded properly.

References:

CertGod Nonprofit Cloud Consultant Guide

To track grant lifecycles using the Nonprofit Success Pack (NPSP), you can utilize a combination of Opportunities, Payments, Deliverables, and Activities. Here’s how you can set this up:

Opportunities for Grants:

Create an Opportunity record for each grant.

Use custom fields or record types to distinguish grants from other types of Opportunities.

Payments:

Use the Payments object to track actual disbursements for each grant.

Associate Payments with the corresponding Opportunity.

Deliverables for Applications and Deadlines:

Create Deliverables (a custom object or use Tasks/Activities) to track grant applications and reporting deadlines.

Link Deliverables to the Opportunity record.

Activities for Action Assignments:

Use Tasks or Events to assign actions to staff members.

These activities can be associated with the Opportunity to keep everything organized.

By using these elements, you can have a comprehensive view of each grant’s lifecycle, from application to final reporting, including all associated payments and staff actions.

References:

"Grant Management in Salesforce" from Salesforce Help: Grant Management

"Using NPSP for Grant Management" from Salesforce.org: Grant Management with NPSP

When the system administrator notices a scheduled skew job but does not remember scheduling it, the best course of action is to view the Setup Audit Trail. This will help determine the origin and purpose of the job. Here’s how to do it:

Navigate to Setup:

Click on the gear icon in the top right corner of Salesforce.

Select "Setup".

Access the Setup Audit Trail:

In the Quick Find box, type "Setup Audit Trail".

Click on "View Setup Audit Trail".

Review the Audit Trail:

The Setup Audit Trail logs changes made to your Salesforce configuration, including scheduled jobs.

Look for entries related to the creation or modification of scheduled jobs.

Identify who created the job, when it was created, and any additional details provided in the log.

Determine Next Steps:

Based on the information found in the audit trail, decide whether the job is necessary.

If the job is not needed, it can be deleted. If it is essential, ensure that it is documented and understood.

References:

Salesforce Documentation: Monitor Setup Changes

Salesforce Trailhead: Monitor Changes in Your Org

To add donors to a Campaign from an Opportunities report, the report must include Contact records. The correct approach is to create a report type that includes Contacts, such as the Opportunities with Contact Roles report type.

Creating the Report:

Navigate to the Reports tab and click "New Report."

Select the "Opportunities with Contact Roles" report type. This report type includes both Opportunity and Contact records.

Configuring the Report:

Add the necessary filters to include the desired Opportunities and their related Contacts.

Customize the report to display relevant fields, such as Contact Name and Opportunity Amount.

Adding to Campaign:

Once the report is configured and run, select the Contacts you want to add to the Campaign.

Use the "Add to Campaign" button available in the report to add these Contacts as Campaign Members.

Benefits of This Approach:

Ensures that the Campaign Members are correctly linked to the Opportunity records.

Streamlines the process of managing Campaigns and associated donor information.

Additional Steps:

Ensure that the "Add to Campaign" button is enabled for the report type in Setup if it is not already visible.

References:

CertGod Nonprofit Cloud Consultant study guide: "Create a report type that includes Contacts such as the Opportunities with Contact Roles report type"​​.