Salesforce Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102 Exam Practice Test

When setting up the process for importing lists of Contacts into Salesforce Campaigns using the NPSP Data Import tool, it is essential to consider how Campaign Members are created and matched.

Key Considerations:

Automatic Campaign Member Creation (A):

The NPSP Data Import tool will automatically create Campaign Member records for the imported Contacts with the default Member Status. This helps streamline the process of adding members to campaigns.

Exact Name Matching (D):

Existing Campaigns in Salesforce are matched by exact Name. This means that the names in the CSV files must match the names of the Campaigns in Salesforce exactly for the import process to associate Contacts with the correct Campaigns.

Steps to Set Up:

Prepare CSV Files:

Ensure that the Campaign names in the CSV files exactly match the names of the Campaigns in Salesforce.

Include all necessary fields to map Contacts to Campaign Members.

Configure NPSP Data Import:

Navigate to NPSP Settings -> Data Import.

Ensure the settings align with the import requirements, including handling duplicates and respecting duplicate matching rules if enabled.

Perform Dry Run:

Use the NPSP Data Import Dry Run feature to validate the import configuration and ensure that the Campaign Member Status and other settings are correctly applied.

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

Explore AppExchange:

Visit the Salesforce AppExchange.

Search for wealth scoring or donor prospecting applications.

Evaluate Apps:

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

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

Select an App:

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

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

Install and Configure the App:

Install the selected app into the Salesforce org.

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

Map Wealth Scores to Salesforce Fields:

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

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

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

Salesforce AppExchange: WealthEngine

Salesforce Documentation: Install Apps from AppExchange

When integrating an external email platform with Salesforce, it's important to consider storage implications and retention policies. Here are the steps to take into account these considerations:

Evaluate Storage Requirements:

Campaign Member records are used to track email interactions within Salesforce. These records typically consume less storage compared to creating a custom object for the same purpose.

Custom objects can lead to higher storage usage, especially if tracking detailed interaction data.

Retention Policies:

Understand the email platform's data retention policies. Some platforms allow you to specify how long subscriber activity data (such as opens, clicks, and unsubscribes) should be retained.

Configure the retention settings to align with your organization's data retention policies and compliance requirements.

Integration Setup:

Set up the integration to ensure that Campaign Members are created or updated with each email interaction.

Use the external email platform's API to push data into Salesforce, ensuring that Campaign Members are updated in real-time or through scheduled syncs.

Monitor and Optimize:

Regularly monitor storage usage in Salesforce and optimize data retention settings to balance between having sufficient historical data and managing storage costs.

Salesforce Storage Usage Best Practices: Detailed best practices for managing storage in Salesforce. Salesforce Help.

Email Platform Integration Guides: Specific guides for integrating popular email platforms with Salesforce (e.g., Mailchimp, Pardot).

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.

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

Organize Advocacy Messages into Campaigns:

Create a Campaign in Salesforce for each advocacy initiative.

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

Use an Online Advocacy Platform from the AppExchange:

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

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

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

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

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

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

Steps:

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

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

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

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

To configure the view of Contact records to avoid visually identifying a subset of clients, the consultant should set the component visibility for the Client Photo Component:

Navigate to Lightning App Builder:

In Salesforce Setup, go to "Lightning App Builder."

Select the Lightning Record Page for Contacts that you wish to modify.

Configure Component Visibility:

Locate the Client Photo Component on the page.

Click on the component to open its properties.

Set Component Visibility Rules:

In the properties panel, set visibility rules for the Client Photo Component.

Define criteria to control when the component is visible. For instance, you can use field values or user profiles to determine visibility.

Save and activate the changes.

Test and Deploy:

Test the Lightning Record Page to ensure the visibility rules work as expected.

Deploy the updated page to users.

By setting the component visibility for the Client Photo Component, you can ensure that the subset of clients is not visually identified, meeting the nonprofit's requirements.

check the entity relationship diagram

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

Steps:

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

Compare the features of PMM and Case Management.

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

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

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.

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

Cost Savings:

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

It also ensures efficient resource utilization and minimizes waste.

Security:

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

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

Delivery Speed:

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

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

Steps to Emphasize Governance:

Establish a governance committee that includes key stakeholders.

Define clear governance policies and procedures.

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

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

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

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

Steps to Set Up Engagement Plans:

Navigate to the "Engagement Plans" tab in NPSP.

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

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

