Nonprofit-Cloud-Consultant Practice Exam Questions with Answers Salesforce Certified Nonprofit Cloud Consultant (NPC) (NP-Con-102) Certification

https://powerofus.force.com/s/article/NPSP-Which-Version-Am-I-Using

When a consultant is unsure when a particular field was added to NPSP, they can find the NPSP version number for the field in the NPSP Data Dictionary. Here’s why:

NPSP Data Dictionary:

The NPSP Data Dictionary provides comprehensive details about all fields, objects, and components within the NPSP package.

It includes information on when fields were introduced, their data types, descriptions, and related objects, making it the best resource for tracking the history of specific fields.

References:

Salesforce NPSP Data Dictionary Documentation

Salesforce Nonprofit Success Pack Release Notes

When rolling out a new implementation of Salesforce and NPSP containing custom code, especially near a Salesforce release date, it's critical to consider the following points about using a preview sandbox:

API Version Differences:

The API version in the preview sandbox may differ from the production instance. This difference can cause inconsistencies or issues when deploying code developed or tested in the preview environment to the production environment.

It’s essential to test the compatibility of your custom code and integrations with the new API version in the preview sandbox to ensure they work seamlessly once the Salesforce release is live in production.

Project Planning:

Ensure that any development or testing done in the preview sandbox accounts for potential changes introduced by the new release. Plan for additional testing post-release to verify everything functions as expected.

Deployment Strategy:

Develop a clear deployment strategy that includes thorough testing and validation in both the preview sandbox and a post-release production environment.

References:

Salesforce Release Notes

Salesforce Sandbox Preview Guide

To search for volunteers with specific skills and availability using Volunteers for Salesforce:

Use the Find Volunteers Tab:

Navigate to the Volunteers for Salesforce application within Salesforce.

Click on the "Find Volunteers" tab.

Fill in the Volunteer Criteria:

In the search form, enter the desired values for Volunteer Status, Volunteer Availability, and Volunteer Skills.

For this scenario, enter "Landscaping" in the Volunteer Skills field and specify the desired availability timeframe in the Volunteer Availability field.

Execute the Search:

Click on the "Search" button to find volunteers that match the specified criteria.

Select Volunteers:

Review the list of volunteers returned by the search.

Select the volunteers that are available at the given time and have the required landscaping skills.

This method ensures that the volunteer manager can efficiently find and assign volunteers to shifts based on their skills and availability.

References:

Volunteers for Salesforce documentation on finding and managing volunteers

CertGod Nonprofit Cloud Consultant guide?

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

To ensure that users only see Engagement Plans on Opportunity records for donations with an Amount greater than 10,000, the consultant should use component visibility filters in Lightning. Here’s the step-by-step process:

Add the Related List - Single Lightning Component:

On the Opportunity Lightning page, add the "Related List - Single" component and set it to display the Engagement Plans related list.

Component Visibility Filter:

Configure a visibility filter on the Related List component. Set the filter condition to check if the Opportunity Amount field is greater than 10,000.

This ensures that the Engagement Plans related list only appears on Opportunities where the amount exceeds the specified threshold.

References:

Salesforce Lightning App Builder Documentation

Salesforce Component Visibility Filters Guide

These solutions provide detailed steps and references to effectively configure and troubleshoot Salesforce Nonprofit Cloud settings and features.

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?

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

For a nonprofit offering courses that grant teachers credit toward maintaining their teaching certification, the Program Management Module (PMM) is the best solution to track course completions and credits awarded. PMM allows the nonprofit to manage program enrollments, track progress, and report on outcomes effectively.

Steps:

Set up the Program Management Module to include the specific courses offered and the credits awarded for each course.

Create Program Engagement records for each teacher enrolling in the annual cohort, linking them to the relevant course modules.

Track the completion of course modules and update the credits awarded to each teacher within their Program Engagement records.

Use custom reports and dashboards to monitor progress, track completions, and generate reports on credits awarded to teachers.

References:

CertGod Nonprofit Cloud Consultant Guide: Recommends using PMM for tracking program enrollments, progress, and outcomes??.

Salesforce Documentation on Program Management Module: Provides detailed instructions on setting up and using PMM for managing educational programs.

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

https://powerofus.force.com/s/article/ASL-Automate-Stage-to-State-Mappings

