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

The relationship between the Program Management Module (PMM) and Nonprofit Cloud Case Management (NCCM) is one of "broad service tracking" meeting "individualized care." While PMM provides the framework for what services an organization offers, NCCM provides the specific tools for caseworkers to manage a participant's journey.

Two objects serve as the primary "connectors" between these two modules:

Program (C): In PMM, the Program object defines the high-level initiative (e.g., "Housing First"). In Case Management, the Case Plan is often directly linked to a Program. When a caseworker creates a Case Plan for a client, they select the Program that the plan supports. This ensures that the individual's goals and action items are contextualized within the organization's broader mission.

Service Delivery (A): This is the functional link. PMM uses Service Deliveries to track when a service was provided. In NCCM, when a caseworker fulfills an Action Item that involves providing a specific service (like a "Counseling Session"), the system can automatically generate a Service Delivery record. This allows the organization to see how specific case-managed activities contribute to overall program outputs.

Why other options are incorrect:

Case (Option B): While NCCM uses the standard Salesforce Case object, it is a base platform object. The specific PMM objects are designed to link to the program-centric logic, not just the generic case container.

Client Alert (Option D): This is a specific feature of Case Management used to flag sensitive information (e.g., "Allergy" or "Safety Risk") on a contact record, but it does not have a direct architectural relationship with the PMM objects like Programs or Service Deliveries do.

Salesforce Shield Platform Encryption provides high-level security, but it has significant "functional trade-offs" because the system cannot "read" encrypted data in the same way it reads plain text for certain automated processes.

Three Critical NPSP Considerations:

Soft Credit Rollup Failure (C): NPSP's Customizable Rollups often use the Role Name on the Partial Soft Credit object to determine how to aggregate credits. Because encryption prevents the database from performing "Group By" or "Where" queries on that field effectively, the nightly rollup jobs will fail to process those credits.

Merge Contacts Failure (D): The NPSP Contact Merge tool relies on identifying and comparing names. If the Contact Name is encrypted, the SOSL/SOQL queries used by the "Merge" button cannot properly index or find the records, rendering the specialized NPSP merge interface unusable.

Data Import Matching (E): The NPSP Data Importer relies heavily on "Matching Rules." If you are trying to match a legacy donor ID or a custom unique ID that has been encrypted, the system cannot perform the "Exact Match" check needed to prevent duplicates during the import process.

Why other options are incorrect:

Option A: Standard address fields on Account/Contact can be encrypted with Shield, so this is not a limitation.

Option B: The Data Import object does not support "all fields" for encryption; like most objects, it has specific supported field types and limits.

Volunteers for Salesforce (V4S) is a powerful application, but it is "resource-heavy." One of its primary functions is to roll up volunteer hours from the Volunteer Hours object to the Volunteer Job, the Volunteer Shift, and the Contact record.

The Limit Consideration:

Roll-up Summary Limits: Salesforce has a hard limit on the number of roll-up summary fields allowed per object (typically 40).

Impact of V4S: When you install V4S, it automatically attempts to create several roll-up summary fields on the Contact and other objects. If the nonprofit has already used many custom roll-up fields for fundraising or programs, the V4S installation will fail because it will exceed the object's field limit.

Best Practice: A consultant should always audit the current field usage on the Contact and Account objects before installing V4S to ensure there is "headroom" for the new package's fields.

Why other options are incorrect:

Option B: V4S is independent of PMM.

Option C: While being on a recent NPSP is good, V4S can actually run on a standard Salesforce org without NPSP entirely.

Option D: V4S is a free, open-source package; there are no licenses to "apply" for.

The calculation of giving totals (e.g., Lifetime Giving, Last Gift Date) in Nonprofit Cloud is a major departure from the older NPSP. In NPC, these summaries are not updated by real-time code or flows; they are managed by the Data Processing Engine (DPE).

Because DPE is a batch-based processing tool, the data is only as "up to date" as the last successful run of the engine. If a user reports that the data is stale, the issue is almost certainly a failure in the background job rather than a UI or security issue.

Step-by-Step Troubleshooting for the Consultant:

Monitor Workflow Services: This is the "Command Center" for all Industry Cloud background processes. The consultant should search for this in the Setup menu.

Locate the Job: Within the monitor, find the entry for the specific Data Processing Engine definition responsible for Fundraising summaries (often titled something like "Calculate Donor Gift Summary").

Check the Status: Look for runs marked as "Failed" or "Completed with Errors."

Analyze Error Logs: Clicking into a failed run will reveal the specific technical reason for the failure (e.g., "System Limit Exceeded," "Data Mapping Error," or "Inactive Picklist Value").

Rerun: Once the underlying data or configuration issue is resolved, the consultant can manually trigger the DPE run from this screen to bring the summaries up to date immediately.

Option A is incorrect because there is no standard record-triggered flow for these rollups in NPC. Option B is a valid check for visibility, but the question specifically states the data is "out of date" (meaning it exists but is wrong), suggesting a calculation/sync failure.

