Salesforce Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (SU24) Exam Practice Test

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 determine if an acknowledgment letter was sent for a donation, the best approach is to check the "Acknowledgement Status" picklist value on the Opportunity object. Here's how you can do it:

Navigate to the Opportunity Object:

Go to the App Launcher and find Opportunities.

Add the Acknowledgement Status Field:

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

Navigate to Setup.

In the Object Manager, select Opportunity.

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

Review the Acknowledgement Status:

Open the Opportunity record for the donation in question.

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

Automate Tracking (Optional):

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

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation: Managing Acknowledgments

Salesforce Trailhead: Opportunities and Donations

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 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 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 setting up Volunteers for Salesforce in an international context, it's important to ensure that volunteer jobs and shifts reflect the local time zones accurately. Here’s how to configure this:

Navigate to Volunteers for Salesforce Settings:

Go to Setup.

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

Configure Volunteer Jobs:

Create Volunteer Jobs for each country.

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

Adjust Volunteer Shift Times:

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

Update Website Information:

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

References:

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

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

To ensure that all child Opportunities contain the unique reference number from the Recurring Donation object and to prevent modifications after creation, follow these steps:

Create a Custom Text Field on the Opportunity Object:

Navigate to Setup.

In the Object Manager, select Opportunity.

Click on Fields & Relationships.

Create a new Text field (e.g., "Recurring Donation Reference Number").

Use NPSP Recurring Donation Custom Field Mappings:

Navigate to NPSP Settings.

Under "Donations", select "Recurring Donations".

Go to "Field Mappings".

Map the custom text field on the Recurring Donation object to the custom text field on the Opportunity object.

Ensure Field-Level Security:

Set the field-level security for the custom fields to ensure that they are only editable by the required profiles and read-only for others.

By following these steps, the unique reference number will be automatically populated and synchronized from the Recurring Donation object to all child Opportunities, and it will remain consistent for reconciliation purposes.

References:

Salesforce NPSP Documentation: Custom Field Mapping

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Settings

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

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.

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

Account: Import accounts first to establish the primary records.

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

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

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

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

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

References:

Salesforce Data Import Best Practices

Salesforce Trailhead: Data Import Wizard and Data Loader

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

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

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

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

Relationships in NPSP:

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

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

Adding Relationships Manually:

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

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

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

Save the relationship record.

Why Manual Entry:

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

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

Use Cases:

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

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

Benefits:

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

Enhances reporting and analysis of donor and constituent relationships.

References:

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

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

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

Data Quality Analysis Dashboard:

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

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

Steps to Ensure Consistency:

Run the Data Quality Analysis Dashboard:

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

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

Address Identified Issues:

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

Regular Monitoring:

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

Benefits of Consistency:

Ensures accurate reporting and analytics.

Improves data integrity and usability across the organization.

Facilitates better donor and constituent management.

Complementary Tools:

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

References:

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

To 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 capture information for grants and easily access previous grant details, the following setup can be used in Salesforce:

Previous Grant/Gift Opportunity Lookup Field:

Add a lookup field on the Opportunity object called "Previous Grant/Gift Opportunity".

When creating a new grant Opportunity, fill in this field with the previous grant's Opportunity record.

Is Grant Renewal Checkbox:

Add a checkbox field on the Opportunity object called "Is Grant Renewal".

Check this box for Opportunities that are renewals of previous grants.

Grant Tracking and Reporting:

This setup allows easy tracking of grant renewals and provides a straightforward way to report on grants and their renewals.

Use reports and dashboards to summarize and analyze grant data, including renewals.

By linking each renewal grant to the original grant Opportunity, you maintain a clear record of the grant history, making it easy to access previous grant information and analyze grant renewals.

References:

"Grant Management Best Practices" from Salesforce Help: Grant Management

"Nonprofit Success Pack Grant Management" from Salesforce.org: NPSP Grant Management

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

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

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

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

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