To export detailed accounting transactions, including pledges, to an external financial system using Accounting Subledger, the consultant should set the "Pledged" stage to "Committed" in Stage to State Mapping. Here’s why:

Stage to State Mapping:

In Accounting Subledger, the Stage to State Mapping feature allows you to map Opportunity stages to accounting states.

By setting the "Pledged" stage to "Committed," you ensure that all pledges are recognized and exported as committed transactions in the accounting system.

This setting helps in accurately reflecting the financial commitments of the nonprofit organization.

References:

Salesforce documentation on Accounting Subledger: Accounting Subledger

To ensure that a deceased donor no longer appears on any mailing lists, the nonprofit organization should 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 and open the donor’s contact record.

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Verify Exclusion from Mailing Lists:

Ensure that automated workflows and processes exclude contacts marked as deceased from email and mailing lists.

Review and update any relevant segments or mailing lists to remove the deceased donor.

This action preserves the donor’s history in Salesforce while ensuring they are no longer included in future communications.

References:

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

Changes to Engagement Plan Templates in Salesforce only affect newly created Engagement Plans. Here’s why:

Template Changes Application:

When an Engagement Plan Template is modified, the changes are not retroactively applied to existing Engagement Plans. Only new plans created after the modification will reflect the changes.

Create New Engagement Plans:

For the development manager to see the changes, new Engagement Plans need to be created using the updated template. Existing plans will retain the configuration they had at the time of creation.

Communicate Changes:

Inform relevant stakeholders about this behavior to manage expectations and plan accordingly. Consider cloning existing Engagement Plans if updates are necessary, applying the new template configurations.

Review Documentation:

Refer to Salesforce documentation on Engagement Plans for detailed information on how templates and plan instances work.

References:

Salesforce Engagement Plan Documentation

Salesforce Nonprofit Success Pack (NPSP) Resources

Salesforce Trailhead: Configure Nonprofit Success Pack Engagement Plans

To standardize addresses in NPSP, especially when dealing with large amounts of Contact address data from street canvassing and telemarketing operations, the consultant should use Address Verification:

Enable Address Verification:

In Salesforce, navigate to the NPSP Settings.

Under "Address Management," enable Address Verification.

Configure the Address Verification settings according to the needs of the nonprofit.

Use Address Verification Service:

Utilize the integrated Address Verification service to standardize and validate addresses.

The service checks addresses against a reliable database, ensuring they are accurate and properly formatted.

Batch Processing:

For large amounts of data, set up batch processing to regularly verify and standardize addresses.

This can be scheduled to run monthly or as needed to keep the address data clean and accurate.

Review and Correct:

After verification, review any addresses flagged as incorrect or incomplete and make necessary corrections.

Using Address Verification helps ensure the nonprofit's address data is accurate and standardized, improving the quality of their data management.

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation: Address Management

Salesforce Help: Configuring Address Verification

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

When implementing a Salesforce marketing automation solution, it is crucial to understand the nonprofit’s overall marketing objectives and strategy first. This foundational question will guide the consultant in aligning the marketing automation tools with the nonprofit's goals and ensuring the solution supports their broader mission. Knowing the marketing objectives and strategy will also help in tailoring the solution to effectively target the right audience, measure success, and adjust tactics as needed.

References:

Salesforce Nonprofit Cloud Consultant Study Guide

Marketing Cloud Implementation Guide

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

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

When a nonprofit creates a custom Opportunity Name for all in-kind gifts, it is important to understand how this change impacts existing and new Opportunity records. The Refresh All Opportunity Names utility can be used to update the names of existing Opportunities to match the new naming convention. Additionally, the custom Opportunity Name Format will only apply to new Opportunities that match the specified record type.

Steps:

Update the Opportunity Name Format settings to reflect the new naming convention for in-kind gifts.

Use the Refresh All Opportunity Names utility to apply the new naming convention to existing Opportunities. This ensures consistency across all records.

Inform users that the new naming convention will only be automatically applied to new Opportunities created with the matching record type going forward.

Monitor the changes and verify that the updated names meet the nonprofit's requirements.

References:

CertGod Nonprofit Cloud Consultant Guide: Provides guidance on updating Opportunity names and using utilities for bulk updates??.

Salesforce Documentation on Opportunity Name Formats: Details the steps for configuring and applying custom naming conventions.

