Salesforce Nonprofit-Cloud-Consultant Dumps

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

GAU Allocation Record:

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

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

Salesforce NPSP Documentation on General Accounting Units (GAUs)

Salesforce Nonprofit Success Pack GAU Allocation Guide

For loading a large volume of records, such as approximately 3 million records, into Salesforce, the Bulk API is the most efficient method. The Bulk API is designed to handle large data sets by processing records asynchronously in batches, which reduces the load on Salesforce servers and ensures efficient data transfer. This API is optimized for data loading and extraction, making it ideal for high-volume data operations.

Salesforce Bulk API Developer Guide

Salesforce Nonprofit Cloud Data Import Best Practices

When migrating historic donation records into a nonprofit's Salesforce org where many of these donations were paid in multiple installments, it is important to ensure that the Payments are correctly matched to the Opportunities. The correct approach involves using the "Do Not Automatically Create Payment" field:

Check the Do Not Automatically Create Payment Field:

When importing historic donations, check the "Do Not Automatically Create Payment" field on the Opportunities.

This prevents Salesforce from automatically creating Payments for these Opportunities, which allows you to manually enter the correct Payments that match the historic installment records.

Manually Create Payments:

After importing the Opportunities with the "Do Not Automatically Create Payment" field checked, manually create Payment records that correspond to each installment.

Ensure each Payment is correctly associated with the corresponding Opportunity.

Validation:

Validate the imported data to ensure all Payments are correctly matched with the Opportunities.

This method ensures that the historic donation records with multiple installments are accurately represented in Salesforce.

When migrating data from a legacy donor management database, the NPSP Data Importer is the recommended tool for loading donor contact information, donation history, and payment information into Salesforce. Here’s why:

NPSP Data Importer:

The NPSP Data Importer is specifically designed for nonprofits using the Nonprofit Success Pack (NPSP).

It supports importing multiple related records (Contacts, Accounts, Opportunities, Payments) in a single file, making it ideal for comprehensive data migration.

The tool provides mapping capabilities to ensure that fields in the import file are correctly mapped to Salesforce fields.

It includes features to handle common nonprofit data structures such as household accounts, affiliations, and recurring donations.

Using NPSP Data Importer minimizes the risk of data discrepancies and ensures that all related records are correctly created and linked.

Salesforce documentation on NPSP Data Importer: NPSP Data Importer

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

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.

For a volunteer manager to search for volunteers with specific skills and availability using Volunteers for Salesforce, the following steps can be advised:

Use the Find Volunteers Tab:

Click on the "Find Volunteers" tab in Salesforce.

Filter Criteria:

Fill in the Volunteer Status, Volunteer Availability, and Volunteer Skills tabs with the required values:

Volunteer Status: Select the appropriate status (e.g., Active, Available).

Volunteer Availability: Specify the dates and times the volunteer is available.

Volunteer Skills: Include landscaping or other required skills.

Hit Search:

Click on the "Search" button to retrieve the list of volunteers matching the criteria.

Review and Contact Volunteers:

Review the list of volunteers who meet the criteria.

Use the contact information provided to reach out to the suitable volunteers for the specific task.

This method leverages the built-in search functionalities in Volunteers for Salesforce, providing an efficient way to find and manage volunteers based on specific needs.

Volunteers for Salesforce Documentation: Finding and Managing Volunteers

Salesforce Trailhead: Volunteers for Salesforce

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.

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

Complexity with the Address Object:

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

Impact on Data Storage:

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

Steps for Migration:

Data Preparation:

Clean and standardize the data before migration to ensure consistency.

Identify and remove duplicates to avoid data redundancy.

Data Mapping:

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

Data Import Tools:

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

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

Testing and Validation:

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

Validate the imported data to ensure accuracy and completeness.

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

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

To configure Accounting Subledger so that only the appropriate records are created and available for export to finance, you need to set up Stage to State Mapping. This ensures that only donations at a certain stage are included in the ledger entries. Here are the steps:

Access Accounting Subledger Setup:

Navigate to the Accounting Subledger settings in Salesforce.

Configure Stage to State Mapping:

Define the mapping between Opportunity Stages and Accounting Subledger States.

For example, map the "Closed Won" stage to a state that signifies the donation is ready for ledger entry creation.

