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

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

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

Salesforce.org recommends using the Affiliations object to address the complexity of tracking donors who have relationships with many different Accounts. The Affiliations object is designed to manage and represent the various roles and relationships that a Contact can have with multiple Accounts. This is especially useful for non-profit organizations that need to track complex and multifaceted relationships between donors and organizations.

Understanding Affiliations in NPSP:

Affiliations are used to track the various roles a Contact has with different Accounts.

Each Affiliation record links a Contact to an Account, along with a Role and a Status.

This allows organizations to manage and report on the different ways Contacts are connected to multiple Accounts.

Setting Up Affiliations:

In NPSP (Nonprofit Success Pack), navigate to the App Launcher and select "NPSP Settings."

Under the Affiliations section, you can configure different settings related to Affiliations, such as default role values and Affiliation mappings.

Creating and Managing Affiliations:

When creating a new Contact or updating an existing one, you can add Affiliation records to link the Contact to various Accounts.

Navigate to the Contact's detail page, and in the Affiliations related list, click "New Affiliation."

Fill out the required fields such as Account, Role, and Status, then save the record.

Using Affiliations for Reporting:

Affiliations can be included in reports to analyze the relationships Contacts have with multiple Accounts.

For example, you can create a report to show all Contacts and their respective roles in various organizations, which helps in understanding the network and influence of donors.

Benefits of Using Affiliations:

It provides a structured way to manage complex donor relationships.

Enhances reporting capabilities by allowing detailed analysis of donor connections.

Improves data accuracy by avoiding duplicate records and ensuring each Contact's relationships are properly tracked.

References:

CertGod Nonprofit Cloud Consultant study guide: "Which Salesforce object does Saleforce.org recommend using to address this complexity?" ​​

Salesforce Nonprofit Success Pack documentation on Affiliations: "Manage and represent the various roles and relationships that a Contact can have with multiple Accounts."

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

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

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

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

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

Incompatibility with NPSP Features:

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

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

Limited Support:

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

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

Best Practices for Nonprofits:

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

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

Data Model Alignment:

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

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

References:

Salesforce NPSP Documentation: Account Models

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

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

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

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

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

References:

Salesforce Data Loader Documentation

Salesforce Trailhead: Data Management Tools

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

If the Check/Reference Number field is not visible in the report builder, the consultant should check if there is a custom field named "Check/Reference Number" on the Payments object. Here’s how to proceed:

Verify Custom Fields on Payments Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Look for a custom field named "Check/Reference Number".

Ensure Field is Included in Report Type:

Go to the Report Builder.

Verify that the report type being used includes the Payments object.

If the report type does not include Payments, create or use a report type that does.

Add Field to Report Layout:

In the Report Builder, ensure the "Check/Reference Number" field is added to the report layout.

Drag and drop the field into the columns of your report.

By ensuring that the custom field is present on the Payments object and included in the report type, the development associate can successfully add the Check/Reference Number to their report.

References:

Salesforce Documentation: Custom Fields

Salesforce Trailhead: Create Reports with the Report Builder

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

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

Creating a Campaign hierarchy is the most effective way to track funding for projects and monitor year-over-year goals in Salesforce. Campaign hierarchies allow for organizing campaigns in a structured manner, making it easy to roll up data and track progress across different levels. Here’s how to set this up:

Create Parent Campaigns for Years:

For each year, create a parent campaign. For example, "2023 Projects" and "2024 Projects".

Create Sub-Campaigns for Projects:

Under each yearly parent campaign, create sub-campaigns for each project. For instance, "2023 Projects" can have sub-campaigns like "Project A", "Project B", etc.

Link Sub-Campaigns to Parent Campaigns:

Use the Parent Campaign lookup field to link each project campaign to its respective year campaign. This establishes the hierarchy.

Track Goals and Progress:

Use Campaign fields to set goals and track actual amounts. Fields like "Campaign Member Status", "Amount Raised", and custom fields can be used to track the funding and progress.

Use roll-up summary fields to aggregate data from sub-campaigns to parent campaigns.

