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

check the entity relationship diagram

When evaluating whether to use Program Management Module (PMM) or Nonprofit Cloud Case Management, it is important to consider the specific requirements of the nonprofit. While PMM can track programs, services, and the impact of those services, Nonprofit Cloud Case Management offers additional functionality tailored to human services nonprofits. Case Management includes custom objects specifically designed to track client goals and action items, making it more suitable for organizations needing detailed goal tracking.

Steps:

Assess the specific requirements for tracking client goals and action items.

Compare the features of PMM and Case Management.

Highlight that Case Management has a custom object for tracking goals and action items.

Discuss the benefits and potential limitations of implementing Case Management, including the need for Experience Cloud licenses if applicable.

References:

CertGod Nonprofit Cloud Consultant Guide: Provides an overview of the features of both PMM and Case Management​​.

Salesforce Nonprofit Cloud Case Management Documentation: Details on custom objects and functionalities available in Case Management.

For a nonprofit client inexperienced with Salesforce, the best training resource to recommend is Trail Tracker by Trailhead:

Trail Tracker by Trailhead:

Trail Tracker is a Salesforce app that integrates with Trailhead, allowing organizations to assign, track, and manage Trailhead training for their users.

It is specifically designed to help users learn Salesforce through guided, interactive learning paths.

Set Up Trail Tracker:

Install Trail Tracker from the Salesforce AppExchange.

Configure the app to align with your nonprofit’s training goals.

Assign Training Modules:

Identify the relevant NPSP fundraising training modules on Trailhead.

Use Trail Tracker to assign these modules to staff members.

Monitor Progress:

Use Trail Tracker dashboards to monitor the progress of staff members as they complete their training modules.

Provide additional support or resources as needed to ensure successful completion.

References:

Salesforce Trailhead and Trail Tracker documentation

CertGod Nonprofit Cloud Consultant guide​

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

To search for nonprofit user groups in a particular region or state, an admin should use the Trailblazer Community:

Access Trailblazer Community:

Go to the Trailblazer Community website: trailblazer.salesforce.com.

Search for User Groups:

Use the search functionality to look for user groups. You can enter keywords related to your region, state, or specific interests such as "nonprofit user groups."

You can also filter search results by location to find groups relevant to your area.

Join Relevant Groups:

Review the list of user groups and join the ones that are most relevant to your needs.

Engaging with these groups allows you to connect with other nonprofit Salesforce users, share best practices, and stay informed about local events and meetups.

The Trailblazer Community is a valuable resource for finding and connecting with regional nonprofit user groups.

References:

Trailblazer Community: trailblazer.salesforce.com

Salesforce Help: Community User Groups

Governance is critical in a Salesforce implementation project for several reasons:

Cost Savings:

Effective governance helps prevent costly mistakes and rework by ensuring that all project activities align with the overall objectives and best practices.

It also ensures efficient resource utilization and minimizes waste.

Security:

Governance frameworks include policies and procedures to safeguard data and ensure compliance with legal and regulatory requirements.

It ensures that proper security measures are in place to protect sensitive information, which is crucial for nonprofit organizations.

Delivery Speed:

With governance, there are clear roles, responsibilities, and processes which streamline decision-making and reduce delays.

It enables quicker resolution of issues and ensures that the project stays on track, leading to faster delivery.

Steps to Emphasize Governance:

Establish a governance committee that includes key stakeholders.

Define clear governance policies and procedures.

Regularly review and adjust the governance framework as needed to ensure continuous alignment with project goals.

By emphasizing these points, the consultant can highlight the importance of governance in ensuring the success of the Salesforce implementation.

References:

Salesforce Governance Documentation

Trailhead Module: Salesforce Governance Basics

When encountering an issue while configuring Nonprofit Cloud Case Management, the consultant should first check Salesforce Help to see if it is a documented issue. Salesforce Help provides extensive documentation, release notes, and known issues, making it a reliable source for troubleshooting.

Steps to Check:

Salesforce Help:

Navigate to Salesforce Help & Training.

Search for the specific issue or error message.

Review any available documentation, known issues, and suggested resolutions.

Additional Resources:

If the issue is not documented in Salesforce Help, the consultant can also check the Trailblazer Community for discussions and solutions provided by other users.

References:

Salesforce Help & Training

Salesforce Trailhead: Salesforce Help Resources

To handle frequent imports of membership renewal and donation data, where each import needs a different configuration to update existing Contacts and create Opportunities, the NPSP Data Importer should be recommended:

NPSP Data Importer:

The NPSP Data Importer is specifically designed for nonprofits and supports complex data import needs, including updating existing records and creating new ones.

It allows you to map fields from your import file to Salesforce fields, ensuring data is correctly placed.

Set Up the Import:

Prepare your data in a CSV format.

Go to the NPSP Data Importer app in Salesforce.

Create separate templates for membership renewals and donations to handle different configurations.

Map Fields:

Use the mapping feature to map fields from your import file to the corresponding Salesforce fields.

Ensure that you map fields for Contacts, Opportunities, and any custom fields needed for memberships and donations.

Run the Import:

Upload your data file and run the import process.

Monitor the import progress and check for any errors or discrepancies.

Verify Data:

After the import is complete, verify that the data has been correctly updated and new records have been created as expected.

Check the updated Contacts and newly created Opportunities to ensure data integrity.

References:

Salesforce Nonprofit Success Pack (NPSP) documentation on the Data Importer

CertGod Nonprofit Cloud Consultant guide​

To predict the likelihood of a contact becoming a recurring donor, the consultant should implement Einstein for Nonprofits. Here's how:

Enable Einstein for Nonprofits:

Ensure that Einstein Analytics and Discovery are enabled in the Salesforce org.

Navigate to the Einstein for Nonprofits setup and configure the necessary settings.

Configure Prediction Models:

