Nonprofit-Cloud-Consultant Salesforce Certified Nonprofit Cloud Consultant (NPC) NP-Con-102 Questions and Answers

To capture information for grants and easily access previous grant details, the following setup can be used in Salesforce:

Previous Grant/Gift Opportunity Lookup Field:

Add a lookup field on the Opportunity object called "Previous Grant/Gift Opportunity".

When creating a new grant Opportunity, fill in this field with the previous grant's Opportunity record.

Is Grant Renewal Checkbox:

Add a checkbox field on the Opportunity object called "Is Grant Renewal".

Check this box for Opportunities that are renewals of previous grants.

Grant Tracking and Reporting:

This setup allows easy tracking of grant renewals and provides a straightforward way to report on grants and their renewals.

Use reports and dashboards to summarize and analyze grant data, including renewals.

By linking each renewal grant to the original grant Opportunity, you maintain a clear record of the grant history, making it easy to access previous grant information and analyze grant renewals.

"Grant Management Best Practices" from Salesforce Help: Grant Management

"Nonprofit Success Pack Grant Management" from Salesforce.org: NPSP Grant Management

To locate NPSP release information, two key places are:

Power of Us Hub: This is a community for Salesforce.org customers, where they can access release notes, documentation, and discussions about NPSP updates.

GitHub Cumulus Releases: This repository contains detailed release information, including new features, bug fixes, and enhancements for NPSP.

These sources provide comprehensive and up-to-date information on NPSP releases.

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.

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

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.

The error message "the data you are trying to access is unavailable" when running a mailing list report on a campaign using the NPSP Household Mailing List button likely indicates a permissions issue. Since the button works as expected for the system administrator, the issue is probably related to user permissions.

Apex Class Access (A): The most likely cause is that the user does not have access to the necessary Apex Class for Manage Households. Ensure that the user has the required permissions to access and execute this Apex Class.

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

When setting up the process for importing lists of Contacts into Salesforce Campaigns using the NPSP Data Import tool, it is essential to consider how Campaign Members are created and matched.

Key Considerations:

Automatic Campaign Member Creation (A):

The NPSP Data Import tool will automatically create Campaign Member records for the imported Contacts with the default Member Status. This helps streamline the process of adding members to campaigns.

Exact Name Matching (D):

Existing Campaigns in Salesforce are matched by exact Name. This means that the names in the CSV files must match the names of the Campaigns in Salesforce exactly for the import process to associate Contacts with the correct Campaigns.

Steps to Set Up:

Prepare CSV Files:

Ensure that the Campaign names in the CSV files exactly match the names of the Campaigns in Salesforce.

Include all necessary fields to map Contacts to Campaign Members.

Configure NPSP Data Import:

Navigate to NPSP Settings -> Data Import.

Ensure the settings align with the import requirements, including handling duplicates and respecting duplicate matching rules if enabled.

Perform Dry Run:

Use the NPSP Data Import Dry Run feature to validate the import configuration and ensure that the Campaign Member Status and other settings are correctly applied.

https://powerofus.force.com/s/article/NPSP-TDTM-Overview

Table-Driven Trigger Management (TDTM) in the Salesforce Nonprofit Success Pack (NPSP) allows developers and administrators to manage Apex triggers in a more flexible and controlled manner. The benefits include:

Control the order in which the code executes (B): TDTM enables you to specify the order of execution for various triggers, ensuring that triggers run in the desired sequence.

Disable specific pieces of code (D): TDTM allows you to disable individual triggers or handler classes without modifying the actual code, which is useful for debugging or temporarily disabling functionality.

To avoid manually entering information twice and ensure it appears on both the Opportunity record and the Payment record, follow these steps:

Create Payment Mappings in NPSP Settings:

Navigate to NPSP Settings.

Go to "Donations" and select "Payment Mappings".

Create mappings to ensure that relevant fields from the Opportunity record are automatically populated in the Payment record.

Create Custom Fields on the Payment Object:

Navigate to Setup.

In the Object Manager, select "Payment".

Click on "Fields & Relationships".

Create custom fields that correspond to the Opportunity fields you want to map.

Ensure the field types match those on the Opportunity object to facilitate accurate data transfer.