To ensure full compliance with Salesforce best practices for data security, the consultant should use Salesforce Health Check. Here’s why:

Salesforce Health Check:

This tool provides a comprehensive security assessment of your Salesforce org by measuring its settings against the Salesforce recommended baseline.

It evaluates critical security settings such as password policies, session settings, and other security configurations.

Health Check provides a score and recommendations to improve the overall security posture of the org, making it a crucial tool for maintaining data security compliance.

References:

Salesforce Health Check Documentation

Salesforce Security Best Practices Guide

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

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

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

To provide support for clients through a real-time chat interface with a staff member, a consultant should recommend Digital Engagement.

Digital Engagement:

Salesforce Digital Engagement allows nonprofits to connect with their clients in real-time through various digital channels, including chat, messaging apps, and social media.

It integrates with Service Cloud to provide a seamless experience for both clients and support staff, enabling real-time interactions and efficient case management.

To collect information online about new volunteers, including names, contact details, skill sets, and availability, and create a report with this information, the following solutions are recommended:

Collect Contact Information During Job Sign Up:

Use the Job Listings feature in Volunteers for Salesforce to capture volunteer information during the job sign-up process.

Ensure that the sign-up form includes fields for contact details, skill sets, and availability.

Steps to Set Up Job Listings:

Navigate to the Volunteers for Salesforce setup.

Configure job listings and ensure the sign-up forms capture all necessary information.

Add the Volunteer Sign Up Form to the Nonprofit's Website:

Create a Volunteer Sign Up form and embed it on the nonprofit’s website.

Use the Volunteers for Salesforce Web-to-Volunteer feature to automatically capture and create records in Salesforce.

Steps to Set Up Web-to-Volunteer:

Go to Volunteers for Salesforce settings.

Set up the Web-to-Volunteer form with the required fields.

Embed the form on the nonprofit’s website.

These methods ensure that all relevant volunteer information is captured and stored in Salesforce, allowing for easy reporting and management.

References:

Volunteers for Salesforce Documentation

Salesforce Help: Setting Up Web-to-Volunteer Forms

Top of Form

Bottom of Form

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

Salesforce.org major releases are typically scheduled to follow Salesforce.com releases by about one month. This staggered release schedule allows nonprofits to prepare for updates and ensures that they can address any potential conflicts with their internal release schedules. The Salesforce.org release schedule is available on the SFDO Major Release Announcements group, which provides detailed information on upcoming releases and related resources.

Steps:

Inform the system admin that Salesforce.org releases follow Salesforce.com releases by approximately one month.

Direct the system admin to the SFDO Major Release Announcements group for the latest release schedule information.

Encourage the admin to plan internal releases accordingly to avoid conflicts with major Salesforce updates.

Stay informed about upcoming releases and leverage available resources to ensure smooth transitions.

References:

CertGod Nonprofit Cloud Consultant Guide: Provides information on the release schedules and where to find them??.

Salesforce.org Major Release Announcements Group: Source for detailed release schedules and updates.

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 restrict access to fields related to background checks on the Contact object so that only the volunteer manager and executive director can access them, the consultant should:

Create a Permission Set:

A permission set is a collection of settings and permissions that gives users access to various tools and functions.

Creating a permission set that includes access to the specific fields related to background checks allows for precise control over who can view and edit these fields.

Grant Field-Level Security:

Within the permission set, set field-level security to ensure only the specified users can view and edit the background check fields.

This ensures that sensitive information is only accessible to authorized personnel.

Assign the Permission Set:

Assign the permission set to the volunteer manager and executive director.

This approach provides flexibility and security, ensuring that only the designated users have the necessary access without altering the overall role hierarchy or creating unnecessary sharing rules.

References:

Salesforce documentation on Permission Sets: Permission Sets

These solutions ensure efficient and secure handling of data and permissions within the Salesforce Nonprofit Cloud.

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?

Customizable Rollups in NPSP provide a flexible way to manage rollup calculations for donations and other records. However, once Customizable Rollups are enabled, the action is irreversible. This means you cannot revert to the standard rollup settings after enabling Customizable Rollups.

Steps to Enable:

Enable Customizable Rollups:

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

Enable the Customizable Rollups feature.

Configure Rollups:

Set up the necessary rollup rules and configurations to match the nonprofit's data tracking and reporting needs.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Configure Customizable Rollups in NPSP

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.

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 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 run an enrollment report for education classes in Salesforce using the Program Management Module (PMM), the "Program Engagement" object is the most appropriate. Here are the steps to create such a report:

Understand Program Engagements:

Program Engagements track the relationship between a participant (Contact) and the program (Program) they are enrolled in. This object captures key details like enrollment status, start and end dates, and related services.

Create a Custom Report Type:

Navigate to Setup > Report Types.

Click "New Custom Report Type."

Select "Program Engagement" as the primary object.

Define the relationships with related objects such as Contacts and Programs.

Build the Enrollment Report:

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

Select the custom report type you just created.

Add relevant fields such as Participant Name (Contact), Program Name, Enrollment Status, Start Date, and End Date.

Apply filters to narrow down the report to specific classes or time periods as needed.

Customize and Save the Report:

Group the report by Program Name or Participant Name to get a clear view of enrollments.

Add summary fields to count enrollments or calculate averages if needed.

Save and run the report to view the enrollment data.

References:

Salesforce Program Management Module Documentation: Detailed instructions on setting up and using PMM for managing programs and engagements. Salesforce PMM Documentation.

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 a system administrator attempts to delete a Household Account record that has Contacts with Recurring Donations, Relationships, and closed/won donations, Salesforce will display an error message due to the presence of closed/won donations associated with the Account record.

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

Navigate to the Household Account:

Go to the Accounts tab and locate the Household Account record.

Attempt to Delete the Account:

Try to delete the Household Account record.

Salesforce will prevent the deletion and display an error message because there are closed/won donations linked to this Account.

Review Associated Records:

Check for closed/won Opportunities and other related records that are preventing deletion.

If necessary, consider reassigning or archiving these records instead of deleting the Household Account.

This safeguard ensures data integrity by preventing the loss of critical financial records.

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

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

When a corporate matching gift is received and the original donor did not indicate that it was to be matched, the consultant should recommend using the "Find Matched Gifts" feature. This feature helps in identifying and linking the matching gift to the original donation:

Select Find Matched Gifts: This option is available within the Nonprofit Success Pack (NPSP) and is designed to help match donations.

Click on the Find More Gifts button: This button will allow the development associate to search for and match the original donation with the corporate matching gift.

This process ensures that all matched gifts are accurately recorded and credited appropriately.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Matching Gifts in NPSP

The most efficient way to install NPSP in an existing Salesforce organization is to use the NPSP Installer. Here’s how to do it:

Access the NPSP Installer Page:

Go to the NPSP Installer page: NPSP Installer

This page provides the latest version of NPSP and installation instructions.

Initiate the Installation:

Click on the installation link for the latest NPSP version.

Log in to your Salesforce org where you want to install NPSP.

Follow the Installation Wizard:

Follow the prompts in the installation wizard to complete the installation.

Choose the appropriate options based on your organization’s needs (e.g., data model selection, configurations).

Complete Post-Install Instructions:

After installation, follow the post-install instructions provided in the documentation. This might include configuring NPSP settings, setting up users, and data import processes.

By following these steps, you can ensure that NPSP is correctly installed and configured in your Salesforce organization.

References:

"Installing NPSP" from Salesforce.org: Installing NPSP

"Post-Install Configuration" from Salesforce Help: Post-Install Configuration

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

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

A https://www.freecram.com/question/Salesforce.Nonprofit-Cloud-Consultant.v2021-01-10.q37/a-nonprofit-organization-has-been-using-salesforce-without-npsp-the-organization-is-now-interested-in ((see in comments)

To evaluate and recommend whether to use NPSP in the same Salesforce environment or start over in a new environment, the consultant should use Salesforce Optimizer. Salesforce Optimizer provides a comprehensive report that evaluates the current Salesforce org and identifies areas for improvement and optimization.

Log in to Salesforce: Access the Salesforce org.

Navigate to Salesforce Optimizer: Go to Setup, search for "Optimizer", and select "Salesforce Optimizer".

Run Salesforce Optimizer:

Click "Run Optimizer".

Wait for the evaluation to complete. Salesforce Optimizer will generate a detailed report.

Review the Report:

Analyze the report to understand the current state of the Salesforce environment.

Look for insights related to customizations, data quality, and system usage.

Make a Recommendation:

Based on the findings, determine if the existing environment is suitable for implementing NPSP.