Use Einstein Prediction Builder to create a custom prediction model.

Define the criteria and data points that indicate a high likelihood of recurring donations, such as past donation behavior, engagement levels, and demographic information.

Train and Deploy the Model:

Train the prediction model using historical data.

Deploy the model to start predicting which contacts are likely to become recurring donors.

Utilize Predictions in Fundraising Strategies:

Fundraisers can use the predictions to prioritize outreach and engagement efforts.

Customize communication and engagement plans for high-potential recurring donors.

Einstein for Nonprofits leverages AI and machine learning to provide insights and predictive analytics, helping nonprofits make data-driven decisions to enhance donor engagement and fundraising efforts.

References:

Salesforce Einstein for Nonprofits: Einstein for Nonprofits.

Salesforce Einstein Prediction Builder Guide: Prediction Builder.

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】.

To delegate authority to specific users for processing gift entries, the consultant should add the following permissions to a permission set:

Grant visibility to the Gift Entry tab:

This permission ensures that users can access the Gift Entry tab where they can process and manage gift entries.

Grant create, edit, and delete access to all required objects and fields:

Users need full CRUD (Create, Read, Update, Delete) access to objects and fields related to gift processing such as Donations, Payments, and any custom fields or objects involved in the gift entry process.

This level of access is essential for users to accurately record, update, and manage gift entries.

Grant access to BDI_BatchOverride and BDI_DataImport Visualforce pages:

These Visualforce pages are part of the Batch Data Import (BDI) functionality in NPSP, which is used for batch processing of gift entries.

Access to these pages allows users to override batch data and perform data imports necessary for processing gifts.

References:

Salesforce documentation on Gift Entry permissions: Gift Entry Permissions

To segment constituents based on their one-time donations from the prior fiscal year, the nonprofit should use Customizable Rollups in NPSP:

Customizable Rollups:

Customizable Rollups in NPSP allow nonprofits to create custom rollup fields that aggregate data based on specific criteria, such as donation type and date range.

These rollups can be configured to include only one-time gifts received during the prior fiscal year.

Setting Up Rollups:

Navigate to NPSP Settings.

Go to "Donations" and then "Customizable Rollups."

Create a new rollup that sums one-time donations within the specified date range (the prior fiscal year).

Use this rollup field to segment and analyze constituents based on their donation history.

Reporting and Segmentation:

Use the rollup field in reports and list views to segment constituents and analyze their giving patterns.

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation: Customizable Rollups

Salesforce Help: Creating and Managing Rollups

When a nonprofit organization is informed of a deceased donor and wants to ensure that the donor no longer appears on any mailing lists, the appropriate action is to select the "Deceased" field on the donor's contact record. Here’s how to do it:

Navigate to the Contact Record:

Go to the Contacts tab in Salesforce.

Search for the donor’s contact record and open it.

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Additional Actions:

Ensure that any automated processes or workflows related to email and mailing lists exclude contacts marked as deceased.

Update any relevant lists or segments to remove the deceased donor from future communications.

Implications of Marking a Contact as Deceased:

The contact will no longer be included in email or direct mail campaigns.

The contact record is retained in Salesforce for historical and reporting purposes, preserving donation history and other relevant information.

References:

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

To reduce manual data entry and improve efficiency when entering donation data into both Salesforce and an external accounting system, the consultant should recommend using the Accounting Subledger:

Accounting Subledger:

The Accounting Subledger in NPSP provides a way to sync financial data between Salesforce and external accounting systems.

It ensures that donation data entered in Salesforce is automatically available for reconciliation and reporting in the accounting system.

Setting Up Accounting Subledger:

Install and configure the Accounting Subledger from the AppExchange.

Define the mapping between Salesforce donation records and the corresponding records in the accounting system.

Set up integration rules to automatically sync data based on predefined triggers and schedules.

Benefits:

Reduces manual data entry by automating the transfer of donation data.

Ensures data consistency and accuracy across systems.

Provides real-time visibility into financial data for better decision-making.

By using the Accounting Subledger, the nonprofit can streamline its data entry processes and improve overall efficiency.

References:

Salesforce AppExchange: Accounting Subledger

Nonprofit Success Pack (NPSP) Documentation: Financial Management and Integration

https://powerofus.force.com/s/artic le/NPSP-Override-the-Default-Address-for-a-Contact

To access a list of constituents who do not reside at their household mailing address, you should create a report with the following steps:

Create a New Report:

Navigate to the Reports tab in Salesforce.

Click on "New Report."

Select Report Type:

Choose "Contacts & Accounts" as the report type.

Add Filters:

Add a filter for "Address Override" and set it to "True."

This filter will include only those constituents whose mailing address is overridden to a different address than their primary household address.

Customize Report Columns:

Include relevant columns such as Contact Name, Household Name, and Address details in your report.

Run and Save the Report:

Run the report to ensure it captures the correct data.

Save the report for future use and sharing with the mail house.

By filtering the Contacts and Accounts report for Address Override = True, you can easily access and export a list of constituents who prefer to receive mail at a different address.

References:

Salesforce documentation on creating and customizing reports.

Nonprofit Success Pack (NPSP) documentation on Address Management and Overrides.

To improve training and adoption of Salesforce, the following standard Salesforce tools can be highly effective:

In-App Guidance (B):

This feature allows administrators to create and customize prompts and walkthroughs that appear directly within the Salesforce interface. In-App Guidance helps new users learn how to use Salesforce by providing contextual help and tips.

myTrailhead (D):

myTrailhead is a customizable learning platform that allows organizations to create their own training content. It provides a self-paced learning environment where new staff can access and complete training modules specific to the nonprofit's Salesforce setup.

Steps to Implement:

Set Up In-App Guidance:

Navigate to Setup -> In-App Guidance.

Create prompts and walkthroughs tailored to the nonprofit's processes.