Reporting and Dashboards:

Create reports and dashboards to monitor the progress of each project and year-over-year comparisons. Use the Campaign Hierarchy feature in reports to show aggregated data.

By setting up a Campaign hierarchy, the foundation can easily track the funding, manage goals, and compare progress year-over-year.

References:

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

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

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

Prepare the Spreadsheet:

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

Access NPSP Data Importer:

Go to the App Launcher.

Search for and open "NPSP Data Importer".

Configure the Data Importer:

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

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

Upload the Spreadsheet:

Upload the prepared spreadsheet to the NPSP Data Importer.

Review and confirm the data mapping.

Run the Import:

Run the import process.

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

Verify and Clean Up:

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

Verify that all data has been imported correctly.

References:

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

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

When an international nonprofit organization adds a translated relationship picklist value, and the reciprocal relationship record is not displaying correctly, it is typically due to the system administrator not adding the reciprocal relationship value in the NPSP Settings tab.

Steps:

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

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

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

Add Reciprocal Relationship:

Click "Reciprocal Method Settings".

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

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

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

References:

CertGod Nonprofit Cloud Consultant Guide

If the NPSP 00 - Error Processing job is accidentally deleted, you can recreate it using the NPSP settings. Here’s how:

Access NPSP Settings:

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

Go to Bulk Data Processes:

In the NPSP Settings, find the "Bulk Data Processes" section.

Batch Process Settings:

Click on "Batch Process Settings".

Here, you can find options to recreate various batch jobs, including the NPSP 00 - Error Processing job.

Recreate the Job:

Follow the prompts to recreate the NPSP 00 - Error Processing job.

Save your settings.

By using the NPSP Settings to recreate the job, you ensure that the necessary error processing is back in place without needing to manually configure or contact support.

References:

Salesforce NPSP Documentation: Batch Process Settings

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

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

Navigate to the NPSP SYBUNT Report:

Go to the Reports tab.

Find and open the NPSP SYBUNT report template.

Customize the Date Range:

Click on the “Filters” pane.

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

Modify Report Criteria:

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

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

Run the Report:

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

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

References:

"Using NPSP Reports" from Salesforce Help: NPSP Reports

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

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

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

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

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

A Salesforce-recommended governance structure for nonprofit organizations ensures the implementation runs smoothly and effectively. It typically includes the following elements:

Release Management: This ensures that changes are systematically planned, tested, and deployed. It involves managing how new features and updates are rolled out to avoid disruption and ensure smooth transitions.

Rules of Engagement: These define how different stakeholders will interact with the system and with each other. It includes protocols and guidelines for communication, decision-making, and responsibilities.

Center of Excellence (CoE): This is a dedicated team or a hub of experts that provides leadership, best practices, research, support, and training. A CoE helps ensure that the organization is leveraging Salesforce effectively and efficiently.

References:

Salesforce Nonprofit Cloud Implementation Guide

Salesforce Trailhead: Governance Framework

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

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

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

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Customizable Rollups in NPSP

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

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

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

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

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 a nonprofit organization creates a custom Opportunity name for all organization donations, the consultant should discuss the following considerations:

Using the "Refresh Name" Action (B):

The organization should use the "Refresh Name" action to change existing Opportunities to the new naming convention. This action ensures that the custom naming convention is applied correctly.

Navigate to the Opportunity record.

Click on the "Refresh Name" button to update the Opportunity name according to the new naming convention.

Using the "Refresh All Opportunity Names" Button in Bulk Data Processes (C):

For bulk updates, the organization should use the "Refresh All Opportunity Names" button available in Bulk Data Processes.

Go to NPSP Settings.

Under Bulk Data Processes, find the "Refresh All Opportunity Names" button.

Click on it to update all existing Opportunities to the new naming convention in bulk.

These methods ensure that the custom naming convention is applied consistently across all existing Opportunity records, maintaining data integrity and consistency within the Salesforce org​​.

When 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 ensure that the membership rollups in NPSP work properly, the following settings need to be configured:

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

Go to NPSP Settings.

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

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

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