Creating the Report:

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

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

Configuring the Report:

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

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

Adding to Campaign:

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

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

Benefits of This Approach:

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

Streamlines the process of managing Campaigns and associated donor information.

Additional Steps:

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

References:

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

For managing social media presence, listening to constituents, measuring impact, and managing activities from a mobile app, Salesforce's Social Studio is the recommended tool.

Social Studio Overview:

Social Studio is a powerful social media management tool within Salesforce.

It provides capabilities for social listening, publishing, engagement, and analytics across multiple social media platforms.

Features and Capabilities:

Social Listening:

Monitor social media channels for mentions, comments, and conversations about the organization.

Identify trends and sentiment to understand constituent engagement and feedback.

Publishing:

Schedule and publish content across multiple social media platforms.

Manage social media campaigns and track their performance.

Engagement:

Interact with constituents directly from the platform.

Manage responses and engage with the audience in real-time.

Analytics:

Measure the impact of social media activities.

Use dashboards and reports to gain insights into engagement, reach, and sentiment.

Mobile App Management:

Social Studio includes a mobile app that allows users to manage social media activities on the go.

This ensures that social media management is not limited to the desktop and can be handled efficiently from anywhere.

Implementation:

Set up Social Studio within the Salesforce environment.

Configure social media accounts and start tracking and managing social media activities.

References:

CertGod Nonprofit Cloud Consultant study guide: "Social Studio"​​.

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

For suggesting new features in NPSP, the recommended resource is:

Power of Us Hub: This is a community platform specifically for Salesforce.org customers. It includes forums, idea exchanges, and collaboration spaces where nonprofit users can suggest and discuss new features for NPSP.

The Power of Us Hub is the central place for engaging with the Salesforce nonprofit community and influencing future product development.

References:

Power of Us Hub

Salesforce Trailhead: Engaging with the Salesforce Nonprofit Community

For a nonprofit organization seeking a multi-channel marketing tool that encompasses email, social media, and text messaging engagement, Salesforce Marketing Cloud is the recommended solution. Marketing Cloud provides comprehensive tools for creating, managing, and analyzing campaigns across multiple channels.

Email Marketing:

Design and send personalized emails to supporters.

Use Email Studio within Marketing Cloud for advanced email campaign management.

Social Media Engagement:

Utilize Social Studio to manage social media accounts, schedule posts, and analyze engagement.

Monitor social media conversations and engage with constituents.

Text Messaging:

Implement Mobile Studio for SMS and MMS campaigns.

Create and automate text messaging campaigns to reach supporters on their mobile devices.

Marketing Cloud's integration capabilities and robust analytics ensure that nonprofits can effectively track and optimize their multi-channel engagement efforts.

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

To address the VP of development's needs:

Review Existing Dashboard: Start by reviewing the existing components on the NPSP Development Forecasting dashboard. This provides a high-level view of the current giving pipeline.

Create Additional Reports: Develop new reports to track program metrics and compare them to donor histories. These new reports should capture the necessary program data.

Edit Dashboard: Modify the existing dashboard to include the new components that reflect the additional program data and metrics.

This approach leverages the existing infrastructure and enhances it to meet the organization's specific needs.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Customizing Dashboards in NPSP

When migrating a large volume of contacts, organizations, and address records into NPSP, it is essential to consider the following:

Complexity with the Address Object:

Using the Address object to track addresses can introduce complexity, especially if multiple addresses per contact or organization need to be managed. This complexity arises from the need to ensure all address records are correctly linked and maintained.

Impact on Data Storage:

Migrating all historical address information can significantly impact system data storage. Salesforce has storage limits, and large volumes of data can quickly consume available storage. It is important to plan for data storage needs and consider archiving or summarizing historical data to manage storage usage effectively.

Steps for Migration:

Data Preparation:

Clean and standardize the data before migration to ensure consistency.