Deploy myTrailhead:

Customize and publish training content on myTrailhead.

Encourage staff to complete the training modules to improve their Salesforce skills.

References:

Salesforce In-App Guidance Documentation

Salesforce myTrailhead Documentation

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-data-mask/understand-the-importance-of-data-privacy

Salesforce Data Mask is the recommended solution to ensure the contractor is unable to access sensitive data in a full copy sandbox. Data Mask is designed to secure sensitive data in sandboxes by masking or obfuscating it, thereby preventing unauthorized access.

Salesforce Data Mask Overview:

Salesforce Data Mask allows you to obfuscate sensitive data in sandboxes, ensuring that real data is not exposed.

It provides various masking options, including anonymization, pseudonymization, and deletion.

Implementation Steps:

Install Salesforce Data Mask from the Salesforce AppExchange.

Configure the masking rules for the fields that contain sensitive information. You can choose the appropriate masking technique based on your needs (e.g., random characters, fixed characters, or deletion).

Apply the masking rules to the full copy sandbox where the contractor will be working.

Benefits of Using Data Mask:

Security: Ensures sensitive data is not exposed in non-production environments.

Compliance: Helps meet regulatory and compliance requirements by protecting personal and personally identifiable information.

Flexibility: Allows you to define specific rules for different types of data and fields.

References:

CertGod Nonprofit Cloud Consultant study guide: "Implement Salesforce Data Mask and mask the sensitive data"​​.

To meet the requirement of sharing client assessments, notes, and alerts among staff within the nonprofit using Nonprofit Cloud Case Management, the following approaches are recommended:

Create a Public Group:

Create a Public Group that includes all staff members who need access to the client information.

This group will be used to grant shared access to the relevant records.

Steps to Create a Public Group:

Go to Setup.

Enter "Public Groups" in the Quick Find box and select it.

Click "New Group" and add the necessary staff members.

Create Sharing Rules:

Set up sharing rules for the Assessments, Client Notes, and Client Alerts objects to share these records with the Public Group.

This ensures that any updates or new records created within these objects are automatically shared with the staff group.

Steps to Create Sharing Rules:

Go to Setup.

Enter "Sharing Settings" in the Quick Find box and select it.

Select the relevant object (e.g., Assessments).

Click "New" under Sharing Rules and define the criteria and target group (Public Group created earlier).

These steps ensure that relevant client information is shared with the appropriate staff, enhancing collaboration and service delivery.

References:

Salesforce Help: Creating Public Groups

Salesforce Help: Defining Sharing Rules

To ensure that a deceased donor no longer appears on any mailing lists, the appropriate action is to select the Deceased field on the donor's Contact record.

Deceased Field:

Salesforce provides a specific field to mark a Contact as deceased.

This field is designed to handle the scenario of deceased Contacts appropriately within the system.

Steps to Mark Contact as Deceased:

Navigate to the Contact record of the deceased donor.

Find the Deceased checkbox field and select it.

Save the record.

Impact of Selecting the Deceased Field:

Once marked as deceased, the Contact will automatically be excluded from future mailing lists and communications.

This helps maintain respectful and accurate communication practices.

Other Considerations:

Do Not Email, Do Not Contact, and Email Opt Out Fields: While these fields prevent specific types of communications, they do not address the status of the Contact as being deceased, which is important for accurate records and reporting.

Deleting Contact Record: Deleting the Contact record is not recommended as it removes historical donation data and other important information that may be needed for reporting and compliance purposes.

References:

CertGod Nonprofit Cloud Consultant study guide: "Select the Deceased field"【22:2†source】.

Before implementing the Accounting Subledger, review the following configurations:

Review Accounting Triggers:

Ensure that your Salesforce instance has the necessary triggers enabled to support the Accounting Subledger.

Go to Setup -> Triggers, and verify the status of triggers related to accounting functionalities.

Check Recurring Donations:

Navigate to NPSP Settings -> Recurring Donations.

Verify that the configuration aligns with the needs of the Accounting Subledger, ensuring proper allocation and tracking of recurring donations.

Payment Allocations:

Check the settings for payment allocations to ensure they are correctly mapped to the general ledger accounts used in your accounting system.

NPSP Settings:

Verify the overall NPSP settings to ensure there are no conflicts with the Accounting Subledger functionalities.

References:

Salesforce Accounting Subledger Documentation

Salesforce Nonprofit Success Pack (NPSP) Configuration Guide

Salesforce Trailhead: Configure Nonprofit Success Pack

To create a report that shows who the solicitor is for each donor using automated soft credits, the system admin should use the "Opportunities with Partial Soft Credits and Contacts" report type. This report type allows the inclusion of soft credits and the related contacts, making it possible to track the solicitor for each donation.

Steps to Create the Report:

Choose the Report Type:

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

Select the "Opportunities with Partial Soft Credits and Contacts" report type.

Customize the Report:

Add the necessary fields to display the solicitor, donor, and relevant opportunity information.

Use filters to refine the data as needed.

Save and Run the Report:

Save the report with an appropriate name and run it to view the results.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Create and Customize Reports

To provide each affiliate and the national nonprofit the ability to see only its own donor data in a single Salesforce org, the consultant should use Criteria-based Sharing. Here's why:

Criteria-based Sharing:

This feature allows for defining sharing rules based on specific criteria, such as record ownership or certain field values.

By setting up criteria-based sharing rules, each affiliate and the national nonprofit can be restricted to viewing only the records that meet the specified criteria, such as records tagged with their specific region or affiliate identifier.

References:

Salesforce Sharing and Visibility Guide

Salesforce Criteria-based Sharing Rules Documentation

When loading a large volume of data, such as 5 million donation history records, into Salesforce, it is essential to temporarily disable TDTM (Trigger Handler Framework) to ensure the data load is successful. TDTM triggers can slow down or interrupt the data load process due to the large volume of records being processed.