If significant issues or customizations are found, consider starting over in a new environment.

Using Salesforce Optimizer helps ensure an informed decision based on the health and suitability of the current Salesforce environment.

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

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

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

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

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

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.

To locate NPSP release information, two key places are:

Power of Us Hub: This is a community for Salesforce.org customers, where they can access release notes, documentation, and discussions about NPSP updates.

GitHub Cumulus Releases: This repository contains detailed release information, including new features, bug fixes, and enhancements for NPSP.

These sources provide comprehensive and up-to-date information on NPSP releases.

References:

Power of Us Hub

GitHub Cumulus Releases Repository

To ensure that the Donor Advised Fund (DAF) receives credit for donations, using Account Soft Credits is the best approach. Here’s how to set this up:

Navigate to NPSP Settings:

Go to Setup.

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

Configure Soft Credits:

In NPSP Settings, navigate to "Donations" -> "Soft Credits".

Ensure that soft credits are enabled for Accounts and Contacts.

Add Soft Credits on Opportunities:

When entering a donation, go to the Opportunity record.

Add a new soft credit for the DAF by selecting the appropriate Account (the financial institution housing the DAF).

Specify the role as "Donor Advised Fund" or similar.

Track and Report:

Use Opportunity reports to track soft credits and generate reports showing the contributions attributed to the DAF.

Using soft credits allows the organization to properly credit the DAF for donations without altering the primary donor records.

References:

"Managing Soft Credits in NPSP" from Salesforce Help: Soft Credits

"Tracking Donor-Advised Funds" from Salesforce.org: Donor-Advised Funds

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 track nested campaigns effectively, Salesforce Campaign Hierarchies can be utilized. Here are the steps to set this up:

Create Parent Campaign:

Create the top-level parent Campaign called "Friends of the Organization".

Create Sub-Campaigns:

Create sub-campaigns under the parent campaign for each hierarchical level: FY19, Capital Campaign, Annual Fund, Digital Donations, and Mobile.

Link each sub-campaign to its parent campaign using the Parent Campaign lookup field.

Configure Campaign Hierarchy Settings:

Ensure the Campaign Hierarchy settings are configured to allow for the desired depth of nested campaigns.

Track Campaign Performance:

Use Campaign Hierarchy reports to track the performance of each campaign within the hierarchy.

Analyze metrics such as total donations, engagement, and conversion rates at each level.

By creating a structured Campaign Hierarchy, the nonprofit can effectively track and manage complex campaign structures, gaining insights into performance at each level of the hierarchy.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Campaign Management

Understanding the trial experiences available on the Salesforce.org website is crucial for setting expectations and planning custom configuration work. Here’s detailed information about the trial options:

Available Trial Experiences:

Lightning Enterprise: This option provides a standard Salesforce Lightning Enterprise edition, suitable for exploring core CRM capabilities.

Lightning Enterprise + NPSP: This trial includes the Nonprofit Success Pack (NPSP) on top of the Lightning Enterprise edition, tailored specifically for nonprofit needs.

Free Trial Period:

The free trial period for Salesforce.org trials is 30 days. This provides enough time to explore features, gather requirements, and conduct initial custom configuration work.

Why Not Other Options:

Option A: While free licenses may be available for qualified customers, this is separate from the trial experience and not universally applicable.

Option D: The trial orgs provided by Salesforce.org are typically not Developer Edition orgs but are configured to showcase the Enterprise capabilities with or without NPSP.

By knowing that the trial choices include Lightning Enterprise or Lightning Enterprise + NPSP and that the free trial period is for 30 days, the consultant can effectively plan and execute the initial phases of the project.

References:

Salesforce.org Trial Experiences Information

Salesforce Nonprofit Success Pack (NPSP) Documentation

When there is a conflict between business lines regarding the addition of a new field that one line of business deems essential and another objects to, the best approach is to use the established governance committee for discussion and resolution. This ensures a structured and balanced decision-making process.

Governance Committee:

The governance committee typically includes representatives from various departments and stakeholders.

They oversee and manage changes, ensuring alignment with organizational goals and policies.

Discussion and Resolution:

Present the conflicting requirements to the governance committee.

Facilitate a discussion to understand the needs and concerns of both business lines.

Evaluate the impact of adding the field versus the potential for duplicate data and other issues.

Decision Making:

The committee will make an informed decision based on the overall benefit to the organization.