Navigate to Setup -> Object Manager -> Opportunity.

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

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

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

References:

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

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

When setting up Volunteers for Salesforce in an international context, it's important to ensure that volunteer jobs and shifts reflect the local time zones accurately. Here’s how to configure this:

Navigate to Volunteers for Salesforce Settings:

Go to Setup.

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

Configure Volunteer Jobs:

Create Volunteer Jobs for each country.

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

Adjust Volunteer Shift Times:

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

Update Website Information:

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

References:

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

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

For 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

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

Create a Public Group:

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

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

Steps to Create a Public Group:

Go to Setup.

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

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

Create Sharing Rules:

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

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

Steps to Create Sharing Rules:

Go to Setup.

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

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

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

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

References:

Salesforce Help: Creating Public Groups

Salesforce Help: Defining Sharing Rules

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

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​

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

Marketing Cloud Connect:

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

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

Email Studio Send Details:

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

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

References:

Salesforce Marketing Cloud Connect Documentation

Salesforce Email Studio Reporting Guide

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 manage incoming donations, provide a portal for constituents and staff members, and create a new web experience for constituents, a consultant should recommend:

NPSP with Experience Cloud:

Experience Cloud (formerly known as Community Cloud) enables nonprofits to build branded portals for their constituents and staff. It facilitates creating a self-service portal, donation management, and community engagement all in one platform.

Before converting from Legacy Recurring Donations to Enhanced Recurring Donations, nonprofits should consider several factors to ensure a smooth transition. Enhanced Recurring Donations offer improved functionality but may introduce compatibility issues with existing integrations. Additionally, once the switch is made, reverting to Legacy Recurring Donations is not supported, which means careful planning and testing are essential.

Steps:

Review all existing integrations to ensure compatibility with Enhanced Recurring Donations.

Conduct thorough testing in a sandbox environment to identify any potential issues.

Inform stakeholders that reverting to Legacy Recurring Donations is not supported once the switch is made.

Plan for a phased rollout and provide training to users on the new features and processes.

References:

CertGod Nonprofit Cloud Consultant Guide: Discusses considerations and steps for transitioning to Enhanced Recurring Donations​​.

Salesforce Nonprofit Success Pack (NPSP) Documentation: Details the features and limitations of Enhanced Recurring Donations.

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​

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

Grant visibility to the Gift Entry tab:

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

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

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

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

Grant access to BDI_BatchOverride and BDI_DataImport Visualforce pages:

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

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

References:

Salesforce documentation on Gift Entry permissions: Gift Entry Permissions

Before installing the Volunteers for Salesforce package, a consultant should:

Check that the nonprofit has the most recent NPSP release:

Ensure that the organization is running the latest version of the Nonprofit Success Pack (NPSP). This is crucial because newer releases might contain important updates and fixes that can impact the installation and functionality of Volunteers for Salesforce.

https://powerofus.force.com/s/article/NPSP-Configure-Data-Importer-Options

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

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.

When implementing Salesforce Shield Platform Encryption with NPSP, there are several key considerations:

Role Name Field on Partial Soft Credit Object:

If the Role Name field on the NPSP Partial Soft Credit object is encrypted, the nightly Soft Credit rollups will fail. This is because the rollup process relies on accessing this field, and encryption can interfere with its functionality.

MergeContacts List Button:

The NPSP MergeContacts list button on Contact list views will fail if the Contact Name is encrypted. The merging process requires access to the Contact Name to identify and merge records accurately, which encryption can prevent.

Custom Unique Id Matching:

NPSP Data Import cannot perform Custom Unique Id matching on Accounts and Contacts if the field used for matching is encrypted. This limitation arises because the encryption prevents the import process from accurately comparing and matching the encrypted values.

These considerations highlight the impact of encryption on certain NPSP functionalities, and it is important to plan accordingly when implementing Shield Platform Encryption.

References:

Salesforce Shield Platform Encryption Documentation

Nonprofit Success Pack (NPSP) Documentation on Data Import and Soft Credits