Steps:

Go to Setup > Custom Metadata Types.

Select "Trigger Handlers."

For each trigger handler, uncheck the "Active" checkbox to temporarily disable it.

Perform the data load using Data Loader or another data import tool.

Once the data load is complete, re-enable the TDTM Trigger Handlers by checking the "Active" checkbox for each trigger handler.

References:

CertGod Nonprofit Cloud Consultant Guide: Advises on the importance of managing TDTM triggers during large data loads​​.

Salesforce Documentation on TDTM: Provides instructions on managing and disabling TDTM triggers.

To track supporters who send advocacy messages to elected officials, the nonprofit can use the following solutions:

Organize Advocacy Messages into Campaigns:

Create a Campaign in Salesforce for each advocacy initiative.

Add Contacts who take action (send messages) as Campaign Members. This allows the nonprofit to track participation and engagement within each advocacy campaign.

Use an Online Advocacy Platform from the AppExchange:

Select an advocacy platform from the Salesforce AppExchange that integrates with Salesforce. These platforms are designed to facilitate advocacy efforts and automatically sync supporter actions with Salesforce.

The platform can record which supporters sent messages and update Salesforce accordingly, ensuring accurate tracking and reporting.

These solutions provide a comprehensive approach to managing and tracking advocacy efforts, leveraging the capabilities of Salesforce and specialized advocacy tools.

References:

Salesforce AppExchange: Advocacy Platforms

Nonprofit Success Pack (NPSP) Documentation: Managing Campaigns and Campaign Members

https://www.salesforce.org/blog/how-nonprofits-can-use-pardot-for-moves-management/

To address the nonprofit's need for a marketing automation tool that allows for segmentation, targeting, and email creation using Lightning Email Templates:

Choose Pardot:

Pardot is Salesforce's marketing automation solution designed to handle sophisticated email marketing, segmentation, and engagement tracking.

Set Up Pardot:

Ensure Pardot is integrated with Salesforce.

Configure user permissions and roles in Pardot.

Connect Pardot to the Salesforce CRM to synchronize data between the two platforms.

Segment and Target Supporters:

Use Pardot's segmentation tools to create lists based on supporter engagement and interactions.

Set up dynamic lists that automatically update based on predefined criteria such as email opens, clicks, and website visits.

Create Emails with Lightning Email Templates:

Utilize Lightning Email Templates in Pardot to design and personalize emails.

Use drag-and-drop features to build responsive email templates without needing HTML knowledge.

Track Engagement:

Implement Pardot’s engagement tracking to monitor how supporters interact with emails.

Use Pardot’s scoring and grading system to prioritize leads based on their engagement and fit with your nonprofit's goals.

Analyze and Optimize:

Use Pardot’s analytics and reporting tools to measure the effectiveness of your campaigns.

Continuously refine your segmentation and targeting strategies based on data insights to improve engagement and conversion rates.

By using Pardot, the nonprofit can effectively segment its audience, target them with personalized email campaigns, and track engagement over time, enhancing their overall marketing efforts.

References:

Salesforce Pardot documentation on segmentation and email marketing

CertGod Nonprofit Cloud Consultant guide​

For loading a large volume of records, such as approximately 3 million records, into Salesforce, the Bulk API is the most efficient method. The Bulk API is designed to handle large data sets by processing records asynchronously in batches, which reduces the load on Salesforce servers and ensures efficient data transfer. This API is optimized for data loading and extraction, making it ideal for high-volume data operations.

References:

Salesforce Bulk API Developer Guide

Salesforce Nonprofit Cloud Data Import Best Practices

To integrate wealth scoring information into Salesforce, the consultant should recommend using a third-party app from the AppExchange. Here’s the process:

Explore AppExchange:

Visit the Salesforce AppExchange.

Search for wealth scoring or donor prospecting applications.

Evaluate Apps:

Review the available apps that offer wealth scoring and donor analytics.

Evaluate the features, customer reviews, and integration capabilities of each app.

Select an App:

Choose an app that best fits the nonprofit’s requirements for wealth scoring integration.

Popular options include apps like WealthEngine, DonorSearch, or iWave.

Install and Configure the App:

Install the selected app into the Salesforce org.

Follow the configuration steps provided by the app to integrate wealth scoring data with Salesforce records.

Map Wealth Scores to Salesforce Fields:

Map the wealth scoring data fields to the appropriate fields on Salesforce objects, such as Contacts and Opportunities.

Ensure the data is displayed where it is most useful for development officers and other users.

By using a third-party app from the AppExchange, the nonprofit can seamlessly integrate comprehensive wealth scoring information into Salesforce, enhancing their donor prospecting and engagement strategies.

References:

Salesforce AppExchange: WealthEngine

Salesforce Documentation: Install Apps from AppExchange

To allow staff to use other applications without leaving Salesforce, implementing Salesforce Canvas is the recommended solution:

Salesforce Canvas:

Salesforce Canvas allows you to embed external applications directly within Salesforce

A runtime error during a Customizable Rollup operation often occurs if the target field has an active validation rule that prevents the update. Validation rules enforce specific criteria that records must meet before they can be saved, and if these criteria are not met during the rollup operation, an error will occur.

Steps to Troubleshoot:

Review Validation Rules:

Navigate to Setup -> Object Manager -> [Target Object] -> Validation Rules.

Review the validation rules on the target object to identify any that might conflict with the rollup operation.

Modify or Temporarily Disable Validation Rules:

If a validation rule is causing the error, consider modifying the rule to accommodate the rollup operation or temporarily disabling it during the data update process.

Check Rollup Configuration:

Ensure the Customizable Rollup settings are correctly configured and that no unnecessary constraints are in place.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Help: Validation Rules