Assign the Engagement Plan to the appropriate client records.

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

Steps to Set Up Levels:

Navigate to NPSP Settings > Levels.

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

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

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

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.

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.

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

Enable My Domain:

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

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

Ensure Appropriate Licenses Are Provisioned:

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

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

Salesforce Nonprofit Cloud Case Management Installation Guide

Salesforce My Domain Documentation

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.

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

Key Considerations:

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

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

Steps to Resolve:

Review Field Types:

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

Check Documentation:

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

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.

"Managing Affiliations in NPSP" from Salesforce Help: Affiliations

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

When using the NPSP Data Importer to upload data that contains payments on existing opportunities, and matching donations to existing records, the following updates may occur:

A Payment Will Be Added to the Opportunity:

When a gift is successfully matched to an existing Opportunity, a Payment record is created and associated with the Opportunity.

This reflects the new donation and updates the financial records accordingly.

The Opportunity Amount Will Include the New Payment Amount:

The total amount on the Opportunity will be updated to reflect the sum of the original amount and the new payment amount.

This ensures that the Opportunity accurately represents the total donations received.

These updates help maintain accurate and up-to-date financial records within Salesforce, reflecting all contributions accurately.

Salesforce NPSP Documentation: NPSP Data Importer

Salesforce Trailhead: Manage Donations with NPSP

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.

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

Batch Size:

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

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

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

Salesforce Batch Apex Documentation

Salesforce Governor Limits Guide

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

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

Access Setup:

Navigate to Setup in Salesforce.

Enable Guest User Permissions:

Go to Sites and Domains > Sites.

Click on the site label for your volunteer portal.

Click on Public Access Settings.

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

Grant Guest Users Update Access:

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

Test the Configuration:

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

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

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

Salesforce Help Documentation: Sites and Public Access Settings.

For a nonprofit organization needing an email marketing tool to measure email engagement and evaluate prospective supporters:

Pardot Grading: This measures how well a prospect fits the ideal customer profile based on criteria such as job title, industry, and location.

Pardot Scoring: This tracks a prospect’s engagement with marketing materials, assigning points based on interactions such as email opens, clicks, and form submissions.

Combining Pardot Grading and Scoring provides a comprehensive view of both the quality and engagement level of prospective supporters.

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

Accounting Subledger:

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

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

Setting Up Accounting Subledger:

Install and configure the Accounting Subledger from the AppExchange.

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

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

Benefits:

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

Ensures data consistency and accuracy across systems.

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

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

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.

Salesforce NPSP Documentation: Batch Process Settings

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

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

Verify Sandbox Release:

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

Review Sandbox Preview Instructions:

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

Prepare Change Sets:

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

Monitor Release Window:

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

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.

Salesforce Einstein for Nonprofits: Einstein for Nonprofits.

Salesforce Einstein Prediction Builder Guide: Prediction Builder.

Both Marketing Cloud and Pardot offer the capability to segment data and functionality using business units. This is particularly useful for large nonprofits with multiple chapters operating under a single brand but needing customized roles, processes, and messaging.

Marketing Cloud:

Business Units: Allows organizations to separate data, user permissions, and content based on different parts of the organization, such as chapters or departments. Each business unit can have its own data and customizations, enabling localized marketing while maintaining centralized control.

Pardot:

Business Units: Pardot Business Units enable marketing teams to partition data and customize marketing efforts for different segments within the organization. This ensures that each chapter can tailor its marketing automation processes to its specific needs while maintaining brand consistency.

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.

Salesforce documentation on Gift Entry permissions: Gift Entry Permissions

For a nonprofit organization looking for a CRM with an integrated email marketing tool that includes built-in scoring and engagement tracking, the recommended solution is:

NPSP (Nonprofit Success Pack): This provides the CRM functionality to manage constituents.

Marketing Cloud: This offers advanced email marketing capabilities, including automation, scoring, and engagement tracking.

Marketing Cloud is designed to handle complex marketing needs and integrates seamlessly with NPSP to provide a comprehensive solution for nonprofits.

If the nightly NPSP batch jobs are taking significantly longer to complete, the system admin should consider the following factors:

A New Standard Roll-Up Summary Field Was Added to an Object:

Adding new roll-up summary fields can increase the processing time for batch jobs.

These fields require calculations that aggregate data, which can slow down batch processing, especially if they are based on high-volume objects.