Update Opportunity Stages:

Ensure that your Opportunity Stages are correctly set up to reflect the different states of your donation process (e.g., "Pledged", "Received").

Create Ledger Entries:

Once an Opportunity reaches the specified stage (e.g., "Closed Won"), a ledger entry is automatically created.

Only these ledger entries are included in the export to finance.

By configuring the Stage to State Mapping, you ensure that only finalized donations (those that reach a specific stage) are included in the ledger entries, making the finance export process more efficient and accurate.

Salesforce Accounting Subledger Documentation: Stage to State Mapping.

To ensure that the person being honored by a tribute gift consistently receives the proper soft credit, the nonprofit should set up Automatic Opportunity Contact Roles in NPSP and configure the Honoree role. This automation ensures that the honoree is always credited appropriately without manual intervention.

Steps:

Navigate to NPSP Settings > Donations > Automatic Opportunity Contact Roles.

Add a new Contact Role with the role type "Honoree."

Set the role to be automatically assigned to Opportunities that meet the criteria for tribute gifts.

Test the configuration by creating a new tribute gift and verifying that the Honoree Contact Role is correctly assigned.

Train staff on how to use the new setup to ensure consistency in data entry.

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

Create Program Engagement Records:

Navigate to the "Program Engagements" tab.

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

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

Select the Program:

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

Specify the Services:

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

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.

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

Closed/Won Donations:

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

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

Error Message:

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

Salesforce Documentation on Record Deletion and Related Records

Salesforce NPSP Data Integrity and Protection Guide

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 a corporate matching gift is received and the original donation was not marked to be matched, you should use the "Find Matched Gifts" functionality:

Navigate to Find Matched Gifts:

Go to the donation record in Salesforce.

Select "Find Matched Gifts" from the related options.

Find More Gifts:

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

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

To help prevent interruptions between integrations and Salesforce, creating a user account solely for integrations is a recommended strategy. Here’s why and how to set it up:

Create a Dedicated Integration User:

Navigate to Setup > Users > Users.

Create a new user specifically for integration purposes.

Assign an appropriate profile with the necessary permissions for the integrations.

Benefits of a Dedicated Integration User:

Isolation of Permissions: The integration user can be given only the permissions required for the integrations, enhancing security.

Minimized Risk of Interruption: If individual user credentials are changed or users leave the organization, the integrations remain unaffected.

Audit and Monitoring: It is easier to monitor and audit integration activities when they are tied to a dedicated user account.

Set API Access for the Integration User:

Ensure that the profile assigned to the integration user has API access enabled.

Configure any necessary OAuth settings if using OAuth for authentication.

Test the Integration:

Use the integration user credentials to set up and test the integrations.

Ensure that the integrations are functioning correctly and that data is being transferred as expected.

By creating a dedicated integration user, you can ensure more stable and secure integration processes between Salesforce and other systems.

Salesforce Integration Best Practices: Integration Best Practices.

Salesforce User Management Guide: User Management.

Top of Form

Bottom of Form

To create a report showing how much each board member has raised, you should:

Use the Opportunities report type: This allows you to capture all gift data.

Add a cross filter for Contacts with Board Member = TRUE: This filters the report to include only those contacts who are board members.

Summarize the Total Gifts this Year and Soft Credits this Year fields: This provides the total amounts for direct gifts and influenced gifts.

This method ensures that both direct contributions and soft credits (gifts influenced by board members) are included in the report.

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.

To automatically credit the spouse for a donation in NPSP, the consultant should recommend enabling Automatic Soft Credit for household members in the NPSP settings. This setting ensures that any donation made by a household member is automatically soft credited to other members of the household.

Steps to Enable:

Navigate to NPSP Settings:

Go to Setup -> NPSP Settings.

Enable Automatic Soft Credits:

Under Donations -> Soft Credits, enable the option for Automatic Soft Credit for Household Members.

Verify Soft Credits:

Check the Opportunity records to ensure that soft credits are correctly applied to household members.

When a consultant is about to begin a data project with a nonprofit to clean up Opportunity data and needs to temporarily disable NPSP Triggers for performance reasons, it is typically necessary when uploading a large volume of records, such as 1 million new Contact records.

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.

Disable Triggers:

In the NPSP Settings, expand "Bulk Data Processes" and then "TDTM".

Find the specific triggers related to the data being uploaded.

Disable the relevant triggers by unchecking the "Active" checkbox.

Save the changes.

Perform Data Upload:

Use a data loader or similar tool to upload the 1 million Contact records.

Ensure data integrity and verify successful upload.

Re-enable Triggers:

After the data upload is complete, go back to the NPSP Settings.

Re-enable the previously disabled triggers by checking the "Active" checkbox.

Save the changes.

Verify and Test: Confirm that the triggers are working correctly and that the data has been uploaded properly.

When installing NPSP (Nonprofit Success Pack) in an existing Salesforce org for a nonprofit organization that plans to use the memberships feature, the consultant should create a Membership Opportunity record type. This step is crucial because it allows the organization to effectively track and manage membership-related opportunities distinctly from other types of opportunities.

Steps:

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

Navigate to Object Manager: Go to Setup and search for "Object Manager".

Select Opportunity Object: From the Object Manager, select the Opportunity object.

Create a New Record Type:

Click "Record Types" under the Opportunity object.

Click "New" to create a new record type.

Enter "Membership" as the Record Type Label.

Provide a description such as "Record type for tracking membership opportunities".

Select the existing record type to clone from (e.g., "Master").

Assign this record type to appropriate profiles.

Click "Save".

Customize Page Layouts: Assign and customize page layouts for the new Membership record type as needed.

Verify and Test: Ensure that the Membership record type is correctly set up by creating a test membership opportunity.

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 segment constituents based on their one-time donations from the prior fiscal year, the nonprofit should use Customizable Rollups in NPSP:

Customizable Rollups:

Customizable Rollups in NPSP allow nonprofits to create custom rollup fields that aggregate data based on specific criteria, such as donation type and date range.

These rollups can be configured to include only one-time gifts received during the prior fiscal year.

Setting Up Rollups:

Navigate to NPSP Settings.

Go to "Donations" and then "Customizable Rollups."

Create a new rollup that sums one-time donations within the specified date range (the prior fiscal year).

Use this rollup field to segment and analyze constituents based on their donation history.

Reporting and Segmentation:

Use the rollup field in reports and list views to segment constituents and analyze their giving patterns.

When defining user stories for a Salesforce implementation, it is essential to ensure that each story is aligned with the overall vision of the project and that they are prioritized based on business needs. This approach helps in delivering value incrementally and keeps the project focused on the key objectives.

Key Components of a User Story:

Alignment with Vision (A):

Ensure that each user story aligns with the nonprofit's overall implementation vision. This alignment helps in maintaining consistency and achieving the strategic goals of the organization.

Assign Priority (C):

Assign a priority to each user story to manage the implementation effectively. Prioritizing user stories ensures that the most critical functionalities are developed and delivered first.

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

Steps:

Enable Deliverables in Salesforce.

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

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

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

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.

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.

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

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

Salesforce Program Management Module Documentation: PMM Documentation.

Salesforce Outbound Funds Module Documentation: OFM Documentation.

Salesforce Education Data Architecture Documentation: EDA Documentation.

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

Steps to Verify:

Check Merge Settings:

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

Review Audit Logs:

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

Restore if Necessary:

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

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.

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.

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

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

GAU Allocations:

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

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

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.

Salesforce Outbound Funds Module Documentation

Salesforce Nonprofit Cloud Consultant Study Guide

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

Marketing Cloud Connect:

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

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

Email Studio Send Details:

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

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

Salesforce Marketing Cloud Connect Documentation

Salesforce Email Studio Reporting Guide

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.

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 ensure the campaign for monthly project updates to donors who have given 10 or more times stays current, the consultant should:

Create a Contact Report:

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

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

Run the Report Monthly:

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

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

Salesforce Reporting Guide

Salesforce Campaign Management Guide

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.

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

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.

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

Account: Import accounts first to establish the primary records.

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

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

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

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

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

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.

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

Salesforce Nonprofit Cloud Consultant Study Guide

Marketing Cloud Implementation Guide

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

Collect Contact Information During Job Sign Up:

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

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

Steps to Set Up Job Listings:

Navigate to the Volunteers for Salesforce setup.

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

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

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

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