Integrating an external event management system with Salesforce can be efficiently achieved using a middleware tool. Middleware tools are designed to facilitate communication and data transfer between different systems, automating processes and ensuring data consistency.

Middleware Tools:

Middleware tools like Mulesoft, Dell Boomi, or Jitterbit are commonly used to integrate Salesforce with external systems.

They offer robust functionalities for data transformation, real-time integration, and scheduled data synchronization.

Integration Process:

Data Mapping: Define how data fields in the event management system correspond to Salesforce fields.

API Connectivity: Set up API connections between the event management system and Salesforce using the middleware tool.

Automation: Schedule daily data transfers to automatically send event and attendee data to Salesforce, creating Campaigns and Campaign Members.

Advantages:

Real-time Data Transfer: Ensure that data is updated in real-time or at scheduled intervals without manual intervention.

Data Consistency: Middleware tools help maintain data consistency and integrity across systems.

Scalability: Easily handle large volumes of data and complex integration requirements.

Implementation Steps:

Choose a middleware tool based on the organization's requirements and budget.

Configure the tool to connect to the event management system and Salesforce.

Map the data fields and set up the necessary transformations.

Test the integration thoroughly before going live.

References:

CertGod Nonprofit Cloud Consultant study guide: "Consider using a middleware tool to integrate the event management system with Salesforce"【22:13†source】.

To ensure that Person Accounts and NPSP can coexist within the same Salesforce org, follow these configurations:

Different Household Record Type in NPSP Settings:

Navigate to NPSP Settings.

Ensure that the Household record type specified in NPSP settings is different from the Person Account record type.

This prevents conflicts and ensures that NPSP correctly distinguishes between Household Accounts and Person Accounts.

Default Record Type for Profiles of Users Converting Leads:

Go to Setup > Profiles.

Ensure that the default record type for any profiles of users who convert leads is not set to the Person Account record type.

This ensures that when leads are converted, they do not automatically become Person Accounts, which could disrupt the NPSP data model.

By following these configurations, the nonprofit can effectively manage both Person Accounts and NPSP functionalities within the same Salesforce environment.

References:

Salesforce NPSP Documentation: NPSP Configuration.

Salesforce Person Accounts Guide: Person Accounts.

To ensure information appears on both the Opportunity and Payment records without entering it twice, the following steps should be taken:

Create Custom Fields on the Payment Object:

Identify the fields that need to be shared between the Opportunity and Payment records.

Go to the Payment object in Salesforce and create custom fields that match those on the Opportunity object.

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to the “Donations” section and find “Payment Mappings.”

Set up mappings to link Opportunity fields to the corresponding Payment fields.

This ensures that when an Opportunity is created or updated, the relevant data is automatically copied to the Payment record.

By creating custom fields and setting up payment mappings, the required information will be synchronized between Opportunity and Payment records, eliminating the need for duplicate data entry.

References:

Salesforce Nonprofit Success Pack (NPSP) documentation on Payment Mappings

CertGod Nonprofit Cloud Consultant guide​

When defining user stories for a Salesforce implementation, it is essential to ensure that each story is aligned with the overall vision of the project and that they are prioritized based on business needs. This approach helps in delivering value incrementally and keeps the project focused on the key objectives.

Key Components of a User Story:

Alignment with Vision (A):

Ensure that each user story aligns with the nonprofit's overall implementation vision. This alignment helps in maintaining consistency and achieving the strategic goals of the organization.

Assign Priority (C):

Assign a priority to each user story to manage the implementation effectively. Prioritizing user stories ensures that the most critical functionalities are developed and delivered first.

References:

Salesforce Agile Development Practices

Salesforce Trailhead: User Stories for Agile Development

Before embarking on a new implementation project, it is crucial to first identify the challenges the nonprofit is currently experiencing. This ensures that the new solution will address the specific needs and pain points of the organization. Understanding these challenges will guide the implementation strategy and help in configuring Salesforce to meet the nonprofit's goals effectively.

Steps:

Conduct stakeholder interviews to gather information on current processes and challenges.

Analyze the data collected to identify common themes and pain points.

Document the identified challenges and prioritize them based on their impact on the organization's mission and operations.

Use these insights to define the scope and objectives of the new implementation project.

References:

NGO Ebook CRM For Good: Emphasizes the importance of understanding current challenges before starting new projects​​.

Nonprofit Cloud Implementation Guide: Provides best practices for identifying and documenting challenges to inform implementation strategy.

https://trailhead.salesforce.com/en/content/learn/modules/opportunity-settings-in-nonprofit-success-pack/set-up-soft-credits-npsp

https://trailhead.salesforce.com/en/content/learn/modules/donation-soft-credit-management-with-nonprofit-success-pack/create-and-manage-soft-credits

To ensure that the person being honored by a tribute gift consistently receives the proper soft credit, the nonprofit should set up Automatic Opportunity Contact Roles in NPSP and configure the Honoree role. This automation ensures that the honoree is always credited appropriately without manual intervention.

Steps:

Navigate to NPSP Settings > Donations > Automatic Opportunity Contact Roles.

Add a new Contact Role with the role type "Honoree."

Set the role to be automatically assigned to Opportunities that meet the criteria for tribute gifts.

Test the configuration by creating a new tribute gift and verifying that the Honoree Contact Role is correctly assigned.

Train staff on how to use the new setup to ensure consistency in data entry.

References:

CertGod Nonprofit Cloud Consultant Guide: Advises on configuring Automatic Opportunity Contact Roles for managing soft credits in tribute gifts​​.

Salesforce Documentation on NPSP Automatic Opportunity Contact Roles: Provides instructions on setting up and managing contact roles for Opportunities.

https://powerofus.force.com/s/article/PMM-Overview

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

To meet the reporting requirements of a new grant that expects services to be segmented according to location, the nonprofit should use the Program Cohort object. The Program Cohort object allows tracking and reporting of services provided in specific locations, making it possible to generate detailed reports that meet funder requirements.