Identify and remove duplicates to avoid data redundancy.

Data Mapping:

Map the fields from the legacy system to the corresponding fields in NPSP, including custom fields if necessary.

Data Import Tools:

Use Salesforce Data Loader or the NPSP Data Importer for the migration process.

Import data in batches, starting with Accounts, followed by Contacts, and then address information.

Testing and Validation:

Test the migration in a sandbox environment to identify and resolve any issues.

Validate the imported data to ensure accuracy and completeness.

References:

"Data Import Strategies for Nonprofits" from Salesforce Help: Data Import Strategies

"Address Management in NPSP" from Salesforce.org: Address Management

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 website visitors who download white papers, case studies, and impact reports, and subsequently pursue them as constituents, Pardot is the recommended solution. Pardot provides robust marketing automation features that can effectively manage and nurture leads. Here’s how to set it up:

Install Pardot:

Purchase Pardot and install it in your Salesforce org.

Configure Pardot Tracking:

Add Pardot tracking code to your website.

This code will track visitor behavior, including downloads of white papers, case studies, and impact reports.

Create Pardot Forms and Landing Pages:

Use Pardot to create forms and landing pages for visitors to fill out before they can download the assets.

These forms will capture visitor information and automatically create a prospect in Pardot.

Set Up Automation Rules:

Create automation rules in Pardot to add prospects to specific lists based on their behavior.

For example, create a rule to add a prospect to a "White Paper Download" list if they download a white paper.

Sync Pardot with Salesforce:

Ensure that Pardot is integrated with Salesforce to sync prospects as leads or contacts.

Use Salesforce campaigns to track these leads and monitor their progress.

Nurture Leads:

Use Pardot’s email marketing and nurturing capabilities to engage with these leads.

Track their interactions and score them based on their engagement to prioritize follow-ups.

By using Pardot, the nonprofit can efficiently track and engage website visitors, converting them into valuable constituents.

References:

Salesforce Pardot Documentation: Pardot Tracking Code

Salesforce Trailhead: Marketing Automation with Pardot

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

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

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

Define Levels in NPSP:

Navigate to NPSP Settings > Levels.

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

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

Gold: $10,000 and above

Silver: $5,000 to $9,999

Bronze: $1,000 to $4,999

Configure Level Criteria:

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

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

Assign Levels to Donors:

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

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

References:

CertGod Nonprofit Cloud Consultant Guide:

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

Household Account:

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

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

Primary Affiliation:

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

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

References:

CertGod Nonprofit Cloud Consultant Guide

When 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

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

When a corporate matching gift is received and the original donation was not marked to be matched, you should use the "Find Matched Gifts" functionality:

Navigate to Find Matched Gifts:

Go to the donation record in Salesforce.

Select "Find Matched Gifts" from the related options.

Find More Gifts:

Click on the "Find More Gifts" button to search for the original donation that matches the corporate gift.

This tool helps to locate and link the matching gift to the original donation, ensuring both donations are accurately recorded and associated.

References:

Salesforce Nonprofit Success Pack (NPSP) Documentation

Salesforce Help: Managing Matched Gifts

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.

To track grants, scholarships, and training programs in Salesforce for a nonprofit, you should use a combination of the Program Management Module (PMM), Outbound Funds Module (OFM), and Education Data Architecture (EDA). Here's how to set it up:

Track Grants with PMM:

Use the Program Management Module to manage the grants your nonprofit receives.

Create Program records for each grant and link them to the related donor accounts.

Track details such as grant amount, application status, and reporting requirements using custom fields or standard fields in PMM.

Track Scholarships with OFM:

Install and configure the Outbound Funds Module to manage scholarships.

Create Funding Programs for different types of scholarships.

Use the Funding Requests object to track individual scholarship applications and awards, linking them to the recipients (Contacts).

Track Training Programs with EDA:

Implement the Education Data Architecture to manage training programs.

Create Program records for each training program.