Steps to Set Up Web-to-Volunteer:

Go to Volunteers for Salesforce settings.

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

Embed the form on the nonprofit’s website.

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

Pardot is the recommended automation method for sending out automated renewal emails on a 30/60/90 day schedule, with different email templates based on members' website visits. Pardot is a powerful marketing automation tool that integrates seamlessly with Salesforce, providing advanced capabilities for email marketing, lead nurturing, and segmentation. Here’s how to set this up:

Integrate Pardot with Salesforce:

Ensure that Pardot is connected to your Salesforce instance. This allows seamless data synchronization between the two systems.

Create Email Templates in Pardot:

Design and create the different email templates in Pardot that you want to use for the 30, 60, and 90-day renewal reminders.

Personalize the email content based on the members’ interactions and website visits.

Set Up Automation Rules:

Use Pardot’s automation rules to create rules that trigger emails based on the members' renewal dates and website activity.

Define the criteria for each rule (e.g., 30 days before renewal date, 60 days before renewal date, etc.).

Create Engagement Programs:

Use Engagement Studio in Pardot to create automated drip programs that send out the renewal emails at the specified intervals.

Add logic to the engagement program to select different email templates based on the members' website visits and interactions.

Track and Analyze:

Use Pardot’s reporting and analytics features to track the performance of the email campaigns, monitor open rates, click-through rates, and engagement metrics.

By leveraging Pardot’s advanced automation capabilities, the organization can efficiently manage and personalize its renewal email campaigns, improving member retention and engagement.

"Getting Started with Pardot" from Salesforce Help: Pardot Setup Guide

"Pardot Engagement Studio" from Salesforce Help: Engagement Studio

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.

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

Email Marketing:

Design and send personalized emails to supporters.

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

Social Media Engagement:

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

Monitor social media conversations and engage with constituents.

Text Messaging:

Implement Mobile Studio for SMS and MMS campaigns.

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

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

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 improve search performance when migrating a large volume of donation data into the Nonprofit Success Pack (NPSP) for a nonprofit, the consultant should consider implementing Skinny Tables and Custom Index. Here is a detailed explanation:

Skinny Tables:

Skinny tables are a performance optimization technique in Salesforce used to improve the performance of read-only operations.

They are highly effective in environments with large volumes of data, such as the scenario described with 20 years of donation data and over 200,000 donations each year.

A skinny table contains frequently accessed fields and can significantly reduce query time.

Skinny tables are maintained by Salesforce and do not require changes to the custom object schema or existing queries.

They are particularly useful for scenarios involving complex reports and list views.

Custom Index:

Custom indexes enhance the performance of search queries in Salesforce.

Creating custom indexes on fields that are frequently used in search filters and conditions can drastically improve search performance.

Salesforce allows up to 25 custom indexes per object, which can be leveraged to optimize searches on key fields such as donor names, donation dates, and amounts.

Custom indexes should be applied to fields involved in frequently used WHERE clauses in SOQL queries.

Salesforce documentation on Skinny Tables: Skinny Tables

Salesforce documentation on Custom Index: Custom Index

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.

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.

To allow case managers to create and edit service delivery records in the Program Management Module (PMM), you should assign the appropriate permissions through Permission Sets. Permission Sets provide a way to grant specific permissions to users without changing their profiles, making it easier to manage access to certain functionalities.

Steps:

Create a Permission Set:

Navigate to Setup -> Permission Sets.

Click "New" to create a new permission set.

Grant Permissions:

In the new permission set, go to Object Settings.

Find and select "Service Deliveries."

Grant "Create" and "Edit" permissions.

Assign the Permission Set:

Assign the newly created permission set to the case managers who need access to create and edit service delivery records.

A Salesforce-recommended V2MOM includes key components that guide an organization’s strategic planning and execution. The two sections that should be included are:

Vision:

This section defines what you want to achieve. It sets the overall direction and purpose of the plan. For example, "Increase donor engagement and retention by 20% over the next fiscal year."

Metrics:

This section includes the measures of success. Metrics help track progress and determine if the vision and goals are being met. For example, "Track the number of new donors, donor retention rate, and total donations received."

Including these sections ensures that the organization has a clear direction (Vision) and a way to measure success (Metrics), which are critical for strategic planning and execution.