Steps:

Configure the Program Management Module to include the necessary fields for tracking service locations within the Program Cohort object.

Ensure that all relevant data is accurately entered into the Program Cohort records, including location details.

Create custom reports and dashboards that segment services based on the location data stored in the Program Cohort object.

Regularly review and update the data to ensure accurate and up-to-date reporting for the funder.

References:

CertGod Nonprofit Cloud Consultant Guide: Discusses the use of Program Cohorts for detailed tracking and reporting of services​​.

Salesforce Documentation on Program Management Module: Provides information on the functionality and use of Program Cohorts.

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

To allow case managers to create and edit service delivery records in the Program Management Module (PMM), you should assign the appropriate permissions through Permission Sets. Permission Sets provide a way to grant specific permissions to users without changing their profiles, making it easier to manage access to certain functionalities.

Steps:

Create a Permission Set:

Navigate to Setup -> Permission Sets.

Click "New" to create a new permission set.

Grant Permissions:

In the new permission set, go to Object Settings.

Find and select "Service Deliveries."

Grant "Create" and "Edit" permissions.

Assign the Permission Set:

Assign the newly created permission set to the case managers who need access to create and edit service delivery records.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Permission Sets

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 create a custom Apex class in the TDTM (Table Driven Trigger Management) framework, follow these steps:

Create the Apex Class:

In Salesforce, go to Setup.

Navigate to "Apex Classes" under "Custom Code".

Click "New" and create your custom Apex class.

Ensure the class implements the TDTM framework correctly.

Create the Test Class:

Create a corresponding test class to ensure your Apex class functions as expected.

This is essential for maintaining code coverage and passing Salesforce deployment requirements.

Create a Trigger Handler Record:

Go to the TDTM Trigger Handlers tab.

Create a new Trigger Handler record and link it to your custom Apex class.

Define the order of execution and the object the trigger applies to.

These steps ensure that your custom Apex class is correctly integrated into the TDTM framework, maintaining organized and manageable trigger logic.

References:

Salesforce NPSP Documentation: TDTM Overview

Salesforce Trailhead: Apex Basics & Database

Enabling State and Country Picklists in Salesforce can improve data consistency and accuracy for address fields. However, there are specific considerations when using them with NPSP:

NPSP Data Import Object Doesn't Support State and Country Abbreviations in Picklist Form:

The NPSP Data Import object does not natively support state and country abbreviations in picklist form. This means that data imports using this object will require additional handling to map state and country values correctly.

Predefined State and Country Abbreviations on Address Records Must Be Used:

When using State and Country Picklists, predefined state and country abbreviations must be used. This ensures consistency and compatibility with Salesforce’s standard address fields.

If your current data uses different formats (e.g., full names or alternative abbreviations), you will need to standardize these before importing or entering data.

Consideration for Existing Data:

If enabling State and Country Picklists for the first time, review and clean existing data to match the picklist values.

Use data tools to update existing records with the correct state and country abbreviations to ensure smooth transition and consistency.

By understanding these considerations and preparing your data accordingly, you can successfully implement State and Country Picklists in NPSP.

References:

"State and Country/Territory Picklists Overview" from Salesforce Help: State and Country Picklists

"Managing Addresses in NPSP" from Salesforce Help: NPSP Address Management

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

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 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 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)

For donors who prefer to have their recurring donations three times per year, follow these steps to create a custom installment period in NPSP:

Navigate to NPSP Settings:

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

Access Recurring Donations Settings:

In NPSP Settings, click on "Donations".

Select "Recurring Donations".

Create a Custom Installment Period:

Click on "Custom Installments".

Add a new custom installment period named "Tri-Yearly" or any other preferred name.

Define the specific details for this installment period, such as frequency and dates.

Add to Installment Picklist:

Ensure the new custom installment period is added to the Recurring Donation installment picklist.

Update existing recurring donations as needed to use the new installment period.

This customization allows the organization to accommodate donors who prefer tri-yearly installments.

References:

Salesforce NPSP Documentation: Recurring Donations

Salesforce Trailhead: Recurring Donations in NPSP

To ensure that donors receive credit for new donations, the automatic Opportunity Contact Role hard credit value should be configured in NPSP Settings. Here’s how to do it:

Navigate to NPSP Settings:

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

Access Donations Settings:

Under NPSP Settings, select "Donations".

Click on "Opportunity Contact Roles".

Configure Default Contact Role:

Set the default Contact Role for Opportunities to ensure that the primary donor is automatically assigned the correct role.

This role typically is "Primary Donor" or "Donor".

Verify and Save:

Ensure that the configuration is correct and save the changes.

This setup ensures that when new donations are imported or entered, the primary donor receives the appropriate hard credit automatically, maintaining accurate donor credit records.

References:

Salesforce NPSP Documentation: Opportunity Contact Roles

Salesforce Trailhead: Manage Donations in NPSP

To identify organizations that have donated to the nonprofit in some year prior to the current year but have not contributed in the current year, the NPSP SYBUNT (Some Year But Unfortunately Not This year) report can be customized. Here’s how to do it:

Navigate to the NPSP SYBUNT Report:

Go to the Reports tab.

Find and open the NPSP SYBUNT report template.

Customize the Date Range:

Click on the “Filters” pane.

Adjust the date range filters to include donations from the desired prior years and exclude the current year.

Modify Report Criteria:

Ensure the report is filtering by Account to get the organization-level data.

Add additional filters if necessary to refine the report (e.g., specific campaign or donation types).

Run the Report:

Save and run the report to get a list of organizations that have donated in previous years but not in the current year.

By customizing the date range on the NPSP SYBUNT report for Accounts, you can easily identify and target these lapsed donors for re-engagement campaigns.

References:

"Using NPSP Reports" from Salesforce Help: NPSP Reports

"SYBUNT and LYBUNT Reports in NPSP" from Salesforce.org: SYBUNT and LYBUNT

To track the high school a student attended and their college enrollment, the consultant should recommend using the NPSP Affiliations objects:

NPSP Affiliations: This object is designed to connect Contacts to Accounts representing institutions like high schools and colleges.

Status Field: Use the Status field within the Affiliations object to indicate if the student is currently enrolled or a former student.

This approach allows the nonprofit to maintain a detailed history of the student's educational journey and easily track changes in their enrollment status.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Affiliations and Relationships in NPSP

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 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 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

To find the NPSP version number for a specific field, the consultant should reference the NPSP Public Data Dictionary. This resource provides detailed information about the fields and features introduced in different versions of NPSP.

Access NPSP Public Data Dictionary:

Go to the Power of Us Hub or the Salesforce.org website.

Navigate to the NPSP documentation section.

Search for the Field:

Use the Data Dictionary to search for the specific field in question.

Review the information provided, including the version number when the field was introduced.

Verify Field Information:

Confirm the details about the field, including any associated metadata and historical changes.

Using the NPSP Public Data Dictionary ensures accurate information about the field's history and version details.

For a nonprofit organization providing case management and requiring automatic scoring of clients based on various factors like age, income, and health conditions, along with automating the creation and assignment of follow-up tasks, the best combination of functions is Engagement Plans and Levels.

Engagement Plans: These are used to automate the creation of tasks and follow-up activities based on predefined templates. This feature ensures that specific tasks are generated and assigned to relevant staff members as soon as certain criteria are met.

Steps to Set Up Engagement Plans:

Navigate to the "Engagement Plans" tab in NPSP.

Create a new Engagement Plan Template, defining the tasks and follow-ups that should be created.

Specify the conditions under which this Engagement Plan should be triggered (e.g., a new client intake).

Assign the Engagement Plan to the appropriate client records.

Levels: These are used to categorize clients (or any other records) based on numeric values or other criteria. In this case, Levels can be used to automatically assign a score to each client based on their age, income, and health conditions.

Steps to Set Up Levels:

Navigate to NPSP Settings > Levels.

Create a new Level, specifying the criteria for each level (e.g., age range, income bracket, number of health conditions).

Define the actions that should be triggered when a client reaches a specific level.

By using Engagement Plans and Levels, the nonprofit can automate both the scoring of clients and the creation of follow-up tasks, ensuring a streamlined case management process.

References:

CertGod Nonprofit Cloud Consultant Guide:

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

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

For frequently importing membership renewal data and daily donation data with different configurations, the NPSP Data Importer is the most suitable tool. Here’s how to set it up:

Prepare Data Files:

Ensure you have separate data files for membership renewals and daily donations.

Format each file according to the required fields for the NPSP Data Importer.

Access NPSP Data Importer:

Go to the App Launcher.

Search for and open "NPSP Data Importer".

Configure Import Settings:

For membership renewals, configure the data mappings specific to membership fields (e.g., membership type, renewal date).

For daily donations, configure the data mappings for donation-related fields (e.g., donation amount, donor information).

Save Import Mappings:

Save each configuration as a template in the NPSP Data Importer.

Name the templates clearly (e.g., "Membership Renewals Import", "Daily Donations Import").

Import Data:

Upload the respective data files to the NPSP Data Importer.

Select the appropriate template for each import process.

Run the import process, ensuring data is correctly mapped and imported.

Verify and Clean Up:

Verify the imported data for accuracy.

Use the NPSP tools to manage any duplicates or discrepancies.

The NPSP Data Importer provides flexibility and efficiency for handling different types of data imports with tailored configurations.

References:

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

"Managing Data Imports with NPSP" from Salesforce.org: Data Import Management

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

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

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

When considering the Individual ("Bucket") account model for a nonprofit organization migrating to an NPSP org:

Legacy Account Model: The Individual account model is considered a legacy option and is not recommended for new implementations due to limitations in scalability and flexibility.

Account Data Skew: With a large volume of contacts, using the Individual account model can lead to data skew issues, where too many contacts are associated with a single account, causing performance and reporting challenges.

It is advisable to consider other account models like the Household Account Model, which is more suitable for managing large volumes of contacts.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Managing Account Models in NPSP

Using Case Hierarchy is the best way to relate Cases for the same client to each other in Salesforce. This allows the organization to see the connection between various Cases and manage them effectively. Here’s how to set it up:

Enable Case Hierarchy:

Ensure that the Case Hierarchy feature is enabled in your Salesforce org. This is typically enabled by default.

Create Parent and Child Cases:

When creating or editing a Case, you can specify a parent Case using the "Parent Case" lookup field.

For each new Case related to the same client, select the main Case as the parent.

View Case Hierarchy:

On the Case record page, click on "View Hierarchy" to see all related Cases in a hierarchical view.

This allows you to easily track and manage all Cases related to a specific client.

By using Case Hierarchy, you can maintain a clear structure of all Cases related to a client and ensure they are appropriately connected and managed.

References:

"Case Hierarchies" from Salesforce Help: Case Hierarchies

"Managing Cases in NPSP" from Salesforce.org: Case Management

To handle duplicate cleanup in bulk for a nonprofit organization:

Third Party App from the AppExchange: There are several apps available on the Salesforce AppExchange specifically designed for bulk duplicate management and cleanup. These apps offer advanced features for identifying and merging duplicate contacts efficiently.

Ease of Use: These third-party apps provide user-friendly interfaces and automated processes to manage duplicates, making the cleanup process more efficient and less error-prone compared to manual methods.

Using a third-party app ensures a thorough and systematic approach to duplicate management.

References:

Salesforce AppExchange: Duplicate Management Apps

