Free Salesforce Nonprofit-Cloud-Consultant Practice Exam with Questions & Answers | Set: 3

https://powerofus.force.com/s/article/SFDO-BP-Pardot-Basics-for-Nonprofit-and-Education

The "Send List Email" feature in Salesforce is ideal for sending emails to multiple contacts directly from Salesforce without needing a separate email service provider. It also allows managing bounces, resending emails, and tracking email history on Contact records.

Send List Email Overview:

This feature enables users to send emails to a list of contacts, leads, or campaign members directly from Salesforce.

It supports email templates and provides tracking capabilities.

Steps to Use Send List Email:

Step 1: Navigate to the Contacts or Leads tab.

Step 2: Create a list view that includes the contacts you want to email.

Step 3: Select the "Send List Email" button.

Step 4: Choose an email template, compose the email, and send it.

Managing Bounces and Send History:

Bounces: Salesforce tracks email bounces, and you can view bounce details on the individual contact records.

Send History: The history of sent emails, including opens and clicks, is tracked and visible on the Contact records.

Benefits:

Integrated Solution: No need for external email service providers.

Efficiency: Quickly send emails to multiple recipients and manage communications directly within Salesforce.

Tracking: Monitor email performance and follow up as needed.

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

Understanding Affiliations in NPSP:

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

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

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

Setting Up Affiliations:

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

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

Creating and Managing Affiliations:

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

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

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

Using Affiliations for Reporting:

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

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

Benefits of Using Affiliations:

It provides a structured way to manage complex donor relationships.

Enhances reporting capabilities by allowing detailed analysis of donor connections.

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

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 track grant lifecycles using the Nonprofit Success Pack (NPSP), you can utilize a combination of Opportunities, Payments, Deliverables, and Activities. Here’s how you can set this up:

Opportunities for Grants:

Create an Opportunity record for each grant.

Use custom fields or record types to distinguish grants from other types of Opportunities.

Payments:

Use the Payments object to track actual disbursements for each grant.

Associate Payments with the corresponding Opportunity.

Deliverables for Applications and Deadlines:

Create Deliverables (a custom object or use Tasks/Activities) to track grant applications and reporting deadlines.

Link Deliverables to the Opportunity record.

Activities for Action Assignments:

Use Tasks or Events to assign actions to staff members.

These activities can be associated with the Opportunity to keep everything organized.

By using these elements, you can have a comprehensive view of each grant’s lifecycle, from application to final reporting, including all associated payments and staff actions.

"Grant Management in Salesforce" from Salesforce Help: Grant Management

"Using NPSP for Grant Management" from Salesforce.org: Grant Management with NPSP

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

Create a Permission Set:

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

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

Grant Field-Level Security:

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

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

Assign the Permission Set:

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

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

Salesforce documentation on Permission Sets: Permission Sets

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

https://sites.google.com/a/cloud4good.com/salesforce-glossary/home/npsp-user-manual/chapter-4-entering-data/npsp-data-importer-tool

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

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

Access Setup:

Navigate to Setup in Salesforce.

Enable Guest User Permissions:

Go to Sites and Domains > Sites.

Click on the site label for your volunteer portal.

Click on Public Access Settings.

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

Grant Guest Users Update Access:

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

Test the Configuration:

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

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

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

Salesforce Help Documentation: Sites and Public Access Settings.

https://trailhead.salesforce.com/en/content/learn/modules/search_solution_basics/search_solution_basics_optimizing

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

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

Verify Custom Fields on Payments Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

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

Ensure Field is Included in Report Type:

Go to the Report Builder.

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

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

Add Field to Report Layout:

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

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

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

Salesforce Documentation: Custom Fields

Salesforce Trailhead: Create Reports with the Report Builder