A New Customizable Rollup Was Added in NPSP Settings:

Customizable rollups allow for complex aggregations and summaries across various objects.

Adding new rollups increases the processing workload for nightly batch jobs, leading to longer completion times.

Review and optimize the rollup settings to balance performance with data aggregation needs.

By considering these factors, the system admin can identify and address the root causes of increased batch job processing times.

Salesforce NPSP Documentation: Customizable Rollups

Salesforce Documentation: Roll-Up Summary Fields

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.

The Program Management Module (PMM) in Salesforce is designed to help nonprofits manage their programs and services, including tracking participation in courses and training. PMM provides the necessary tools and features to capture and report on the various activities and outcomes associated with the programs run by the nonprofit.

Key Features:

Service Delivery Tracking: PMM allows for detailed tracking of services provided, including courses and training sessions.

Customizable Program Management: Nonprofits can configure PMM to meet their specific needs for managing programs and tracking participant engagement.

Steps to Implement PMM:

Install PMM:

Go to the Salesforce AppExchange and install the Program Management Module.

Set Up Programs and Services:

Define programs and related services within PMM to reflect the courses and training offerings.

Track Participation:

Use the PMM features to log and manage participant data, track attendance, and monitor outcomes.

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.

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

Lightning Flow in Salesforce is a powerful declarative tool that allows users to automate business processes and create guided visual experiences. This tool is specifically designed for process automation and can help nonprofits streamline routine activities without requiring any coding knowledge. Here are the steps to use Lightning Flow for automating processes:

Access Lightning Flow Builder:

Navigate to Setup.

In the Quick Find box, type "Flows" and select "Flows" under Process Automation.

Create a New Flow:

Click "New Flow".

Choose the type of flow you want to create. For automating routine activities, "Screen Flow" or "Scheduled-Triggered Flow" might be appropriate.

Design the Flow:

Use the drag-and-drop interface to add elements like screens, decisions, assignments, and loops.

Configure each element to define the process logic.

Set Entry Conditions and Actions:

Define the trigger for the flow (e.g., record creation, updates, scheduled times).

Specify the actions to be taken (e.g., create/update records, send emails, call Apex classes).

Test the Flow:

Before activating the flow, use the Debug mode to test and ensure it works as expected.

Activate the Flow:

Once tested, activate the flow so it starts running based on the defined conditions.

"Get Started with Automation Tools" from Salesforce Help: Salesforce Automation

"Salesforce Flow for Nonprofits" from Salesforce.org: Salesforce.org Guide

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

Access Trailblazer Community:

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

Search for User Groups:

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

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

Join Relevant Groups:

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

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

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

For a large nonprofit that functions like a for-profit corporation and tracks funding exclusively from corporations, the Standard Account Model without NPSP is the most suitable choice. This model allows the nonprofit to manage Leads and track its Opportunity pipeline effectively, focusing on corporate accounts.

Benefits of the Standard Account Model:

Simplicity: The Standard Account Model is straightforward and designed for organizations that do not need the additional features provided by NPSP.

Corporate Focus: It is well-suited for managing corporate accounts and opportunities without the additional complexities of individual or household account models.

Steps to Implement:

Set Up Standard Account Model:

Use the default Salesforce setup for Accounts, Contacts, Leads, and Opportunities.

Customize as Needed:

Customize the standard objects and fields to align with the nonprofit’s specific requirements for tracking corporate funding.

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.

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

Steps:

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

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

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

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

When migrating a large volume of donation and payment data into an NPSP org, the consultant should discuss the following considerations with the nonprofit organization:

Data Storage Limits:

Salesforce has data storage limits based on the type and edition of the Salesforce instance.

It is important to calculate the volume of data being imported and ensure it does not exceed the available storage.

If necessary, consider purchasing additional data storage or archiving old records to free up space.

Data Skew:

Data skew occurs when a large number of child records are associated with a single parent record.

This can impact performance and cause issues with sharing rules and data visibility.

Plan the data import to distribute records evenly and avoid creating data skew, particularly with high-volume objects like Contacts and Accounts.

By addressing these considerations, the nonprofit can ensure a smooth and efficient data migration process while maintaining optimal system performance and compliance with Salesforce limits.

Salesforce Documentation: Data Storage Allocations

Salesforce NPSP Documentation: 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.

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