Use the Course Connections object to link participants (Contacts) to the training programs and track their progress.

Integrate and Report:

Use Salesforce's reporting tools to create integrated reports across these modules.

For example, you can create a report that shows the total grants received, scholarships awarded, and participants enrolled in training programs.

References:

Salesforce Program Management Module Documentation: PMM Documentation.

Salesforce Outbound Funds Module Documentation: OFM Documentation.

Salesforce Education Data Architecture Documentation: EDA Documentation.

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.

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​

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

GAU Allocation Record:

General Accounting Units (GAUs) are used in NPSP to allocate portions of donations to specific funds or purposes.

Creating a GAU Allocation record allows the nonprofit to specify the amount of each donation that should be allocated to the designated fund, ensuring accurate tracking and reporting.

References:

Salesforce NPSP Documentation on General Accounting Units (GAUs)

Salesforce Nonprofit Success Pack GAU Allocation Guide

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 track the volunteer's relationship with Universal Containers, the consultant should create an Affiliation record. Here’s why:

Affiliation Record:

In NPSP, Affiliation records are used to track the relationship between Contacts (individuals) and Accounts (organizations).

Creating an Affiliation record between the volunteer (who is a Contact) and Universal Containers (an Organization Account) effectively captures the volunteer's association with the company.

This method aligns with NPSP best practices for managing relationships and affiliations within the nonprofit's Salesforce instance.

References:

Salesforce Nonprofit Success Pack Documentation on Affiliations

Salesforce NPSP Account and Contact Management Guide

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

When a system admin attempts to delete a Household Account record that has Contacts with Affiliations, Relationships, and Closed/Won donations associated with it, Salesforce will prevent the deletion and display an error message. Here’s why:

Closed/Won Donations:

Salesforce prevents the deletion of records that have important related records, such as Closed/Won donations, to maintain data integrity.

Closed/Won Opportunities represent actual donations that are crucial for reporting and financial tracking. Deleting the associated Household Account would disrupt this data integrity.

Error Message:

Salesforce will display an error message indicating that the record cannot be deleted because of its associated Closed/Won donations. This safeguard ensures that critical financial data is preserved.

References:

Salesforce Documentation on Record Deletion and Related Records

Salesforce NPSP Data Integrity and Protection Guide