This decision will be documented and communicated to all relevant parties.

By leveraging the governance committee, the consultant ensures that the decision is made transparently, with input from all stakeholders, and in alignment with organizational policies.

References:

CertGod Nonprofit Cloud Consultant Guide

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

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

For maintaining an audit trail of metadata changes over time and developing, testing, and releasing projects independently, the recommended development model is:

Package Development: This model supports modular development, allowing developers to create, test, and deploy packages independently. It provides version control and a clear audit trail of changes, ensuring that metadata changes are tracked and managed efficiently.

Independent Projects: Package development allows multiple projects to be developed in parallel without interference, making it ideal for complex environments with multiple ongoing initiatives.

Package development provides the structure and control needed for managing metadata and development processes effectively.

References:

Salesforce DX and Package Development Documentation

Salesforce Trailhead: Package Development

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

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

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

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

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

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

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

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.

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

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 enhance the security of Salesforce usernames and passwords and prevent them from being compromised, setting up two-factor authentication (2FA) is the recommended approach. Here’s how to implement it:

Enable Two-Factor Authentication for the Org:

Navigate to Setup.

In the Quick Find box, type "Two-Factor Authentication" and select it.

Enable 2FA at the organization level.

Assign 2FA to User Profiles:

Go to the user profiles that require 2FA.

Under the profile settings, enable the requirement for two-factor authentication.

Configure 2FA Methods:

Allow users to register their preferred authentication method (e.g., Salesforce Authenticator app, SMS, email, or third-party authenticator apps).

Ensure users set up their 2FA methods through their personal settings.

User Training and Support:

Provide training materials and support to help users understand and set up 2FA.

Offer assistance for troubleshooting common issues during the setup process.

Monitor and Enforce:

Use Salesforce’s monitoring tools to ensure compliance with 2FA requirements.

Regularly review and update security policies to maintain a high level of security.

Implementing two-factor authentication significantly reduces the risk of account compromise by adding an extra layer of security beyond just usernames and passwords.

References:

"Setting Up Two-Factor Authentication" from Salesforce Help: Two-Factor Authentication

"Salesforce Authenticator" from Salesforce Help: Salesforce Authenticator

Before upgrading from version 2 to version 3 of NPSP, the consultant should:

Run NPSP Health Check: This tool identifies potential issues in the current NPSP configuration, including deprecated fields, custom objects, and other configurations that might cause problems during the upgrade.

Running NPSP Health Check ensures that the upgrade process goes smoothly by addressing any issues beforehand.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Upgrading NPSP

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 generating mailing labels for a direct mail campaign in Salesforce Nonprofit Cloud, it's essential to use the correct object and address field, especially when the organization employs the Household Account model with Address Management. Here’s a detailed explanation:

Understanding Household Account Model:

The Household Account model in Salesforce Nonprofit Cloud groups related contacts under a single account, representing a household. This model helps nonprofits manage donor relationships effectively.

Scenario Explanation:

The fundraising associate needs to print mailing labels for families who give to the organization. The key is to pull the correct address for each family.

Steps to Build the Report:

Choose the Contact Object: In Salesforce, the Contact object holds individual donor details, including their addresses. When using the Household Account model, the address information is managed at the contact level.

Select the Mailing Address Field:

Navigate to Reports in Salesforce and create a new report based on the Contacts & Accounts report type.

Include the necessary fields such as Contact Name and Mailing Address.

Filter for Donors: Apply filters to ensure you are only including contacts who are donors. This can be based on donation history or related opportunities.

Format for Mailing Labels: Adjust the report format to ensure it can be used for mailing labels. This might involve creating a custom report format or exporting the data for use in an external mailing label tool.

Why Not Other Options:

Option A: Using the Account object and Billing Address is inappropriate because the Billing Address often pertains to the primary address for account records, which might not accurately reflect the household mailing address.

Option B: Contact’s Other Address field is typically used for secondary addresses and not the primary mailing address.

Option C: Account’s Shipping Address is also less relevant for mailing labels within the context of Household Account models where individual contact addresses are used.

By using the Contact object and the Mailing Address field, the fundraising associate can ensure that the mailing labels are accurate and reflect the correct addresses for each donor family.

References:

Salesforce Nonprofit Cloud Documentation on Household Account Model

Salesforce Reports and Dashboards Guide

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