"V2MOM: Vision, Values, Methods, Obstacles, and Measures" from Salesforce Blog: V2MOM Framework

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

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

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

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

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.

Salesforce NPSP Documentation: TDTM Overview

Salesforce Trailhead: Apex Basics & Database

Before importing a large volume of data into an NPSP org, it’s crucial to ensure data quality and optimize performance. Here are the steps:

Check if the Data is Clean, Structured, and in its Final Format:

Review the data to ensure it is free of duplicates, correctly formatted, and complete.

Clean data before importing to avoid data quality issues.

Disable Certain Apex Classes Using TDTM:

Navigate to NPSP Settings in Salesforce.

Under "Settings", find "TDTM (Table Driven Trigger Management)".

Temporarily disable non-essential Apex classes that might interfere with the data import process. This helps improve the import performance and reduces the risk of errors.

By following these steps, you can ensure that the data import process is smooth and that the imported data maintains high quality.

"Preparing for Data Import in NPSP" from Salesforce Help: Data Import Preparation

"Managing TDTM in NPSP" from Salesforce.org: TDTM Management

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.

"WealthEngine for Salesforce" on AppExchange: WealthEngine

"DonorSearch for Salesforce" on AppExchange: DonorSearch

When an international nonprofit adds a translated Relationship picklist value but both Relationship records are displaying incorrectly, the likely cause is that the reciprocal relationship value is missing in the NPSP Settings tab.

Reciprocal Relationship Setup:

In NPSP (Nonprofit Success Pack), relationships between contacts often need to be reciprocal. For example, if Contact A is listed as "Parent" of Contact B, then Contact B should be automatically listed as "Child" of Contact A.

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

NPSP Data Dictionary:

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

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

Salesforce NPSP Data Dictionary Documentation

Salesforce Nonprofit Success Pack Release Notes

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

Digital Engagement:

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

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

To troubleshoot the error message "Npsp,TDTMCContact

of AfterUpdate caused by : System,SObjectException

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

Check for Invalid Values:

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

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

Steps to Verify and Correct Values:

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

Check for any discrepancies or invalid entries.

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

Review Field Mappings and Settings:

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

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

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

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.

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

Access the NPSP Installer Page:

Go to the NPSP Installer page: NPSP Installer

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

Initiate the Installation:

Click on the installation link for the latest NPSP version.

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

Follow the Installation Wizard:

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

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

Complete Post-Install Instructions:

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

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

"Installing NPSP" from Salesforce.org: Installing NPSP

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

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

Understanding Household Account Model:

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

Scenario Explanation:

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

Steps to Build the Report:

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

Select the Mailing Address Field:

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

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

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

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

Why Not Other Options:

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

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

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

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

Salesforce Nonprofit Cloud Documentation on Household Account Model

Salesforce Reports and Dashboards Guide

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

Create a Flow:

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

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

Design the Flow:

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

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

Deploy the Flow:

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

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

Training and Support:

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

Monitor usage and collect feedback to make any necessary adjustments.

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

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.

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.

Salesforce Nonprofit Success Pack Documentation

Salesforce Merge Contact Permissions Guide

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 access a list of constituents who do not reside at their household mailing address, you should create a report with the following steps:

Create a New Report:

Navigate to the Reports tab in Salesforce.

Click on "New Report."

Select Report Type:

Choose "Contacts & Accounts" as the report type.

Add Filters:

Add a filter for "Address Override" and set it to "True."

This filter will include only those constituents whose mailing address is overridden to a different address than their primary household address.

Customize Report Columns:

Include relevant columns such as Contact Name, Household Name, and Address details in your report.

Run and Save the Report:

Run the report to ensure it captures the correct data.

Save the report for future use and sharing with the mail house.

By filtering the Contacts and Accounts report for Address Override = True, you can easily access and export a list of constituents who prefer to receive mail at a different address.

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

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.

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

Navigate to the NPSP SYBUNT Report:

Go to the Reports tab.

Find and open the NPSP SYBUNT report template.

Customize the Date Range:

Click on the “Filters” pane.

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

Modify Report Criteria:

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

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

Run the Report:

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

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

"Using NPSP Reports" from Salesforce Help: NPSP Reports

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