Nonprofit-Cloud-Consultant Questions and Answers

To run an enrollment report for education classes in Salesforce using the Program Management Module (PMM), the "Program Engagement" object is the most appropriate. Here are the steps to create such a report:

Understand Program Engagements:

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

Create a Custom Report Type:

Navigate to Setup > Report Types.

Click "New Custom Report Type."

Select "Program Engagement" as the primary object.

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

Build the Enrollment Report:

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

Select the custom report type you just created.

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

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

Customize and Save the Report:

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

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

Save and run the report to view the enrollment data.

References:

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

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

Add the Related List - Single Lightning Component:

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

Component Visibility Filter:

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

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

References:

Salesforce Lightning App Builder Documentation

Salesforce Component Visibility Filters Guide

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

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

Navigate to the Contact Record:

Go to the Contacts tab in Salesforce.

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

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Additional Actions:

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

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

Implications of Marking a Contact as Deceased:

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

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

References:

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

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.

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.

References:

Trailhead: trailhead.salesforce.com

Power of Us Hub: powerofus.force.com

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

Create a Public Group:

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

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

Steps to Create a Public Group:

Go to Setup.

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

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

Create Sharing Rules:

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

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

Steps to Create Sharing Rules:

Go to Setup.

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

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

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

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

References:

Salesforce Help: Creating Public Groups

Salesforce Help: Defining Sharing Rules

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

References:

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

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.

References:

Salesforce Documentation: Lightning App Builder

Trailhead Module: Build and Customize Lightning Experience Pages

To localize the US-focused labels of some NPSP fields for a UK-based nonprofit, such as replacing "Organization" with "Organisation," the consultant should activate English (UK) in Language Settings. Here’s why:

Activate English (UK):

Salesforce supports multiple languages and localizations, including English (UK), which provides localized labels for standard fields and objects.

By activating English (UK), the system will automatically use British English conventions, replacing US-centric terms with UK equivalents.

This is a straightforward and efficient method to localize field labels without the need for custom development or manual label changes.

References:

Salesforce Language Settings Documentation

Salesforce Localization and Translation Guide

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

Enable My Domain:

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

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

Ensure Appropriate Licenses Are Provisioned:

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

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

References:

Salesforce Nonprofit Cloud Case Management Installation Guide

Salesforce My Domain Documentation

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

Pardot for Email Automation:

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

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

Setting Up Pardot Automation:

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

Design and create different email templates for each segment.

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

Tracking and Reporting:

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

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

References:

Salesforce Pardot Documentation

Trailhead: Automate Marketing to Businesses with Pardot

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

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

Steps to Enable:

Enable Customizable Rollups:

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

Enable the Customizable Rollups feature.

Configure Rollups:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Configure Customizable Rollups in NPSP

To retain the legacy system's 150 donation appeal source codes as historical data in NPSP, you should follow these steps:

Create Campaigns for Each Legacy Source Code:

Navigate to the Campaigns tab in Salesforce.

Create a new Campaign for each of the 150 legacy source codes.

Name the Campaigns according to the source codes for easy identification.

Prepare Your Import Data:

Ensure that your import data includes a column for Campaigns, where you can map each donation to the corresponding legacy source code Campaign.

Import Contacts and Opportunities:

Use the Data Import Wizard or Data Loader to import your Contacts and Opportunities.

During the import process, map the source code field in your data to the appropriate Campaign in Salesforce.

Relate Contacts and Opportunities to Campaigns:

Ensure that each Contact and Opportunity record is related to the correct Campaign representing the legacy source code.

By organizing your legacy source codes into Campaigns and mapping your import data accordingly, you can effectively retain and manage historical donation appeal source codes in NPSP.

References:

Nonprofit Success Pack (NPSP) Data Import documentation.

Salesforce documentation on Campaigns and data import processes.

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

References:

Salesforce Reporting and Dashboards Guide

Salesforce Nonprofit Cloud Consultant Study Guide

To measure user adoption after the go-live of Salesforce for program management, the nonprofit can track the following metrics:

Number of Account and Contact Records Created (B):