To ensure that a subset of Service Delivery records are visible to selected staff while maintaining private sharing settings, you should use criteria-based sharing rules:

Navigate to Sharing Settings:

Go to Setup in Salesforce.

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

Create a Criteria-Based Sharing Rule:

In the Sharing Settings, locate the object for which you want to create the sharing rule (e.g., Service Deliveries).

Create a new sharing rule and select "Based on Criteria" as the rule type.

Define the criteria that records must meet to be shared (e.g., specific fields or values that identify the subset of records).

Specify the users or roles that should have access to these records and define the level of access (Read/Write).

Save and Apply the Rule:

Save the sharing rule and ensure it is activated.

Verify that the selected staff have the appropriate access to the records as defined by the rule.

By using criteria-based sharing rules, you can selectively grant access to specific records without compromising the overall privacy settings of the organization.

References:

Salesforce Help: Setting Up Sharing Rules

Nonprofit Success Pack (NPSP) Documentation on Sharing and Security Settings

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.

To exclude gala attendees from the report that identifies individual donors who have yet to make a gift toward the Annual Fund Campaign this year, a cross filter should be added to the report. Cross filters allow you to filter records based on related objects, such as excluding contacts who are campaign members of the gala event.

Steps:

Go to Reports and create a new report or edit an existing report on donors.

Add a cross filter to the report by clicking on the "Filters" pane and selecting "Add Cross Filter."

Set the cross filter to exclude Contacts who are Campaign Members of the specific gala campaign.

Save and run the report to ensure it correctly excludes gala attendees.

References:

Nonprofit Cloud Reporting Guide: Explains how to use cross filters to refine report data based on related objects​​.

Salesforce Help: Detailed steps on creating and using cross filters in reports.

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

Create Program Engagement Records:

Navigate to the "Program Engagements" tab.

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

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

Select the Program:

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

Specify the Services:

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

References:

Salesforce Nonprofit Cloud Consultant Study Guide

Salesforce Program Management Module Documentation

Salesforce NPSP (Nonprofit Success Pack) Resources

For tracking funds received and allocated for grants, the Outbound Funds Module is the best solution. Here’s how to configure it:

Install the Outbound Funds Module:

Go to the AppExchange and search for the "Outbound Funds Module."

Click "Get It Now" and follow the installation instructions to add the module to your Salesforce org.

Configure Funding Programs and Grants:

Navigate to the "Funding Programs" tab to set up different programs that receive funds.

Create "Funding Requests" for organizations applying for grants and track the status and details of each request.

Track Funds:

Use "Funding Allocations" to track how funds are distributed to various grants. Each allocation record should specify the amount, date, and purpose of the funds.

Reporting:

Use standard and custom reports to track the inflow and outflow of funds, ensuring transparency and accountability in grant management.

References:

Salesforce Outbound Funds Module Documentation

Salesforce Nonprofit Success Pack (NPSP) Resources

Salesforce Trailhead: Manage Programs and Funding

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.

The PMM has two main objects — Programs and Services — and several objects that connect those objects together with contacts and household accounts

In the Program Management Module (PMM), the objects that are directly connected to objects in Nonprofit Cloud Case Management are:

Case:

Cases in Nonprofit Cloud Case Management are used to track client issues and support needs.

They can be directly related to program participants and services provided, allowing for comprehensive case management.

Service Delivery:

Service Deliveries represent the specific services provided to clients, such as counseling sessions, classes, or other forms of assistance.

They are essential for tracking the outcomes and effectiveness of the nonprofit's programs and are directly connected to case management processes.

References:

Salesforce Nonprofit Cloud Case Management Guide

Salesforce Program Management Module (PMM) Documentation

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

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

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

Custom Report Type:

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

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

Include Relevant Fields:

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

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

Filters and Sorting:

Apply necessary filters to ensure only relevant records are included.

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

References:

Salesforce Help: Custom Report Types

Nonprofit Success Pack (NPSP) Documentation: Managing Relationships

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

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

Steps to Verify:

Check Merge Settings:

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

Review Audit Logs:

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