These steps automate the data transfer between Opportunities and Payments, reducing manual entry and ensuring consistency across records.

Salesforce NPSP Documentation: Payment Mappings

Salesforce Trailhead: Custom Fields

To streamline the import of donations made by nonprofit volunteers using NPSP Data Import features, the following steps are recommended:

Create a Batch and Map Opportunity Primary Contact on First and Last Name:

When creating a data import batch, you can map the Opportunity Primary Contact based on the First and Last Name. This ensures that the donation is linked to the correct contact in Salesforce.

Create a Batch and Match Contact on First and Last Name:

During the import process, create a batch and use the matching criteria based on the Contact's First and Last Name. This helps in accurately matching the donations to the existing contacts in Salesforce, reducing duplicate records and maintaining data integrity.

Steps to Implement:

Navigate to NPSP Data Import.

Create a new Batch.

Map the fields appropriately, ensuring the Opportunity Primary Contact and Contact matching criteria are based on First and Last Name.

Validate the mapping and run the batch to import the donation data.

These features help automate and streamline the data import process, ensuring accurate and efficient data management.

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

Create a Public Group:

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

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

Steps to Create a Public Group:

Go to Setup.

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

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

Create Sharing Rules:

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

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

Steps to Create Sharing Rules:

Go to Setup.

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

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

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

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

To track the high school a student attended and their college enrollment, the consultant should recommend using the NPSP Affiliations objects:

NPSP Affiliations: This object is designed to connect Contacts to Accounts representing institutions like high schools and colleges.

Status Field: Use the Status field within the Affiliations object to indicate if the student is currently enrolled or a former student.

This approach allows the nonprofit to maintain a detailed history of the student's educational journey and easily track changes in their enrollment status.

Before installing the Volunteers for Salesforce package, a consultant should:

Check that the nonprofit has the most recent NPSP release:

Ensure that the organization is running the latest version of the Nonprofit Success Pack (NPSP). This is crucial because newer releases might contain important updates and fixes that can impact the installation and functionality of Volunteers for Salesforce.

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

After using the Conversion Utility tool to convert an NPSP account model from One-to-One to Household, the consultant needs to manually select a Primary Contact for each Household Account. Here’s the detailed process:

Run the Conversion Utility Tool:

Navigate to NPSP Settings.

Under the "Bulk Data Processes" section, find and run the Conversion Utility tool to convert One-to-One Accounts to Household Accounts.

Review Converted Records:

Once the Conversion Utility tool runs successfully, review the newly created Household Accounts.

Each Household Account should have the associated Contacts correctly linked.

Select a Primary Contact for Each Household:

Go to each new Household Account.

Manually select a Primary Contact from the list of related Contacts. This step is crucial as the Conversion Utility does not automatically set the Primary Contact.

The Primary Contact field is used in many NPSP features and reports, so ensuring it is correctly set is important.

By performing this manual action, you ensure that the data integrity and functionality within NPSP are maintained after the conversion.

Salesforce NPSP Documentation: Convert One-to-One Accounts to Household Accounts

Salesforce Trailhead: Manage Households in NPSP

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.

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.

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.

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 track nested campaigns effectively, Salesforce Campaign Hierarchies can be utilized. Here are the steps to set this up:

Create Parent Campaign:

Create the top-level parent Campaign called "Friends of the Organization".

Create Sub-Campaigns:

Create sub-campaigns under the parent campaign for each hierarchical level: FY19, Capital Campaign, Annual Fund, Digital Donations, and Mobile.

Link each sub-campaign to its parent campaign using the Parent Campaign lookup field.

Configure Campaign Hierarchy Settings:

Ensure the Campaign Hierarchy settings are configured to allow for the desired depth of nested campaigns.

Track Campaign Performance:

Use Campaign Hierarchy reports to track the performance of each campaign within the hierarchy.

Analyze metrics such as total donations, engagement, and conversion rates at each level.

By creating a structured Campaign Hierarchy, the nonprofit can effectively track and manage complex campaign structures, gaining insights into performance at each level of the hierarchy.

"Campaign Hierarchies" from Salesforce Help: Campaign Hierarchies