Set Up General Accounting Units (GAUs):

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

Create GAUs:

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

Provide names and descriptions that clearly identify each fund.

Link GAUs to Donations:

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

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

Run Reports on GAU Allocations:

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

Automate Allocations (Optional):

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

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

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Overview

To allow volunteers to log their own hours in Volunteers for Salesforce, the consultant should propose setting up the Volunteers Personal Site or adding a Log Volunteer Hours section on the nonprofit’s website.

Volunteers Personal Site:

This site allows volunteers to log in and manage their hours directly within Salesforce.

Steps to Set Up:

Navigate to Setup > Sites.

Create a new site and configure it to use the Volunteers for Salesforce functionality.

Add the Volunteers Personal Site tab and configure the permissions.

Direct volunteers to use this site to log their hours.

Log Volunteer Hours Section on Website:

Create a section on the nonprofit’s website where volunteers can log their hours.

Steps to Set Up:

Design a web form that captures the volunteer's job or shift and the hours worked.

Use Salesforce Web-to-Case or Web-to-Lead to capture this data and create records in Salesforce.

Direct volunteers to this section to submit their hours.

Both solutions provide a user-friendly way for volunteers to log their hours without requiring manual entry by staff.

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

Salesforce documentation on Permission Sets: Permission Sets

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

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.

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

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

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

Set Up Volunteer Recurrence Schedules:

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

Click "New Volunteer Recurrence Schedule."

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

Assign Volunteers to Recurrence Schedules:

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

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

Review and Manage:

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

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

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

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

Access the Power of Us Hub:

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

Log in using your Salesforce credentials.

Explore the Solution Exchange:

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

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

Connect with Similar Nonprofits:

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

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

Utilize Shared Resources:

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

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

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

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

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

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.

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

Create the Report:

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

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

Create a Custom Object:

Create a custom object to store the snapshot data.

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

Set Up the Reporting Snapshot:

Navigate to Setup.

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

Click "New Reporting Snapshot".

Name the snapshot and select the source report you created.

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

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

Schedule the Reporting Snapshot:

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

Save and activate the schedule.

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

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

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

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

Salesforce Reporting and Dashboards Guide

Salesforce Nonprofit Cloud Consultant Study Guide

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.

Salesforce Data Import Wizard Guide: Data Import Wizard.

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

Navigate to NPSP Settings:

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

Enable Lead Conversion Setting:

In NPSP Settings, expand the "Leads" section.

Find the "Lead Conversion" settings.

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

Save the settings.

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

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.

Salesforce Nonprofit Success Pack (NPSP) Documentation: Managing Acknowledgments

Salesforce Trailhead: Opportunities and Donations

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.

When migrating millions of Contact records and encountering the error "npsp.TDTM_Address: System.LimitException: Apex CPU time limit exceeded," you can take the following actions:

Disable Automation:

Go to NPSP Settings.

Navigate to "TDTM" (Table Driven Trigger Management).

Disable all automation triggers temporarily to ensure they do not interfere with the data load process.

Load Address Object Separately:

Split the data load into two parts: first load Contacts without address data, then load address data separately.

This reduces the complexity and processing required for each batch.

Disable ADDR_Addresses_TDTM Handler:

In NPSP Settings, go to "Trigger Configuration."

Locate the 'ADDR_Addresses_TDTM' handler.

Disable this specific handler to prevent it from executing during the data import process.

Reduce Batch Size:

When using Data Loader or any import tool, set the batch size to a significantly lower number (e.g., 100 or 200 records per batch).

This helps in managing CPU limits and ensures smoother processing.

By following these steps, you can mitigate the Apex CPU time limit issue and successfully import large volumes of data into NPSP.

To keep nonprofit staff up to date on the latest Salesforce platform features and best practices, the following resources are recommended:

Trailhead:

Trailhead is Salesforce’s free, interactive learning platform. It offers modules, projects, and trails that cover new features, best practices, and hands-on activities to help users learn and apply Salesforce skills.

Regularly check Trailhead for new content related to Salesforce updates and best practices.

Power of Us Hub:

The Power of Us Hub is an online community specifically for Salesforce.org users, including nonprofits. It provides a wealth of resources, discussions, and updates about Nonprofit Cloud and related Salesforce features.

Join the Power of Us Hub to stay informed about new features, best practices, and upcoming releases.

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.