Restore if Necessary:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Merge Duplicate Records in Nonprofit Success Pack

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

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.

When a nonprofit is making a substantial technology shift that will affect multiple teams and departments, the initial steps should include forming a powerful guiding coalition and establishing a sense of urgency. These steps are critical for successful change management.

Form a powerful guiding coalition:

This involves assembling a group with enough power and influence to lead the change effort and encourage collaboration across departments.

Establish a sense of urgency:

Creating a sense of urgency helps build the momentum needed for change by highlighting the importance and benefits of the technology shift to the entire organization.

References:

Kotter's 8-Step Change Model

Salesforce Nonprofit Cloud Consultant Study Guide

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

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

Salesforce Data Mask Overview:

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

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

Implementation Steps:

Install Salesforce Data Mask from the Salesforce AppExchange.

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

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

Benefits of Using Data Mask:

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

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

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

References:

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

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

Check the CSV File:

Open the CSV file that was uploaded.

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

Ensure Completeness:

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

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

Re-import Data:

Correct any incomplete or missing data in the CSV file.

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

Verify Field Mappings:

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

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

References:

Salesforce Data Import Wizard Guide: Data Import Wizard.

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 record the donation and credit it correctly in Salesforce Nonprofit Success Pack (NPSP):

Create a Relationship:

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

Go to the individual’s contact record.

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

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

Create the Donation Opportunity:

Go to the individual's contact record.

Click on the "New Opportunity" button.

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

Save the opportunity.

Add a Soft Credit Contact Role:

After saving the opportunity, go to the Opportunity record.

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

Click "New" to add a new contact role.

Select the board member’s contact.

Choose "Soft Credit" as the role type.

Save the contact role.

Verify Relationship and Soft Credit:

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

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

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

References:

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

CertGod Nonprofit Cloud Consultant guide​

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

Middleware Tools:

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

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

Integration Process:

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

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

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

Advantages:

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

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

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

Implementation Steps:

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

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

Map the data fields and set up the necessary transformations.

Test the integration thoroughly before going live.

References:

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

To 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

To ensure the campaign for monthly project updates to donors who have given 10 or more times stays current, the consultant should:

Create a Contact Report:

Create a report on the Contact object and include a filter to display only those contacts whose total number of gifts meets the criteria (10 or more).

This filter ensures that only the relevant donors are included in the report.

Run the Report Monthly:

Schedule or manually run the report each month to get the updated list of donors.

Use the "Add to Campaign" button to add the contacts from the report to the newsletter campaign, ensuring the campaign list stays current with donors who meet the criteria.

References:

Salesforce Reporting Guide

Salesforce Campaign Management Guide

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

Populate the Primary Campaign Source Field:

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

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

Enable Automatic Campaign Member Management:

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

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

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

Steps to Implement:

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

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

Benefits:

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

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

References:

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

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

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

Steps:

Go to Setup > Custom Metadata Types.

Select "Trigger Handlers."

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

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

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

References:

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

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

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

Enable Einstein for Nonprofits:

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

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

Configure Prediction Models:

Use Einstein Prediction Builder to create a custom prediction model.

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

Train and Deploy the Model:

Train the prediction model using historical data.

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

Utilize Predictions in Fundraising Strategies:

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

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

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

References:

Salesforce Einstein for Nonprofits: Einstein for Nonprofits.

Salesforce Einstein Prediction Builder Guide: Prediction Builder.

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 track a check that includes donations from several donors for a specific program, the consultant should configure GAU Allocations and Partial Soft Credits in NPSP. Here’s why:

GAU Allocations:

General Accounting Unit (GAU) Allocations are used to track how donations are allocated across different programs or funds.

This feature allows the nonprofit to specify which portion of the check is designated for the specific program, providing clear tracking and reporting.

Partial Soft Credits:

Partial Soft Credits can be used to attribute portions of a single donation to multiple donors.

This feature allows the nonprofit to recognize each donor for their contribution while keeping the accounting of the total donation intact.

References:

Salesforce NPSP Documentation on GAU Allocations

Salesforce NPSP Documentation on Soft Credits