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

https://powerofus.force.com/s/article/NPSP-Merging-Contacts

When a staff member receives an error while attempting to merge duplicate contacts, it is often due to insufficient permissions. Creating a Permission Set with "Modify All" on Contacts and Accounts and assigning it to the staff member will grant the necessary permissions to perform merges. This Permission Set will override the default profile permissions and provide the required access to manage and merge contacts.

Steps:

Go to Setup > Permission Sets.

Click "New" to create a new Permission Set.

Name the Permission Set appropriately (e.g., "Contact Merge Permissions").

In the Permission Set, navigate to Object Settings.

Select Contacts and Accounts.

Check the "Modify All" checkbox for both objects.

Save the Permission Set.

Assign the Permission Set to the staff member by navigating to the user's profile and adding the Permission Set.

https://powerofus.force.com/s/article/NPSP-Install

The recommended method to install NPSP in an existing Salesforce org is to use the NPSP Installer page. This installer simplifies the process by guiding users through the necessary steps and ensuring that all components are correctly installed.

Steps:

Navigate to the NPSP Installer page on Salesforce.org.

Click the "Install NPSP" button to start the installation process.

Follow the prompts to authenticate and select the Salesforce org where NPSP will be installed.

The installer will automatically download and configure all required NPSP components.

Verify the installation by checking the NPSP settings and ensuring all components are functional.

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

Test Code Coverage:

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

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

Sandbox vs. Production Differences:

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

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

Mitigating Upgrade Failures:

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

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

Additional Considerations:

Conduct a comprehensive review of all customizations and integrations.

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

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.

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

Volunteers Personal Site:

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

Steps to Set Up:

Navigate to Setup > Sites.

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

Add the Volunteers Personal Site tab and configure the permissions.

Direct volunteers to use this site to log their hours.

Log Volunteer Hours Section on Website:

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

Steps to Set Up:

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

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

Direct volunteers to this section to submit their hours.

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

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

To protect sensitive data like a government-issued ID number, encrypting the field and carefully managing access permissions is crucial. Here's a step-by-step guide on implementing this security solution:

Create the Custom Field:

Navigate to Setup.

In the Object Manager, select the relevant object (e.g., Contact).

Click on Fields & Relationships.

Create a new Text field for the government-issued ID number.

Enable Classic Encryption for Custom Fields:

In Setup, search for "Encryption Policy".

Enable "Encrypt Custom Fields".

Select the custom field you created for the government-issued ID and mark it for encryption.

Set Permissions:

Navigate to Setup.

Go to Profiles or Permission Sets.

Ensure only the necessary profiles/permission sets have the "View Encrypted Data" permission:

Click on the relevant Profile or Permission Set.

In System Permissions, enable "View Encrypted Data".

Assign this permission only to those users who need to interact with the government ID data.

Adjust Field-Level Security:

In the Object Manager, select the custom field for the government ID.

Click on "Set Field-Level Security".

Ensure the field is visible only to the necessary profiles.

Remove the field from page layouts for users who should not access it.

Test the Setup:

Log in as a user with access to the encrypted data to verify they can view and interact with the data.

Log in as a user without access to ensure they cannot see the encrypted field.

By following these steps, you ensure that the government-issued ID number is encrypted and only accessible to authorized personnel, thereby protecting sensitive client data effectively.

To load 45,000 records into Salesforce from a single flat file:

Data Loader: This tool is designed for bulk data import and export, handling large volumes of records efficiently. It supports complex data mappings and transformations required for importing donor, donation, and payment processing records.

Large Volume Handling: Data Loader can process up to millions of records, making it suitable for the task at hand.

Using Data Loader ensures that the records are imported accurately and efficiently, with the ability to handle data transformations as needed.

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.

To help a nonprofit run a large scholarship program using Salesforce for accepting external scholarship applications, reviewing processes, and tracking requirements, the following solutions are recommended:

Experience Cloud:

Experience Cloud allows the nonprofit to create a community or portal where external applicants can submit their scholarship applications.

It provides a user-friendly interface for applicants and reviewers to interact with the application process.

Steps to Implement Experience Cloud:

Set up an Experience Cloud site and customize it to match the nonprofit’s branding.

Create forms and pages for application submission.

Enable user roles and permissions to control access for applicants and reviewers.

Outbound Funds Module:

The Outbound Funds Module (OFM) is specifically designed to manage the distribution of funds, such as scholarships.

It allows for tracking applications, managing review processes, and ensuring compliance with scholarship requirements.

Steps to Implement Outbound Funds Module:

Install and configure the Outbound Funds Module from the AppExchange.

Set up funding programs, grant types, and application criteria.

Use OFM’s built-in features to manage the review and approval workflows.

These solutions provide a comprehensive and integrated approach to managing the scholarship program within Salesforce.