Salesforce Nonprofit Success Pack Documentation on Affiliations

Salesforce NPSP Account and Contact Management Guide

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

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

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

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

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

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

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

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

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields

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.

To test new Nonprofit Cloud features coming out in the upcoming Salesforce release, follow these steps:

Identify the Sandbox Preview Period:

Salesforce announces preview periods before major releases. Check the Salesforce release calendar for the dates.

Refresh a Preview Instance Sandbox:

During the sandbox preview period, refresh one of your sandboxes. Ensure that you refresh an existing sandbox that is on a preview instance, or create a new sandbox if needed.

Verify the Sandbox Instance:

Make sure your sandbox is on a preview instance. Salesforce typically migrates sandboxes to preview instances for testing new features.

Test New Features:

Once the sandbox is refreshed, you can start testing the new Nonprofit Cloud features that will be included in the upcoming release.

Use the Release Notes and documentation provided by Salesforce to guide your testing.

This process allows you to evaluate new features before they are available in your production environment, ensuring a smooth transition and allowing time to address any potential issues.

Salesforce Sandbox Preview Guide: Sandbox Preview Instructions.

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.

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

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

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

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

Key Features:

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

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

Steps to Implement:

Set Up Programs:

Navigate to the Programs tab.

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

Track Engagements:

Navigate to the Program Engagements tab.

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

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

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

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

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

Regular Updates:

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

Automatic Updates:

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

Release Notes:

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

Testing and Sandbox Environments:

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

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

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

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.

"Case Hierarchies" from Salesforce Help: Case Hierarchies

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

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.

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.

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

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

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

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

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.

To protect data and secure login credentials for external systems, the consultant should recommend using Named Credentials. Named Credentials simplify the management of authentication for external systems by storing login credentials securely within Salesforce. This approach reduces the risk of exposed credentials and ensures that data remains protected even if an employee is terminated.

Steps:

Configure Named Credentials in Salesforce for each external system.

Store the authentication details securely within Salesforce.

Use Named Credentials in Apex code and integrations to access external systems.

Regularly review and update Named Credentials as needed to maintain security.

To track website visitors who download white papers, case studies, and impact reports, and then pursue them as constituents, using Pardot is the most effective solution. Here’s how to set it up:

Install and Configure Pardot:

Purchase and install Pardot if not already done.

Configure Pardot settings to align with your nonprofit’s tracking and lead management needs.

Add Pardot Tracking Code to Website:

Implement Pardot tracking code on your website to monitor visitor behavior, including downloads.

Create Pardot Forms and Landing Pages:

Use Pardot to create forms and landing pages for asset downloads.

Capture visitor information (name, email, etc.) before allowing downloads.

Set Up Automation Rules:

Create automation rules in Pardot to add visitors who download assets to specific lists.

Assign these visitors a score to prioritize follow-up actions.

Sync with Salesforce:

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

Use Salesforce campaigns to manage and track these new constituents.

Salesforce Pardot Documentation: Pardot Tracking Code

Salesforce Trailhead: Marketing Automation with Pardot

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.

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.

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

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

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.

For a nonprofit trade association that sells research papers, certifications, and other products online to its existing members who are primarily universities and companies, Salesforce B2B Commerce is the most suitable solution:

Salesforce B2B Commerce:

Salesforce B2B Commerce is designed for business-to-business transactions, making it ideal for organizations that sell products and services to other businesses, such as universities and companies.

It provides features for managing complex pricing, bulk orders, and accounts, which are essential for a trade association dealing with institutional members.

Features and Benefits:

B2B Commerce offers personalized buying experiences, self-service portals for customers, and streamlined order management processes.

It integrates seamlessly with Salesforce CRM, allowing the nonprofit to manage member relationships, sales, and order histories within a single platform.

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.

Salesforce Marketing Cloud Connect Documentation

Salesforce Email Studio Reporting Guide

To allow prospective volunteers to fill out their volunteer application online:

Set up the Volunteers for Salesforce Volunteer Signup Form: This form can be embedded on the nonprofit's website, allowing prospective volunteers to submit their information directly into Salesforce.

This approach leverages the existing Volunteers for Salesforce functionality, making it easy to capture and manage volunteer applications.

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.

Salesforce Nonprofit Cloud Case Management Guide

Salesforce Program Management Module (PMM) Documentation

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

Digital Engagement:

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

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