"Managing Campaigns in NPSP" from Salesforce.org: Campaign Management

To keep nonprofit staff up to date on the latest Salesforce platform features and best practices, the following resources are recommended:

Trailhead:

Trailhead is Salesforce’s free, interactive learning platform. It offers modules, projects, and trails that cover new features, best practices, and hands-on activities to help users learn and apply Salesforce skills.

Regularly check Trailhead for new content related to Salesforce updates and best practices.

Power of Us Hub:

The Power of Us Hub is an online community specifically for Salesforce.org users, including nonprofits. It provides a wealth of resources, discussions, and updates about Nonprofit Cloud and related Salesforce features.

Join the Power of Us Hub to stay informed about new features, best practices, and upcoming releases.

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

Access NPSP Public Data Dictionary:

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

Navigate to the NPSP documentation section.

Search for the Field:

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

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

Verify Field Information:

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

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

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

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

Delete Access to Contacts:

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

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

Unique External ID:

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

Salesforce Nonprofit Success Pack Documentation

Salesforce Merge Contact Permissions Guide

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

To present active volunteer sites on a map that should be visible without logging in, the nonprofit can use Tableau Public. Here’s why:

Tableau Public:

Tableau Public is a free platform that allows users to create and share interactive data visualizations online.

It supports publishing maps and other visualizations that can be accessed publicly without requiring login credentials.

This tool is ideal for sharing information like volunteer site locations with a broad audience.

Tableau Public Documentation

Salesforce and Tableau Integration Guide

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.

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.

For maintaining an audit trail of metadata changes over time and developing, testing, and releasing projects independently, the recommended development model is:

Package Development: This model supports modular development, allowing developers to create, test, and deploy packages independently. It provides version control and a clear audit trail of changes, ensuring that metadata changes are tracked and managed efficiently.

Independent Projects: Package development allows multiple projects to be developed in parallel without interference, making it ideal for complex environments with multiple ongoing initiatives.

Package development provides the structure and control needed for managing metadata and development processes effectively.

When using the NPSP Data Importer to upload data that contains payments on existing opportunities, and matching donations to existing records, the following updates may occur:

A Payment Will Be Added to the Opportunity:

When a gift is successfully matched to an existing Opportunity, a Payment record is created and associated with the Opportunity.

This reflects the new donation and updates the financial records accordingly.

The Opportunity Amount Will Include the New Payment Amount:

The total amount on the Opportunity will be updated to reflect the sum of the original amount and the new payment amount.

This ensures that the Opportunity accurately represents the total donations received.

These updates help maintain accurate and up-to-date financial records within Salesforce, reflecting all contributions accurately.

Salesforce NPSP Documentation: NPSP Data Importer

Salesforce Trailhead: Manage Donations with NPSP

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

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

Navigate to NPSP Settings:

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

Access Donations Settings:

Under NPSP Settings, select "Donations".

Click on "Opportunity Contact Roles".

Configure Default Contact Role:

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

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

Verify and Save:

Ensure that the configuration is correct and save the changes.

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

Salesforce NPSP Documentation: Opportunity Contact Roles

Salesforce Trailhead: Manage Donations in NPSP

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

Organize Reports into Appropriate Folders:

Navigate to the Reports tab.

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

Move existing reports into these folders for better organization.

Run Health Check:

Navigate to Setup.

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

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

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

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

"Salesforce Health Check" from Salesforce Help: Health Check

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.

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

Apply for a New Salesforce Organization:

Create a new Salesforce instance without enabling Person Accounts.

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

Request a License Transfer:

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

Provide the necessary details and justification for the transfer.

Install NPSP in the New Org:

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

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

Migrate Data:

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

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

Ensure data integrity and mapping during the migration process.

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

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

"Managing Person Accounts" from Salesforce Help: Person Accounts

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.

To automatically add donors to the Capital Campaign when they contribute to the Capital Fund, the following steps should be taken:

Populate the Primary Campaign Source Field:

The Primary Campaign Source field on the Opportunity record links the donation to a specific Campaign.

This ensures that donations are tracked under the correct Campaign and allows for accurate reporting and analysis.

Enable Automatic Campaign Member Management:

NPSP (Nonprofit Success Pack) provides a feature for automatic campaign member management.

This feature automatically adds donors to Campaigns based on their donations, streamlining the process and reducing manual work.

To enable this, navigate to NPSP Settings -> Donations -> Automatic Campaign Member Management and activate the feature.

Steps to Implement:

Step 1: Ensure that the Primary Campaign Source field is populated on the Opportunity record whenever a donation is made to the Capital Fund.

Step 2: Enable the Automatic Campaign Member Management feature in NPSP settings to automate the addition of Campaign Members.

Benefits:

Efficiency: Reduces the need for manual updates, saving time and effort.

Accuracy: Ensures that all relevant donations are correctly attributed to the appropriate Campaign, improving reporting and donor management.

When encountering an issue while configuring Nonprofit Cloud Case Management, the consultant should first check Salesforce Help to see if it is a documented issue. Salesforce Help provides extensive documentation, release notes, and known issues, making it a reliable source for troubleshooting.

Steps to Check:

Salesforce Help:

Navigate to Salesforce Help & Training.

Search for the specific issue or error message.

Review any available documentation, known issues, and suggested resolutions.

Additional Resources:

If the issue is not documented in Salesforce Help, the consultant can also check the Trailblazer Community for discussions and solutions provided by other users.

To ensure a subset of org users can fully access the government-issued personal identification number stored in an encrypted field on Contact records, the consultant should enable the "View Encrypted Data" system permission on a Permission Set:

View Encrypted Data System Permission:

This permission allows users to view the full unmasked value of encrypted fields.

It is necessary for users who need to access sensitive data stored in encrypted fields.

Steps to Enable the Permission:

Create or update a Permission Set in Salesforce.

Enable the "View Encrypted Data" permission in the System Permissions section of the Permission Set.

Assign the Permission Set to the appropriate subset of users who require access to the encrypted data.

Security Considerations:

Ensure that only trusted and authorized users are granted this permission due to the sensitive nature of the data.

Regularly review and audit Permission Set assignments to maintain security and compliance.

By enabling the "View Encrypted Data" permission, the nonprofit ensures that authorized users can access sensitive data as needed for their roles.

To troubleshoot incorrect values in the NPSP calculated donation summary fields on Contact and Account records, the consultant should review the following:

Customizable Rollups:

Verify the settings and configuration of Customizable Rollups in NPSP. Incorrect configurations or mappings can lead to inaccurate summary values.

Ensure that the rollups are set up correctly to calculate totals based on the desired criteria.

Opportunity Stages:

Check the Opportunity stages to ensure they are correctly defined and assigned. Only certain stages (e.g., "Closed Won") should be included in donation summaries.

Misconfigured or incorrect stages can result in inaccurate summary calculations.

NPSP Health Check:

Run the NPSP Health Check to identify any potential configuration issues or data integrity problems.

The Health Check provides insights and recommendations to address common issues within NPSP.

Salesforce Nonprofit Success Pack Documentation on Customizable Rollups

Salesforce Opportunity Stages Configuration Guide

NPSP Health Check Documentation

The Power of Us Hub Solution Exchange is designed for nonprofit organizations using Salesforce to connect directly with other nonprofits that have similar business use cases. Here’s how to utilize this resource:

Access the Power of Us Hub:

Navigate to the Power of Us Hub (https://powerofus.force.com).

Log in using your Salesforce credentials.

Explore the Solution Exchange:

Go to the "Solution Exchange" section within the Hub.

Browse through various solutions, discussions, and best practices shared by other nonprofits.

Connect with Similar Nonprofits:

Use the search and filter features to find nonprofits with similar use cases.

Participate in discussions, ask questions, and share your experiences.

Utilize Shared Resources:

Access shared resources, templates, and configurations that have been successful for other organizations.

Apply relevant solutions and best practices to your own organization’s use case.

The Power of Us Hub Solution Exchange is a valuable resource for collaboration and learning from the experiences of other nonprofits using Salesforce.

"Power of Us Hub Overview" from Salesforce.org: Power of Us Hub

"Using the Solution Exchange" from Salesforce Help: Solution Exchange

https://powerofus.force.com/s/article/PMM-Overview

https://trailhead.salesforce.com/en/content/learn/modules/program-management-with-nonprofit-cloud/manage-nonprofit-programs-with-salesforce?trail_id=manage-programs-with-nonprofit-cloud

To meet the reporting requirements of a new grant that expects services to be segmented according to location, the nonprofit should use the Program Cohort object. The Program Cohort object allows tracking and reporting of services provided in specific locations, making it possible to generate detailed reports that meet funder requirements.

Steps:

Configure the Program Management Module to include the necessary fields for tracking service locations within the Program Cohort object.

Ensure that all relevant data is accurately entered into the Program Cohort records, including location details.

Create custom reports and dashboards that segment services based on the location data stored in the Program Cohort object.

Regularly review and update the data to ensure accurate and up-to-date reporting for the funder.

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.

A Salesforce-recommended governance structure for nonprofit organizations ensures the implementation runs smoothly and effectively. It typically includes the following elements:

Release Management: This ensures that changes are systematically planned, tested, and deployed. It involves managing how new features and updates are rolled out to avoid disruption and ensure smooth transitions.

Rules of Engagement: These define how different stakeholders will interact with the system and with each other. It includes protocols and guidelines for communication, decision-making, and responsibilities.

Center of Excellence (CoE): This is a dedicated team or a hub of experts that provides leadership, best practices, research, support, and training. A CoE helps ensure that the organization is leveraging Salesforce effectively and efficiently.

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

To categorize donors into Gold, Silver, and Bronze based on the total gift amount for the year, the NPSP Levels feature should be utilized. This feature allows the organization to automatically categorize donors based on specified criteria.

Define Levels in NPSP:

Navigate to NPSP Settings > Levels.

Create three new Levels: Gold, Silver, and Bronze.

For each Level, specify the range of the total gift amount for the year. For example:

Gold: $10,000 and above

Silver: $5,000 to $9,999

Bronze: $1,000 to $4,999

Configure Level Criteria:

Set the criteria for each Level to be based on the "Total Gifts This Year" field.

Ensure the system is tracking the total gifts correctly by verifying the Customizable Rollups settings.

Assign Levels to Donors:

The system will automatically evaluate donors and assign them to the appropriate Level based on their total giving for the year.

This categorization can be used in reports, dashboards, and donor segmentation for targeted communication and recognition.

To enhance the security of Salesforce usernames and passwords and prevent them from being compromised, setting up two-factor authentication (2FA) is the recommended approach. Here’s how to implement it:

Enable Two-Factor Authentication for the Org:

Navigate to Setup.

In the Quick Find box, type "Two-Factor Authentication" and select it.

Enable 2FA at the organization level.

Assign 2FA to User Profiles:

Go to the user profiles that require 2FA.

Under the profile settings, enable the requirement for two-factor authentication.

Configure 2FA Methods:

Allow users to register their preferred authentication method (e.g., Salesforce Authenticator app, SMS, email, or third-party authenticator apps).

Ensure users set up their 2FA methods through their personal settings.

User Training and Support:

Provide training materials and support to help users understand and set up 2FA.

Offer assistance for troubleshooting common issues during the setup process.

Monitor and Enforce:

Use Salesforce’s monitoring tools to ensure compliance with 2FA requirements.

Regularly review and update security policies to maintain a high level of security.

Implementing two-factor authentication significantly reduces the risk of account compromise by adding an extra layer of security beyond just usernames and passwords.

"Setting Up Two-Factor Authentication" from Salesforce Help: Two-Factor Authentication

"Salesforce Authenticator" from Salesforce Help: Salesforce Authenticator

Changes to Engagement Plan Templates in Salesforce only affect newly created Engagement Plans. Here’s why:

Template Changes Application:

When an Engagement Plan Template is modified, the changes are not retroactively applied to existing Engagement Plans. Only new plans created after the modification will reflect the changes.

Create New Engagement Plans:

For the development manager to see the changes, new Engagement Plans need to be created using the updated template. Existing plans will retain the configuration they had at the time of creation.

Communicate Changes:

Inform relevant stakeholders about this behavior to manage expectations and plan accordingly. Consider cloning existing Engagement Plans if updates are necessary, applying the new template configurations.

Review Documentation:

Refer to Salesforce documentation on Engagement Plans for detailed information on how templates and plan instances work.

To allow prospective volunteers to fill out their volunteer application online:

Set up the Volunteers for Salesforce Volunteer Signup Form: This form can be embedded on the nonprofit's website, allowing prospective volunteers to submit their information directly into Salesforce.

This approach leverages the existing Volunteers for Salesforce functionality, making it easy to capture and manage volunteer applications.

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

Partial Data Sandbox:

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

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

Navigate to NPSP Settings:

Go to Setup.

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

Configure Soft Credits:

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

Ensure that soft credits are enabled for Accounts and Contacts.

Add Soft Credits on Opportunities:

When entering a donation, go to the Opportunity record.

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

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

Track and Report:

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

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

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

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

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.

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

To search for volunteers with specific skills and availability using Volunteers for Salesforce:

Use the Find Volunteers Tab:

Navigate to the Volunteers for Salesforce application within Salesforce.

Click on the "Find Volunteers" tab.

Fill in the Volunteer Criteria:

In the search form, enter the desired values for Volunteer Status, Volunteer Availability, and Volunteer Skills.

For this scenario, enter "Landscaping" in the Volunteer Skills field and specify the desired availability timeframe in the Volunteer Availability field.

Execute the Search:

Click on the "Search" button to find volunteers that match the specified criteria.

Select Volunteers:

Review the list of volunteers returned by the search.

Select the volunteers that are available at the given time and have the required landscaping skills.

This method ensures that the volunteer manager can efficiently find and assign volunteers to shifts based on their skills and availability.

(wrong),b(wrong), a(if d is wrong then a is also wrong),So Option C

https://help.salesforce.com/s/articleView?id=000358792 &type=1

When using Advanced Mapping for data imports in Salesforce Nonprofit Success Pack (NPSP), it is essential to understand that the target objects must be NPSP objects. Advanced Mapping is designed specifically to enhance the data import capabilities within NPSP by allowing detailed mapping configurations that align with NPSP's data model.

Key Considerations:

NPSP Specific: Advanced Mapping is tailored for NPSP objects, ensuring that data is correctly mapped and imported into the NPSP-specific fields and objects.

Enhanced Data Import: This feature allows for more precise data import, reducing the likelihood of errors and ensuring data integrity.

Steps for Using Advanced Mapping:

Navigate to NPSP Settings:

Go to NPSP Settings -> Data Import -> Advanced Mapping.

Configure Mapping:

Set up mappings between source data fields and target NPSP object fields.

Ensure that the target fields align with the NPSP data model requirements.

Perform Data Import:

Use the NPSP Data Importer to upload and import the data using the configured mappings.

To transfer data from Salesforce to an accounting system using Accounting Subledger, nonprofits can use several methods. Here are three possible methods:

Integrate Salesforce with the Accounting System Using Middleware:

Middleware can act as a bridge between Salesforce and the accounting system, facilitating data transfer.

Tools like MuleSoft, Jitterbit, or Dell Boomi can be used to create integrations that sync data between Salesforce and the accounting system.

This method ensures real-time or near-real-time data synchronization, reducing manual data handling.

Export Data via Salesforce Reports to Upload to the Accounting System:

Salesforce allows the creation of detailed reports which can be exported in various formats (e.g., CSV, Excel).

These reports can be manually uploaded to the accounting system.

This method is suitable for organizations with fewer transactions or where real-time integration is not critical.

Develop a Custom Integration Solution:

For organizations with specific needs that are not met by standard middleware solutions, a custom integration can be developed.

This involves using Salesforce APIs (REST or SOAP) to programmatically extract data from Salesforce and load it into the accounting system.

Custom integrations provide flexibility but require more technical expertise and maintenance.

Salesforce Integration Patterns and Best Practices: Salesforce Integration Guide.

Salesforce Reporting and Exporting: Salesforce Reporting.

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

Activate English (UK):

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

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

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

Salesforce Language Settings Documentation

Salesforce Localization and Translation Guide

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

Create GAU Records:

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

Create a new GAU record for each designated fund.

Link Donations to GAUs:

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

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

Set Up GAU Allocation:

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

Click "New" to create a new GAU Allocation.

Select the appropriate GAU and enter the allocation amount.

Reporting on GAUs:

Create reports to track donations by GAU.

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

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

Salesforce NPSP Documentation: General Accounting Units (GAUs)

Salesforce Trailhead: Manage General Accounting Units (GAUs)

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

https://trailhead.salesforce.com/content/learn/modules/program-management-with-nonprofit-cloud/manage-nonprofit-programs-with-salesforce

To track each program and the status of youth enrolled in the program using the Program Management Module (PMM) in Salesforce, the consultant should use the "Programs" and "Program Engagements" objects.

Key Features:

Programs: This object represents the various programs offered by the nonprofit. Each program can have multiple engagements and activities associated with it.

Program Engagements: This object tracks the involvement of individuals (youth in this case) in specific programs. It allows the nonprofit to monitor the status and progress of each participant within the program.

Steps to Implement:

Set Up Programs:

Navigate to the Programs tab.

Create records for each after-school program offered by the nonprofit.

Track Engagements:

Navigate to the Program Engagements tab.

Create records for each youth enrolled in the programs, linking them to the appropriate program and tracking their status.

To automatically generate an Opportunity whenever a Lead is converted in NPSP, the consultant should enable the "Create an Opportunity on Lead Convert" option in the NPSP Settings. This option ensures that an Opportunity is automatically created as part of the lead conversion process.

Navigate to NPSP Settings:

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

Enable Lead Conversion Setting:

In NPSP Settings, expand the "Leads" section.

Find the "Lead Conversion" settings.

Check the box for "Create an Opportunity on Lead Convert".

Save the settings.

This configuration streamlines the process, ensuring that Opportunities are consistently created during lead conversion, without requiring additional custom code or third-party applications.

https://powerofus.force.com/s/article/NPSP-Configure-Gift-Entry

Gift Entry Templates in NPSP allow for the configuration of different batch data input settings for various types of donations. This feature ensures consistency and efficiency in processing different donation batches.

Steps:

Access the Gift Entry Templates in NPSP.

Create a new template for each type of donation batch that needs to be processed.

Configure the fields and layout for each template to match the specific data requirements of each donation type.

Save and publish the templates.

Use the templates when processing donation batches to ensure consistent data entry and processing.

To ensure full compliance with Salesforce best practices for data security, the consultant should use Salesforce Health Check. Here’s why:

Salesforce Health Check:

This tool provides a comprehensive security assessment of your Salesforce org by measuring its settings against the Salesforce recommended baseline.

It evaluates critical security settings such as password policies, session settings, and other security configurations.

Health Check provides a score and recommendations to improve the overall security posture of the org, making it a crucial tool for maintaining data security compliance.

Salesforce Health Check Documentation

Salesforce Security Best Practices Guide

Before upgrading from version 2 to version 3 of NPSP, the consultant should:

Run NPSP Health Check: This tool identifies potential issues in the current NPSP configuration, including deprecated fields, custom objects, and other configurations that might cause problems during the upgrade.

Running NPSP Health Check ensures that the upgrade process goes smoothly by addressing any issues beforehand.

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.

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

Regular Updates:

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

Automatic Updates:

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

Release Notes:

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

Testing and Sandbox Environments:

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

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

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

To determine if an acknowledgment letter was sent for a donation, the best approach is to check the "Acknowledgement Status" picklist value on the Opportunity object. Here's how you can do it:

Navigate to the Opportunity Object:

Go to the App Launcher and find Opportunities.

Add the Acknowledgement Status Field:

Ensure that the "Acknowledgement Status" field is included in the Opportunity page layout.

Navigate to Setup.

In the Object Manager, select Opportunity.

Go to Page Layouts and add the "Acknowledgement Status" field to the relevant layout if it is not already there.

Review the Acknowledgement Status:

Open the Opportunity record for the donation in question.

Look for the "Acknowledgement Status" field to see if it indicates that the acknowledgment letter has been sent.

Automate Tracking (Optional):

Use workflows or Process Builder to update the "Acknowledgement Status" automatically when certain conditions are met, such as when a task related to sending an acknowledgment letter is marked complete.

Salesforce Nonprofit Success Pack (NPSP) Documentation: Managing Acknowledgments

Salesforce Trailhead: Opportunities and Donations

To ensure a case manager can assign a group of services to a client using the Case Plan Wizard, the following configuration is required:

Program with Goals and Action Item Templates:

A program in Salesforce should be configured with defined goals and action item templates.

Goals represent the objectives for the client, and action item templates provide the specific tasks or services that need to be delivered.

Steps to Configure:

Navigate to the Program Management Module in Salesforce.

Create or update the program to include the relevant goals that outline the objectives for the clients.

Define action item templates that detail the services or tasks that will help achieve these goals.

Using the Case Plan Wizard:

The Case Plan Wizard utilizes these predefined goals and action item templates to create a structured case plan for the client.

The case manager can select the appropriate goals and action items from the templates during the case plan creation process.

By having a program with goals and action item templates configured, the nonprofit ensures that case managers can efficiently assign and manage services for their clients.

When the consultant encounters API call limit errors after switching the integration from a sandbox to a production environment, the likely explanation is:

Different API Call Limits for Sandbox and Production Environments:

Salesforce environments have different API call limits based on the type of environment and the organization's Salesforce edition. Sandbox environments often have higher API call limits for testing purposes, while production environments have stricter limits to ensure performance and reliability.

For a large nonprofit that functions like a for-profit corporation and tracks funding exclusively from corporations, the Standard Account Model without NPSP is the most suitable choice. This model allows the nonprofit to manage Leads and track its Opportunity pipeline effectively, focusing on corporate accounts.

Benefits of the Standard Account Model:

Simplicity: The Standard Account Model is straightforward and designed for organizations that do not need the additional features provided by NPSP.

Corporate Focus: It is well-suited for managing corporate accounts and opportunities without the additional complexities of individual or household account models.

Steps to Implement:

Set Up Standard Account Model:

Use the default Salesforce setup for Accounts, Contacts, Leads, and Opportunities.

Customize as Needed:

Customize the standard objects and fields to align with the nonprofit’s specific requirements for tracking corporate funding.

The Program Management Module (PMM) in Salesforce is designed to help nonprofits manage their programs and services, including tracking participation in courses and training. PMM provides the necessary tools and features to capture and report on the various activities and outcomes associated with the programs run by the nonprofit.

Key Features:

Service Delivery Tracking: PMM allows for detailed tracking of services provided, including courses and training sessions.

Customizable Program Management: Nonprofits can configure PMM to meet their specific needs for managing programs and tracking participant engagement.

Steps to Implement PMM:

Install PMM:

Go to the Salesforce AppExchange and install the Program Management Module.

Set Up Programs and Services:

Define programs and related services within PMM to reflect the courses and training offerings.

Track Participation:

Use the PMM features to log and manage participant data, track attendance, and monitor outcomes.

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

Criteria-based Sharing:

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

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

Salesforce Sharing and Visibility Guide

Salesforce Criteria-based Sharing Rules Documentation

For a nonprofit offering courses that grant teachers credit toward maintaining their teaching certification, the Program Management Module (PMM) is the best solution to track course completions and credits awarded. PMM allows the nonprofit to manage program enrollments, track progress, and report on outcomes effectively.

Steps:

Set up the Program Management Module to include the specific courses offered and the credits awarded for each course.

Create Program Engagement records for each teacher enrolling in the annual cohort, linking them to the relevant course modules.

Track the completion of course modules and update the credits awarded to each teacher within their Program Engagement records.

Use custom reports and dashboards to monitor progress, track completions, and generate reports on credits awarded to teachers.

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

Navigate to the Contact Record:

Go to the Contacts tab in Salesforce.

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

Select the Deceased Field:

Locate the "Deceased" checkbox on the contact record.

Check the box to mark the contact as deceased.

Additional Actions:

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

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

Implications of Marking a Contact as Deceased:

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

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

Salesforce NPSP Documentation: Managing Contact Records

Salesforce Trailhead: Nonprofit Success Pack (NPSP) Basics

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