This metric indicates how actively users are adding new data into the system, reflecting their engagement and usage of Salesforce for managing accounts and contacts.

Percentage of Staff Logging In Weekly (C):

This metric provides insight into how consistently staff members are using Salesforce. High login rates suggest good user adoption, while low rates may indicate a need for additional training or support.

Steps to Measure:

Create Reports:

Use Salesforce reports to track the number of Account and Contact records created over the past 30 days.

Set up a report to monitor user login frequency and calculate the percentage of staff logging in weekly.

Monitor and Analyze:

Regularly review these reports to assess user adoption and identify any areas needing improvement.

References:

Salesforce Adoption Dashboards

Salesforce Trailhead: Measure Salesforce Adoption

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

Criteria-based Sharing:

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

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

References:

Salesforce Sharing and Visibility Guide

Salesforce Criteria-based Sharing Rules Documentation

To quickly query data across multiple systems and get insights on any device about the impact the nonprofit is having, the consultant should recommend:

CRM Analytics (formerly known as Tableau CRM or Einstein Analytics):

CRM Analytics allows for advanced data analysis, visualization, and reporting. It can integrate data from multiple Salesforce objects and external sources, providing comprehensive insights across systems. It is designed to work seamlessly on various devices, ensuring accessibility and usability.

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

Steps to Enable My Domain:

Navigate to Setup:

Go to Setup -> My Domain.

Register My Domain:

Enter your preferred domain name and check its availability.

Register the domain and wait for the confirmation email.

Deploy My Domain:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Help: My Domain

https://www.craftsmantech.com/2019/11/14/npsp-data-import-advanced-mapping/

https://trailhead.salesforce.com/content/learn/modules/data_modeling/schema_builder

To ensure that new system admins understand the purpose of Salesforce field customizations, the following steps should be taken:

Complete All Field Descriptions:

For every custom field created in Salesforce, ensure that the "Description" field is filled out comprehensively.

Go to Salesforce Setup.

Navigate to the Object Manager and select the object that has custom fields.

For each custom field, click on "Edit" and provide a detailed description that explains the field’s purpose, usage, and any important notes regarding its functionality.

Save the changes.

Document Customizations:

Maintain comprehensive documentation of all custom fields, including their descriptions, data types, and any validation rules associated with them.

Use a shared document or a dedicated Salesforce documentation tool to keep this information accessible and up-to-date.

Training and Onboarding:

Create a training module or onboarding program for new system admins that includes an overview of key customizations.

Use Trailhead modules to supplement learning about field management and customization best practices.

Utilize Salesforce Resources:

Encourage new admins to use Salesforce’s Schema Builder to get a visual overview of the data model, which can help them understand how different fields and objects are interconnected.

Leverage the Setup Audit Trail to review any changes made to field customizations and understand their history.

By ensuring that all field descriptions are complete and providing thorough documentation, new system admins will have a clear understanding of the customizations, helping them manage and maintain the Salesforce instance more effectively.

References:

Salesforce documentation on field customization and descriptions

CertGod Nonprofit Cloud Consultant guide​

V

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.

References:

Salesforce Sandbox Preview Guide: Sandbox Preview Instructions.

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

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

Choose Pardot:

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

Set Up Pardot:

Ensure Pardot is integrated with Salesforce.

Configure user permissions and roles in Pardot.

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

Segment and Target Supporters:

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

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

Create Emails with Lightning Email Templates:

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

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

Track Engagement:

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

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

Analyze and Optimize:

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

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

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

References:

Salesforce Pardot documentation on segmentation and email marketing

CertGod Nonprofit Cloud Consultant guide​

https://developer.salesforce.com/forums/?id=9060G000000I7sYQAS ,and “D”.( When importing data into the NPSP Data Import Object, if the error message indicates that the Record ID field is not mapped, the system admin should ensure that the appropriate mapping is set up and use the correct operation for the data loader.

Select the Appropriate Record ID (A):

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

Select "Upsert" Operation (C):

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

Steps to Resolve:

Check Field Mapping:

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

Choose Upsert Operation:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Trailhead: Import Data for Nonprofits