Salesforce Trailhead: Managing Duplicate Records in NPSP

Updates to the Nonprofit Success Pack (NPSP) are pushed to production organizations once every two weeks. These frequent updates ensure that organizations using NPSP have access to the latest features, bug fixes, and improvements. Here’s what you need to know:

Regular Updates:

NPSP follows a bi-weekly release schedule, meaning updates are deployed approximately every two weeks.

Automatic Updates:

These updates are automatically pushed to production environments, requiring no manual intervention from administrators.

Release Notes:

Release notes for each update are published and can be accessed to understand the changes and new features included in each release.

Testing and Sandbox Environments:

It’s recommended to test updates in a sandbox environment before they are deployed to production, especially if customizations are in place.

References:

"NPSP Release Schedule" from Salesforce.org: NPSP Release Schedule

"Release Notes and Announcements" from Salesforce.org: NPSP Release Notes

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

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"​​.

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"​​.

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

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

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

Quality Assurance (QA):

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

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

Staging:

A staging sandbox is a replica of the production environment.

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

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

Development:

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

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

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

References:

Salesforce Documentation: Sandbox Types and Templates

Salesforce Trailhead: Developing in Sandboxes

To ensure that the membership rollups in NPSP work properly, the following settings need to be configured:

Check that the Membership Record Type is Selected for Membership Rollups:

Go to NPSP Settings.

Navigate to "Settings" -> "Donations" -> "Customizable Rollups".

Ensure that the membership record type is selected and configured to be included in the rollups. This allows NPSP to aggregate membership data correctly.

Ensure there is an Opportunity Record Type Set Up for Memberships:

Navigate to Setup -> Object Manager -> Opportunity.

Ensure there is a specific record type for memberships (e.g., "Membership Opportunity").

Configure this record type with the necessary fields and settings specific to membership tracking.

By ensuring these configurations are in place, NPSP can properly roll up membership data and provide accurate metrics for the organization.

References:

"Customizable Rollups in NPSP" from Salesforce Help: Customizable Rollups

"Setting Up Opportunity Record Types" from Salesforce.org: Opportunity Record Types

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.

In the Nonprofit Success Pack (NPSP), donations can be credited in two ways: hard credits and soft credits. Hard credits reflect direct donations, while soft credits are used to acknowledge indirect contributions, such as when a donor's employer matches a donation.

Hard Credits:

Hard credits represent the actual donor who made the donation.

In this scenario, the employer who matches the donation will receive a hard credit for the matched amount.

Soft Credits:

Soft credits are used to recognize individuals or entities who influenced or facilitated the donation but are not the direct donors.

The donor will receive a soft credit for the amount matched by their employer.

Scenario Application:

The donor made a donation of $500. This is a hard credit for the donor.

The employer matches this donation with another $500. The employer receives a hard credit for this matched amount.

The donor is acknowledged for facilitating the matched gift, thus receiving a soft credit of $500.

Implementation in NPSP:

To implement this, configure the Opportunity Contact Role to automatically assign soft credits to related contacts, such as employers matching donations.

Use the NPSP Settings to ensure that soft credit roles are correctly assigned and tracked.

References:

CertGod Nonprofit Cloud Consultant study guide: "The donor has a soft credit of $500 and the employer has a hard credit of $500"​​.

To ensure that the status for a Campaign Member on a fundraising campaign is automatically updated when a donation is received from that Contact, the Automatic Campaign Member Management feature in NPSP can be used. Here’s how to enable and configure it:

Navigate to NPSP Settings:

Go to Setup.

In the Quick Find box, type "NPSP Settings" and select it.

Enable Automatic Campaign Member Management:

In the NPSP Settings, navigate to "Donations".

Find the "Automatic Campaign Member Management" section.

Enable this feature by checking the corresponding box.

Configure the Settings:

Define the criteria for when and how Campaign Member statuses should be updated. For example, you can specify that the status should change to "Responded" when a donation is received.

Save Settings:

Save the changes to activate the automatic updates.

This setup ensures that Campaign Member statuses are updated automatically based on the criteria defined, reducing manual effort and improving accuracy.

References:

"Automatic Campaign Member Management" from Salesforce Help: Automatic Campaign Member Management

"NPSP Settings Overview" from Salesforce.org: NPSP Settings

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 create a report showing how much each board member has raised, you should:

Use the Opportunities report type: This allows you to capture all gift data.

Add a cross filter for Contacts with Board Member = TRUE: This filters the report to include only those contacts who are board members.

Summarize the Total Gifts this Year and Soft Credits this Year fields: This provides the total amounts for direct gifts and influenced gifts.

This method ensures that both direct contributions and soft credits (gifts influenced by board members) are included in the report.

References:

Salesforce Help: Creating and Customizing Reports

Salesforce Trailhead: Reporting for Nonprofits

The Power of Us Hub Solution Exchange is designed for nonprofit organizations using Salesforce to connect directly with other nonprofits that have similar business use cases. Here’s how to utilize this resource:

Access the Power of Us Hub:

Navigate to the Power of Us Hub (https://powerofus.force.com ).

Log in using your Salesforce credentials.

Explore the Solution Exchange:

Go to the "Solution Exchange" section within the Hub.

Browse through various solutions, discussions, and best practices shared by other nonprofits.

Connect with Similar Nonprofits:

Use the search and filter features to find nonprofits with similar use cases.

Participate in discussions, ask questions, and share your experiences.

Utilize Shared Resources:

Access shared resources, templates, and configurations that have been successful for other organizations.

Apply relevant solutions and best practices to your own organization’s use case.

The Power of Us Hub Solution Exchange is a valuable resource for collaboration and learning from the experiences of other nonprofits using Salesforce.

References:

"Power of Us Hub Overview" from Salesforce.org: Power of Us Hub

"Using the Solution Exchange" from Salesforce Help: Solution Exchange