,and “D”.( When importing data into the NPSP Data Import Object, if the error message indicates that the Record ID field is not mapped, the system admin should ensure that the appropriate mapping is set up and use the correct operation for the data loader.

Select the Appropriate Record ID (A):

In the Salesforce Data Import Wizard, ensure that the Record ID field is correctly mapped. This field is required for updating existing records or ensuring data integrity.

Select "Upsert" Operation (C):

When using the Salesforce Data Loader, choose the "Upsert" operation. This allows the system to insert new records or update existing ones based on the Record ID or an external ID, ensuring that duplicates are avoided and data is accurately imported.

Steps to Resolve:

Check Field Mapping:

Verify that the Record ID field is mapped correctly in the import wizard or data loader.

Choose Upsert Operation:

If using the Data Loader, select the "Upsert" option to handle both insertions and updates.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Import Data for Nonprofits

To send automated renewal emails on a 30/60/90/180-day cadence with different email templates based on members' website visits, Pardot is the recommended solution:

Pardot for Email Automation:

Pardot is Salesforce’s B2B marketing automation solution that can handle complex email automation requirements.

It allows you to create automated email campaigns based on specific triggers and criteria, such as website visits and renewal dates.

Setting Up Pardot Automation:

Create dynamic lists in Pardot that segment members based on their renewal dates (30/60/90/180 days).

Design and create different email templates for each segment.

Use Pardot's Engagement Studio to build automated workflows that send the appropriate email template to each segment based on the criteria.

Tracking and Reporting:

Pardot provides detailed tracking and reporting on email engagement, allowing you to monitor the effectiveness of your renewal campaigns.

Using Pardot, the nonprofit can create personalized and timely renewal emails, improving member engagement and renewal rates.

References:

Salesforce Pardot Documentation

Trailhead: Automate Marketing to Businesses with Pardot

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.

When donation totals on donor records are not showing correctly in NPSP, one common issue is that the Customizable Rollups might be configured incorrectly. Specifically, it's crucial to verify that the correct target custom field is chosen for the rollup calculations.

Steps to Troubleshoot:

Check Customizable Rollups Settings:

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

Review the rollup configurations to ensure that the correct fields are selected as targets for the rollup calculations.

Verify Target Fields:

Confirm that the fields where the totals should appear are correctly mapped in the rollup settings.

Ensure there are no discrepancies or misconfigurations that might cause incorrect calculations.

Review Opportunity Primary Contact:

While the primary contact verification is less likely to affect donation totals directly, it’s good practice to check that the opportunities are correctly associated with the primary contacts.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Configure Customizable Rollups in NPSP

To prepare for a new release of an open-source Nonprofit Cloud product, the system admin should check the following sources for release notes:

Nonprofit Hub Group in the Trailblazer Community:

The Trailblazer Community is a rich resource for Salesforce users, including non-profits. The Nonprofit Hub group frequently posts updates, discussions, and release notes related to Nonprofit Cloud products.

This group can be accessed by logging into the Trailblazer Community and searching for "Nonprofit Hub."

GitHub Repository Release Page:

For open-source products, the official GitHub repository is a primary source for release notes. The release page on GitHub will have detailed notes about new features, bug fixes, and enhancements.

To access, navigate to the product’s GitHub repository and click on the “Releases” tab.

References:

Trailblazer Community: Nonprofit Hub Group

GitHub: Product’s repository release page

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

When loading a large volume of historical data into Salesforce, especially data spanning several years, it is common to encounter performance issues like the "Apex CPU Time Limit Exceeded" error. This error occurs because Salesforce processes each record with all active triggers, which can consume a significant amount of processing time.

Steps to Resolve:

Disable Trigger Handlers:

Navigate to NPSP Settings -> Trigger Handlers.

Uncheck the Active checkbox for all Trigger Handlers. This will temporarily disable the triggers, allowing the data to load without the additional processing overhead.

Load Da

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 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 for a nonprofit, the following steps can significantly speed up the process:

Defer Sharing Rule Calculation:

Defer the sharing rule calculations during the data load process. This prevents Salesforce from recalculating sharing rules for each record as it is loaded, which can slow down the process considerably.

After the data load is complete, you can manually trigger the sharing rule recalculations.

Steps to Defer Sharing Rule Calculation:

Go to Setup.

Enter "Defer Sharing Calculations" in the Quick Find box.

Enable the deferment option before starting the data load.

Disable Related Apex Classes in TDTM:

Temporarily disable Apex triggers and classes in the TDTM (Table Driven Trigger Management) framework to reduce processing overhead during the data load.

This ensures that the system doesn't execute complex Apex code for each record being loaded.

Steps to Disable Related Apex Classes in TDTM:

Go to NPSP Settings.

Navigate to TDTM (Table Driven Trigger Management).

Identify and disable the relevant triggers and classes temporarily.

These steps help streamline the data loading process by minimizing the processing and recalculations that Salesforce would otherwise perform on each record.

References:

Salesforce Help: Defer Sharing Rule Calculation

Nonprofit Success Pack (NPSP) Documentation: Managing TDTM Settings

To troubleshoot the error message "Npsp,TDTMCContact

of AfterUpdate caused by : System,SObjectException

field gender_c Contact (npsp)," the admin should:

Check for Invalid Values:

The error indicates that there might be invalid values in the gender field on Contact records.

Review the values in the gender field across the Contact records to ensure they conform to the expected values (e.g., Male, Female, Non-binary).

Steps to Verify and Correct Values:

Use Salesforce reports or data export tools to extract Contact records with gender values.

Check for any discrepancies or invalid entries.

Correct the invalid values by updating the records with appropriate values.

Review Field Mappings and Settings:

Ensure that any field mappings related to the gender field in Relationship settings or Reciprocal Relationships are correctly configured.

By ensuring the gender field values are valid, the admin can resolve the error and ensure smooth execution of the after-update trigger.

References:

Salesforce Help: Managing Custom Fields

Nonprofit Success Pack (NPSP) Documentation: Relationship and Gender Field Settings

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

Delete Access to Contacts:

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

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

Unique External ID:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Merge Contact Permissions Guide

When migrating a large volume of contacts, accounts, and address records into NPSP, the following considerations are important:

Managing Multiple Addresses:

NPSP allows for multiple addresses per contact or account, which can introduce additional complexity in managing and maintaining these records.

It is essential to have a clear strategy for handling primary, mailing, and other types of addresses to ensure data consistency and accuracy.

Data Storage Consumption:

Each address record consumes additional data storage in Salesforce.

Nonprofits should be aware of their data storage limits and plan accordingly to avoid running out of storage space.

Consider archiving old or inactive address records to manage storage usage efficiently.

These considerations help ensure a smooth data migration process and ongoing data management within NPSP.

References:

Salesforce Help: Managing Addresses in NPSP

Nonprofit Success Pack (NPSP) Documentation: Data Management and Storage

To ensure that a subset of users can fully access the government-issued personal identification numbers stored in encrypted fields on Contact records, you must enable the "View Encrypted Data" permission in a permission set. This permission allows users to see the actual encrypted data instead of a masked value.

Steps to Enable:

Create or Edit a Permission Set:

Navigate to Setup -> Permission Sets.

Create a new permission set or edit an existing one.

Enable View Encrypted Data:

In the permission set, go to System Permissions.

Enable the "View Encrypted Data" permission.

Assign Permission Set:

Assign the permission set to the appropriate users who need to access the encrypted data.

References:

Salesforce Help: Encrypt Custom Fields

Salesforce Trailhead: Data Security and Encryption

To ensure that case managers gather all required information when qualifying new beneficiaries, Salesforce Flow is the most effective automation tool:

Create a Flow:

In Salesforce Setup, navigate to "Flow Builder" and create a new Flow.

Choose a "Screen Flow" to guide users through the data entry process.

Design the Flow:

Add screens to the Flow that contain fields for all the required information. Use validation rules to ensure required fields are completed before proceeding to the next screen.

Use logic elements like decisions and assignments to handle conditional data collection based on previous inputs.

Deploy the Flow:

Embed the Flow on the Lightning Record Page for case managers to use when qualifying new beneficiaries.

Ensure the Flow is easily accessible and part of the standard workflow for case managers.

Training and Support:

Provide training for case managers on how to use the Flow.

Monitor usage and collect feedback to make any necessary adjustments.

Salesforce Flow provides a guided, interactive way to ensure all required information is collected consistently.

References:

Salesforce Documentation: Flow Builder Guide

Trailhead Module: Automate Your Business Processes with Lightning Flow

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 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 troubleshoot incorrect values in the NPSP calculated donation summary fields on Contact and Account records, the consultant should review the following:

Customizable Rollups:

Verify the settings and configuration of Customizable Rollups in NPSP. Incorrect configurations or mappings can lead to inaccurate summary values.

Ensure that the rollups are set up correctly to calculate totals based on the desired criteria.

Opportunity Stages:

Check the Opportunity stages to ensure they are correctly defined and assigned. Only certain stages (e.g., "Closed Won") should be included in donation summaries.

Misconfigured or incorrect stages can result in inaccurate summary calculations.

NPSP Health Check:

Run the NPSP Health Check to identify any potential configuration issues or data integrity problems.

The Health Check provides insights and recommendations to address common issues within NPSP.

References:

Salesforce Nonprofit Success Pack Documentation on Customizable Rollups

Salesforce Opportunity Stages Configuration Guide

NPSP Health Check Documentation

Before using Advanced Mapping in NPSP, it is necessary to enable and deploy My Domain. My Domain is a prerequisite for using several Salesforce features, including Advanced Mapping, as it allows you to customize your Salesforce org's URL, and it enhances security by creating a unique subdomain for your Salesforce org.

Steps to Enable My Domain:

Navigate to Setup:

Go to Setup -> My Domain.

Register My Domain:

Enter your preferred domain name and check its availability.

Register the domain and wait for the confirmation email.

Deploy My Domain:

After registration, deploy the domain to users and ensure it is active.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Help: My Domain

When a donor wants to split their gift between two scholarship funds, the consultant should recommend using GAU Allocations:

GAU Allocations:

General Accounting Unit (GAU) Allocations in NPSP (Nonprofit Success Pack) allow for the distribution of a single donation across multiple funds or purposes. This feature supports detailed tracking and reporting on how donations are allocated.

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

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.

/understand-the-npsp-data-model

For nonprofits needing to track key information related to grants, such as deadline dates, activity completion dates, and descriptions, Deliverables within Salesforce are the recommended feature. Deliverables allow nonprofits to create and manage detailed records of grant-related activities, set deadlines, and monitor progress directly on the Opportunity object.

Steps:

Enable Deliverables in Salesforce.

Create Deliverable records to track grant-related tasks, deadlines, and activities.

Configure Deliverables to display the next deadline date on the Opportunity.

Use reports and dashboards to monitor the status and progress of grant-related activities.

References:

CertGod Nonprofit Cloud Consultant Guide: Recommends using Deliverables for tracking detailed grant information and deadlines​​.

Salesforce Documentation on Deliverables: Provides setup instructions and usage guidelines.

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

Payments = Opportunities with Payments:

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

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

Applications = Deliverables:

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

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

Reporting Deadlines = Deliverables:

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

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

Actions = Activities:

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

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

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

References:

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

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

Top of Form

Bottom of Form

salesforce.com/products/marketing-cloud/faq/

For managing multiple communication channels, creating personalized journeys, automating message triggers, and linking communications to donations, the combination of NPSP and Marketing Cloud is the best solution. Marketing Cloud offers robust capabilities for email marketing, social media, mobile messaging, and more, integrated with Salesforce for a unified view of constituent interactions.

Steps:

Implement NPSP to manage donor and constituent information within Salesforce.

Set up Marketing Cloud and connect it to Salesforce using the Marketing Cloud Connect integration.

Configure Marketing Cloud to create personalized journeys for constituents based on their interactions and engagement history.

Use Marketing Cloud's automation features to trigger messages and manage multi-channel communications.

Link communication activities in Marketing Cloud to donation records in NPSP to track the impact of marketing efforts on fundraising outcomes.

References:

CertGod Nonprofit Cloud Consultant Guide: Recommends using Marketing Cloud for advanced marketing automation and multi-channel communications​​.

Salesforce Documentation on Marketing Cloud and NPSP Integration: Details on setting up and leveraging Marketing Cloud for nonprofits.

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

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

Enhanced Recurring Donations in NPSP allows nonprofits to manage recurring donations more flexibly, including making one-time adjustments to the donation amounts. This feature provides a robust way to handle scenarios where donors want to change their regular giving amounts temporarily.

Steps to Implement:

Enable Enhanced Recurring Donations:

Navigate to NPSP Settings -> Donations -> Recurring Donations.

Enable Enhanced Recurring Donations.

Set Up Recurring Donations:

Create a Recurring Donation record for the donor, specifying the regular donation amount and schedule.

Use the Enhanced Recurring Donations feature to adjust the schedule and amounts as needed.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Manage Recurring Donations in NPSP