To 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 delegate authority to specific users for processing gift entries, the consultant should add the following permissions to a permission set:

Grant visibility to the Gift Entry tab:

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

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

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

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

Grant access to BDI_BatchOverride and BDI_DataImport Visualforce pages:

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

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

References:

Salesforce documentation on Gift Entry permissions: Gift Entry Permissions

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

Salesforce Canvas:

Salesforce Canvas allows you to embed external applications directly within Salesforce

(https://trailhead.salesforce.com/en/content/learn/modules/contact-and-account-settings-in-nonprofit-success-pack/merge-duplicate-contacts-and-accounts-npsp)

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

Delete Access to Contacts:

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

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

Unique External ID:

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

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Merge Contact Permissions Guide

For a data migration involving tens of millions of records to NPSP over a weekend, the Bulk API is recommended due to its ability to handle large volumes of data efficiently:

Prepare Data for Migration:

Ensure all data is cleaned and formatted correctly for import into Salesforce.

Segment the data into manageable batches to optimize the migration process.

Use Bulk API for Migration:

The Bulk API is designed for loading large data sets and operates asynchronously, allowing for high performance.

Create a Bulk API job to import the data.

Upload data batches and monitor the job status to ensure successful data import.

Minimize System Downtime:

Schedule the data migration to occur during a weekend to reduce the impact on users and minimize system downtime.

Inform stakeholders about the migration schedule and expected downtime.

Verify Data Integrity:

After the migration, run data integrity checks to ensure that all records have been accurately imported.

Compare source data with the imported data in Salesforce to verify completeness.

Using the Bulk API will ensure that the large volume of data is migrated efficiently within the limited timeframe, minimizing disruption to the organization’s operations.

References:

Salesforce documentation on using the Bulk API for data migration

CertGod Nonprofit Cloud Consultant guide​

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.

References:

Salesforce B2B Commerce Documentation

Salesforce Trailhead: Salesforce B2B Commerce Basics

https://trailhead.salesforce.com/content/learn/modules/project-risk-management-for-partners/identify-ass ess-address-risk

In project management, the three elements impacted by change that cause risk are cost, quality, and time. These elements are often referred to as the project management triangle or triple constraint.

Elements Impacted by Change:

Cost: Changes can lead to increased project costs, affecting the budget and financial resources.

Quality: Changes can impact the quality of the project deliverables, potentially leading to rework or reduced standards.

Time: Changes can affect the project timeline, causing delays and extending the project schedule.

Steps for Risk Mitigation:

Identify Potential Risks:

Conduct a risk assessment to identify potential changes that could impact cost, quality, or time.

Develop Mitigation Strategies:

Create plans to mitigate identified risks, including contingency plans and resource allocations.

Monitor and Control:

Regularly monitor the project for changes and adjust plans as necessary to manage risks effectively.

References:

Salesforce Project Management Best Practices

Salesforce Trailhead: Risk Management in Project Management

To restrict access to fields related to background checks on the Contact object so that only the volunteer manager and executive director can access them, the consultant should:

Create a Permission Set:

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

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

Grant Field-Level Security:

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

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

Assign the Permission Set:

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

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

References:

Salesforce documentation on Permission Sets: Permission Sets

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

To ensure effective user acceptance testing and training before going live with its Nonprofit Cloud implementation, a nonprofit can use the following sandbox configuration options:

Partial Data Sandbox:

This sandbox type includes a subset of the production data, which is useful for testing with realistic data without the need for a full copy of the production environment. It provides a balance between data availability and cost.

For tracking and reviewing scholarship applications and recording scholarship recipients, award amounts, and dates, the consultant should recommend setting up the Outbound Funds Module. This module is designed for managing funds that are disbursed, such as grants and scholarships. By connecting the Funding Request to Contacts for the recipient, the nonprofit can effectively manage and track all related information in a structured and organized manner.

References:

Salesforce Outbound Funds Module Documentation

Salesforce Nonprofit Cloud Consultant Study Guide

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

API Version Differences:

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

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

Project Planning:

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

Deployment Strategy:

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

References:

Salesforce Release Notes

Salesforce Sandbox Preview Guide

To provide real-time insights into membership data stored in a proprietary system, the nonprofit should use Salesforce Connect to store this information in External Objects:

Salesforce Connect:

Salesforce Connect allows Salesforce to integrate with external data sources in real-time without the need to import the data into Salesforce.

It uses External Objects to represent the data from the external system, making it accessible within Salesforce like any other object.

Implementing Salesforce Connect:

Set up an external data source connection in Salesforce to the proprietary membership management system.

Define External Objects for the membership data, such as member status, renewal dates, and other relevant data points.

Create relationships between External Objects and standard Salesforce objects (e.g., Contacts, Accounts) to link donor and membership information.

Real-Time Insights:

Use reports and dashboards to display membership data alongside fundraising and program data.

Ensure that membership data is updated in real-time, providing accurate and timely insights.

By utilizing Salesforce Connect and External Objects, the nonprofit can achieve real-time visibility into its membership data without duplicating data storage.

References:

Salesforce Connect Documentation

Trailhead Module: Integrate with External Data Sources Using Salesforce Connect

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

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

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

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

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

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

Consideration for Existing Data:

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

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

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

References:

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

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

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 track all donations that go to a specific, designated fund, the consultant should create a GAU Allocation record for the designated fund. Here’s how to set it up:

Create GAU Records:

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

Create a new GAU record for each designated fund.

Link Donations to GAUs:

When entering or importing donations (Opportunities), use the GAU Allocation section to allocate the donation amount to the relevant GAU.

Specify the amount or percentage of the donation that should be allocated to each GAU.

Set Up GAU Allocation:

In the Opportunity record, scroll to the GAU Allocations related list.

Click "New" to create a new GAU Allocation.

Select the appropriate GAU and enter the allocation amount.

Reporting on GAUs:

Create reports to track donations by GAU.

Use the GAU Allocation object in your report to filter and summarize donations by designated funds.

By using GAU Allocations, the nonprofit can effectively manage and report on restricted funds, ensuring that donations are tracked according to donor intent.

References:

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Manage General Accounting Units (GAUs)

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

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

Steps to Set Up Engagement Plans:

Navigate to the "Engagement Plans" tab in NPSP.

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

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

Assign the Engagement Plan to the appropriate client records.

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

Steps to Set Up Levels:

Navigate to NPSP Settings > Levels.

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

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

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

References:

CertGod Nonprofit Cloud Consultant Guide:

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

Hard Credits:

Hard credits represent the actual donor who made the donation.

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

Soft Credits:

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

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

Scenario Application:

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

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

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

Implementation in NPSP:

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

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

References:

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

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.

References:

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

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

A common cause of the NPSP (Nonprofit Success Pack) upgrade failing when run in Production, despite no issues in the sandbox, is not having adequate test code coverage. This is essential for successful deployments in Salesforce environments.

Test Code Coverage:

Salesforce requires a minimum of 75% test code coverage for deploying Apex code to a production environment.

This means that automated tests must cover at least 75% of the codebase, ensuring that most functionalities are validated and reducing the risk of errors during deployment.

Sandbox vs. Production Differences:

Sandbox environments often have less data and different configurations compared to production, which might not fully mimic real-world scenarios.

In production, there could be additional triggers, validation rules, or workflows that are not present or not active in the sandbox.

Mitigating Upgrade Failures:

Ensure that all custom code, including Apex triggers, classes, and batch processes, has adequate test coverage.

Review and test all dependent packages and configurations in a full sandbox environment that closely replicates the production setup.

Additional Considerations:

Conduct a comprehensive review of all customizations and integrations.

Run the NPSP Health Check Tool and Salesforce Optimizer in sandbox before the actual upgrade to identify potential issues.

References:

CertGod Nonprofit Cloud Consultant study guide: "Not having adequate test code coverage"​​.

To send a mailing to all clients and track who was sent the invitation and who responded, you should use Campaigns in NPSP. Here’s how to set it up:

Create a Campaign:

Navigate to the Campaigns tab.

Click "New Campaign" and fill out the necessary details such as Campaign Name (e.g., "Workforce Development Program Invite").

Filter List View for Clients:

Go to the Contacts tab.

Create a new list view or filter an existing one to include only clients. This might include adding filters for criteria that identify clients, such as specific Account Record Types or custom fields.

Add Contacts to Campaign:

Select all the clients in the list view.

Use the "Add to Campaign" button to add these Contacts to the previously created Campaign.

Track Responses:

After sending the invitations, track responses by updating the Campaign Member Status. This can be done manually or through an automated process if you have integrated email tracking.

Create a Campaign Report:

Go to the Reports tab.

Create a new report using the "Campaigns with Campaign Members" report type.

Filter the report to show the specific Campaign and the statuses of the Campaign Members (e.g., "Sent", "Responded").

This process ensures that the nonprofit can track who the invitations were sent to and who has responded, providing a clear view of the engagement for the workforce development program.

References:

"Campaign Management in NPSP" from Salesforce Help: Campaign Management

"Creating and Managing Campaigns" from Salesforce.org: Campaigns Guide

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.

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

Navigate to NPSP Settings:

Go to Setup.

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

Configure Soft Credits:

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

Ensure that soft credits are enabled for Accounts and Contacts.

Add Soft Credits on Opportunities:

When entering a donation, go to the Opportunity record.

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

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

Track and Report:

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

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

References:

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

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

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

Regular Updates:

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

Automatic Updates:

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

Release Notes:

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

Testing and Sandbox Environments:

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

References:

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

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

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

Salesforce Flows are ideal for guiding users through step-by-step processes, making them a perfect solution for triaging patients. By creating a flow, the nonprofit can ensure volunteers follow a consistent process, capture accurate data, and make immediate service decisions. Here’s how to set this up:

Design the Flow:

Open Flow Builder from Setup.

Create a new Screen Flow.

Add Screens and Inputs:

Add screens with input fields for the qualifying questions.

Use Decision elements to branch the flow based on the answers provided.

Capture Data:

Use Assignment elements to store input data in variables.

Save data to Salesforce records as needed (e.g., Case or Custom Object records).

Generate Decision Outcomes:

Based on the data captured, use Decision elements to determine eligibility.

Display the outcome on a final screen or update a record with the decision.

Test and Deploy:

Test the flow thoroughly in Sandbox.

Deploy the flow to production and embed it in the relevant Lightning pages.

References:

"Create a Simple Flow" from Salesforce Help: Create a Flow

"Guided Processes for Nonprofits" from Salesforce.org: Salesforce Flow for Nonprofits

To capture and analyze wealth scoring for donors in Salesforce, leveraging an AppExchange application is the most effective approach. These applications can provide comprehensive wealth data and insights to support donor cultivation efforts. Here’s how to do it:

Identify Suitable AppExchange Applications:

Search the Salesforce AppExchange for wealth screening and donor prospecting tools (e.g., WealthEngine, DonorSearch).

Install the Application:

Follow the installation instructions provided by the selected application.

Ensure necessary permissions and configurations are set up.

Configure Wealth Scoring:

Set up the application to pull in wealth data for your donor contacts.

Use the provided features to rank and score donors based on their wealth data.

Integrate with NPSP:

Ensure the wealth data integrates with your existing NPSP setup.

Create reports and dashboards to visualize and analyze donor wealth information.

References:

"WealthEngine for Salesforce" on AppExchange: WealthEngine

"DonorSearch for Salesforce" on AppExchange: DonorSearch

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

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

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

If a nonprofit organization has enabled Person Accounts in its Salesforce org and now wants to install NPSP while completely removing all Person Account features, the best approach is to apply for a new Salesforce organization and request a license transfer. Here’s why and how to do it:

Apply for a New Salesforce Organization:

Create a new Salesforce instance without enabling Person Accounts.

This approach avoids the complexities and potential issues of removing Person Accounts from an existing instance.

Request a License Transfer:

Contact Salesforce support to request a transfer of licenses from the old org to the new one.

Provide the necessary details and justification for the transfer.

Install NPSP in the New Org:

Install the Nonprofit Success Pack (NPSP) in the new Salesforce org.

Follow the standard installation and post-installation steps to set up NPSP properly.

Migrate Data:

Plan and execute a data migration from the old org to the new org.

Use data import tools like Data Loader to transfer Contacts, Accounts, Opportunities, and other relevant data.

Ensure data integrity and mapping during the migration process.

By creating a new org and transferring the licenses, the organization can start fresh without the complexities of removing Person Accounts and ensure a smooth transition to using NPSP.

References:

"Salesforce Nonprofit Success Pack Installation" from Salesforce Help: NPSP Installation

"Managing Person Accounts" from Salesforce Help: Person Accounts

To help the executive director understand the overall summary of individuals engaged with the organization across multiple channels, creating a Campaign Hierarchy is the most effective solution. Here’s how to do it:

Create Campaigns for Each Channel:

Navigate to the Campaigns tab.

Create separate Campaigns for donations, volunteer shifts, and event attendance.

Use meaningful names to easily identify the Campaigns.

Build the Campaign Hierarchy:

Within each Campaign, specify a parent Campaign if applicable to create a hierarchy.

For example, an overarching "Engagement 2024" Campaign can have child Campaigns for donations, volunteer shifts, and events.

Associate Campaign Members:

Add relevant individuals to each Campaign as Campaign Members.

Ensure that each Campaign Member record reflects the individual's engagement in that specific channel.

Reporting on Campaign Hierarchy:

Create reports to summarize engagement across the Campaign hierarchy.

Use filters and grouping to display the number of people associated with each type of engagement by channel.

This approach provides a clear and organized view of individual engagement across various activities, making it easy to track and report on overall engagement.

References:

Salesforce NPSP Documentation: Campaign Management

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Campaigns

For tracking job seeker engagements and assigning them to case managers:

Enable web-to-case: This allows job seekers to submit inquiries via web forms, which automatically create cases in Salesforce.

Customize cases: Modify the case object to track specific engagement details from start to finish.

Assignment rules: Set up rules to automatically assign cases (job seekers) to appropriate case managers based on predefined criteria (e.g., job seeker's needs, case manager's workload).

This solution provides a structured way to handle multiple engagement channels (phone, web, email) and ensures that each job seeker is assigned a case manager for personalized support.

References:

Salesforce Help: Setting Up Web-to-Case

Salesforce Trailhead: Service Cloud for Nonprofits

To ensure data hygiene and maintenance in Salesforce, it’s essential to follow best practices that help in keeping the data clean and organized. Here are the detailed steps:

Organize Reports into Appropriate Folders:

Navigate to the Reports tab.

Create folders for different types of reports (e.g., Fundraising, Program Management).

Move existing reports into these folders for better organization.

Run Health Check:

Navigate to Setup.

In the Quick Find box, type "Health Check".

Run the Health Check to evaluate your org’s security settings against Salesforce security baseline.

Review the findings and follow the recommendations to improve data security and compliance.

References:

"Organize Reports and Dashboards" from Salesforce Help: Organize Reports

"Salesforce Health Check" from Salesforce Help: Health Check

When a system administrator attempts to delete a Household Account record that has Contacts with Recurring Donations, Relationships, and closed/won donations, Salesforce will display an error message due to the presence of closed/won donations associated with the Account record.

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

Navigate to the Household Account:

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

Attempt to Delete the Account:

Try to delete the Household Account record.

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

Review Associated Records:

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

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

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

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

Access NPSP Public Data Dictionary:

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

Navigate to the NPSP documentation section.

Search for the Field:

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

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

Verify Field Information:

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

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

To transition from Person Accounts to the Household Account model in NPSP and avoid interacting with Person Accounts, the recommended approach is to migrate to a new Salesforce NPSP org. Here’s how:

Apply for a New Salesforce NPSP Org:

Contact Salesforce to apply for a new NPSP org.

Ensure the organization qualifies for the NPSP and request the necessary licenses.

Request License Transfer:

Work with Salesforce support to transfer existing licenses from the current org to the new NPSP org.

Export Data from Current Org:

Export all Person Account data, including Contacts, Accounts, Opportunities, and any other relevant records.

Use Salesforce Data Loader or another export tool to ensure a complete data export.

Prepare Data for Import:

Clean and prepare the exported data for import into the new org.

Map Person Account data to the appropriate fields in the Household Account model.

Import Data into New NPSP Org:

Use the NPSP Data Importer or Data Loader to import the cleaned data into the new org.

Ensure that all relationships and references are correctly mapped and maintained during the import process.

This method ensures a clean transition to the Household Account model without the complications of dealing with Person Accounts in the original org.

References:

Salesforce NPSP Documentation: Account Models

Salesforce Trailhead: Data Import Strategies

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

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

Create the Report:

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

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

Create a Custom Object:

Create a custom object to store the snapshot data.

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

Set Up the Reporting Snapshot:

Navigate to Setup.

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

Click "New Reporting Snapshot".

Name the snapshot and select the source report you created.

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

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

Schedule the Reporting Snapshot:

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

Save and activate the schedule.

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

References:

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

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

To create a custom Apex class in the TDTM (Table Driven Trigger Management) framework, follow these steps:

Create the Apex Class:

In Salesforce, go to Setup.

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

Click "New" and create your custom Apex class.

Ensure the class implements the TDTM framework correctly.

Create the Test Class:

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

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

Create a Trigger Handler Record:

Go to the TDTM Trigger Handlers tab.

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

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

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

References:

Salesforce NPSP Documentation: TDTM Overview

Salesforce Trailhead: Apex Basics & Database

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

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

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

References:

Power of Us Hub

Salesforce Trailhead: Engaging with the Salesforce Nonprofit Community

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

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

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

Log in to Salesforce: Access the Salesforce org.

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

Run Salesforce Optimizer:

Click "Run Optimizer".

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

Review the Report:

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

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

Make a Recommendation:

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

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

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

Install NPSP:

Ensure that NPSP is installed in your Salesforce instance. You can download it from the AppExchange or install it directly from the NPSP Installer page​​.

Configure Acknowledgement Settings:

Navigate to NPSP Settings.

Under “Donations,” find the “Acknowledgements” settings.

Configure the settings to define when and how acknowledgements should be sent.

Set Up Email Templates:

Go to Setup > Classic Email Templates.

Create a new email template or modify an existing one to suit your acknowledgment needs.

Ensure the template includes merge fields to personalize the emails with donor information.

Create Automation with Process Builder:

Use Process Builder to automate the sending of acknowledgment emails.

Create a new process on the Opportunity object.

Set criteria to trigger the process when a new donation is recorded.

Add an action to send an email using the previously created template.

Testing:

Test the process by creating a test donation record and verifying that the acknowledgment email is sent automatically.

Monitoring and Refinement:

Monitor the process to ensure it is working correctly.

Refine the email templates and automation rules based on feedback and evolving needs.

By utilizing the NPSP, nonprofits can streamline their donation acknowledgment process, ensuring timely and personalized communications with donors, ultimately enhancing donor satisfaction and retention.

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

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

Prepare Data Files:

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

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

Access NPSP Data Importer:

Go to the App Launcher.

Search for and open "NPSP Data Importer".

Configure Import Settings:

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

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

Save Import Mappings:

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

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

Import Data:

Upload the respective data files to the NPSP Data Importer.

Select the appropriate template for each import process.

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

Verify and Clean Up:

Verify the imported data for accuracy.

Use the NPSP tools to manage any duplicates or discrepancies.

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

References:

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

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

To 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

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

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

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

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

References:

Salesforce Governance Framework Documentation

Salesforce Trailhead: Center of Excellence

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.

References:

Salesforce Nonprofit Success Pack Documentation

Salesforce Marketing Cloud Overview

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

Navigate to NPSP Settings:

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

Access Donations Settings:

Under NPSP Settings, select "Donations".

Click on "Opportunity Contact Roles".

Configure Default Contact Role:

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

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

Verify and Save:

Ensure that the configuration is correct and save the changes.

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

References:

Salesforce NPSP Documentation: Opportunity Contact Roles

Salesforce Trailhead: Manage Donations in NPSP

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

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