When delegating access to Gift Entry in NPSP, a consultant must follow the "Principle of Least Privilege." This means granting enough access to do the job without exposing the entire system.

Three Essential Permissions:

Object and Field Access (B): Users must be able to Create and Edit the records involved in the gift entry process. This includes the NPSP Data Import (the staging object), Accounts, Contacts, Opportunities, and GAU Allocations. Note that Delete (Option E) is usually not a "necessary level of access" for a standard entry clerk; they only need to enter and modify records.

Tab Visibility (C): A user cannot use a feature if they cannot find it. The Gift Entry tab must be set to "Default On" or "Visible" within the permission set so the users can access the interface.

Visualforce Page Access (D): NPSP Gift Entry is built using a custom interface. To run this interface, the user's profile or permission set must explicitly have access to the underlying Visualforce pages that power the tool, specifically those related to the Batch Object Importer (BOI). Without access to BOI_BatchOverride and BOI_DataImport, the user will see an "insufficient privileges" error when they try to open the Gift Entry tool.

Option A is incorrect because View All Data is a powerful administrative permission that bypasses all security and is never appropriate for a standard data entry role.

In the Nonprofit Cloud (NPC) Fundraising model, tracking donor intent—where the money is "designated" to go—is a core requirement for financial transparency. It is important to distinguish between the "Fund" and the "Allocation."

Gift Designation (The Fund): This object represents the master fund or program area (e.g., "Clean Water Initiative"). It is a static record that holds rollup data for that specific fund.

Gift Transaction Designation (The Allocation): This is the junction object that records the donor's specific intent for a particular gift. When a consultant identifies that a donation needs to be split across multiple programs, they create multiple Gift Transaction Designation records linked to a single Gift Transaction. This object stores the specific amount or percentage of that transaction that should be credited to a particular program.

Workflow During Solicitation:

During the solicitation of an Opportunity, the consultant or gift officer captures the donor’s intent. Even if the money has not yet arrived, the data model for NPC Fundraising (v59 and higher) anticipates that this intent will eventually live on the Gift Transaction Designation record. When an Opportunity is "Won" and converted into a Gift Transaction, the system uses the metadata captured during solicitation to populate these designation records.

Why other options are incorrect:

Gift Default Designation (Option C): These are used at the Campaign or Org-wide level to define where unrestricted or "unmarked" gifts should go by default. They are templates for inheritance rather than the record that tracks a specific donor's intent for a specific solicitation.

Gift Designation (Option B): As mentioned, this is the master definition of the fund, not the record of a specific allocation instance.

Accounting Subledger (ASL) is designed to bridge the gap between Fundraising (Salesforce) and Finance (General Ledger). It uses a "Stage to State" mapping to determine when a fundraising record is ready to be processed as an accounting transaction.

In the Starter Edition of ASL, the system looks for specific "States" to trigger record creation:

Committed: This state indicates that a donor has made a formal promise to give (a Pledge), but the cash has not necessarily been received yet. In accounting terms, this creates an Accounts Receivable entry.

Finalized: This state usually indicates that the cash has been received and the transaction is closed.

The Solution for Pledges:

To meet the requirement of exporting pledges "when they are booked," the consultant must map the organization's "Pledged" Opportunity stage to the Committed Accounting State.

Step-by-Step Configuration:

Navigate to Accounting Subledger Settings.

Go to Stage to State Mapping.

Locate the Pledged stage (or whatever custom stage the nonprofit uses for booked pledges).

Map this stage to Committed.

Save the settings and run the subledger job.

Once this mapping is in place, as soon as an Opportunity is moved to the "Pledged" stage, ASL will generate Ledger Entries that reflect the revenue as "Committed." These entries can then be exported to the external financial system to record the expected income on the organization's books.

To organize data across different departments and objects using "focus areas" (e.g., "Youth Literacy," "Veterans Affairs," or "Sustainability"), a consultant should implement Interest Tags.

Interest Tags (built on the Salesforce Industry's Tagging framework) provide a flexible, "horizontal" way to categorize records regardless of their object type.

How to Implement Focus Areas with Interest Tags:

Define Tag Categories: The consultant creates a Tag Category called "Focus Areas."

Create Tags: Within that category, the consultant creates individual Interest Tags (e.g., "Environment," "Health," "Education").

Cross-Object Application: Unlike a standard picklist which is tied to one object, Interest Tags can be added to almost any object in the Nonprofit Cloud. A consultant adds the "Interest Tags" component to:

Programs: To show the focus of the service.

Person Accounts: To show the interests of a donor or participant.

Individual Applications: To show the focus of a grant request.

Unified Reporting: Because all these records share the same tags, the organization can easily run a report to see "Everything related to Youth Literacy"—including the donors interested in it, the programs delivering it, and the grants funding it.

Why other options are incorrect:

Data Pipelines (Option A): This is a tool for high-volume data transformation and aggregation, not for qualitative categorization.

Compliant Data Sharing (Option C): This is a security feature for record-level visibility, not a data organization or tagging tool. Interest Tags are the architecturally correct choice for cross-departmental "Focus Area" tracking.