Pass the Salesforce Nonprofit Cloud Consultant Nonprofit-Cloud-Consultant Questions and answers with ExamsMirror

For donors who prefer to have their recurring donations three times per year, follow these steps to create a custom installment period in NPSP:

Navigate to NPSP Settings:

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

Access Recurring Donations Settings:

In NPSP Settings, click on "Donations".

Select "Recurring Donations".

Create a Custom Installment Period:

Click on "Custom Installments".

Add a new custom installment period named "Tri-Yearly" or any other preferred name.

Define the specific details for this installment period, such as frequency and dates.

Add to Installment Picklist:

Ensure the new custom installment period is added to the Recurring Donation installment picklist.

Update existing recurring donations as needed to use the new installment period.

This customization allows the organization to accommodate donors who prefer tri-yearly installments.

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.

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.

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

Role Name Field on Partial Soft Credit Object:

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

MergeContacts List Button:

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

Custom Unique Id Matching:

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

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

When a nonprofit organization creates a custom Opportunity name for all organization donations, the consultant should discuss the following considerations:

Using the "Refresh Name" Action (B):

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

Navigate to the Opportunity record.

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

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

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

Go to NPSP Settings.

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

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

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

To ensure that a subset of users can fully access the government-issued personal identification numbers stored in encrypted fields on Contact records, you must enable the "View Encrypted Data" permission in a permission set. This permission allows users to see the actual encrypted data instead of a masked value.

Steps to Enable:

Create or Edit a Permission Set:

Navigate to Setup -> Permission Sets.

Create a new permission set or edit an existing one.

Enable View Encrypted Data:

In the permission set, go to System Permissions.

Enable the "View Encrypted Data" permission.

Assign Permission Set:

Assign the permission set to the appropriate users who need to access the encrypted data.

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

Navigate to Sharing Settings:

Go to Setup in Salesforce.

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

Create a Criteria-Based Sharing Rule:

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

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

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

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

Save and Apply the Rule:

Save the sharing rule and ensure it is activated.

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

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

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.

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.

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.