(Jun-2026) Get professional help from our NP-Con-102 Dumps PDF
Give You Free Regular Updates on NP-Con-102 Exam Questions
NEW QUESTION # 33
A nonprofit wants to deploy Nonprofit Cloud Case Management into its production org. Which two prerequisites should be considered prior to installing Case Management? (Choose 2)
- A. Install NPSP
- B. Enable My Domain
- C. Ensure appropriate licenses are provisioned
- D. Ensure Volunteers for Salesforce is properly configured
Answer: B,C
Explanation:
Nonprofit Cloud Case Management (NCCM) is a managed package that extends the capabilities of Salesforce for human services. Like many high-end Salesforce industry solutions, it has specific technical and legal prerequisites that must be met before the installation can succeed.
Prerequisite 1: Provisioned Licenses (A):
NCCM is not a free, open-source tool like NPSP. It is a paid product that requires specific Permission Set Licenses (PSLs) to be provisioned in the org. A consultant must verify that the organization has purchased the necessary licenses through their Salesforce Account Executive. Without these licenses appearing in the
"Company Information" section of Setup, the managed package will not function, and users will not be able to access the custom Case Management objects like Goals, Action Items, or Case Plans.
Prerequisite 2: My Domain (C):
NCCM relies heavily on modern Lightning components and OmniStudio features to power its interactive interfaces (such as the Case Plan Wizard). Salesforce requires My Domain to be enabled and deployed in any org that uses custom Lightning components. My Domain adds a unique prefix to the Salesforce URL (e.g.,
https://my-nonprofit.my.salesforce.com), which is necessary for the secure rendering of these components.
Why other options are incorrect:
* Volunteers for Salesforce (Option B): This is a completely separate application for managing volunteer shifts and is not required for Case Management to function.
* Install NPSP (Option D): While NCCM is often used alongside NPSP, the modern Nonprofit Cloud Case Management package can technically run on a standard Salesforce platform without NPSP, provided the necessary licenses are in place.
NEW QUESTION # 34
A nonprofit organization wants to enter both one-off gifts and batch gifts in Nonprofit Cloud for Fundraising.
What Nonprofit Cloud features should the organization use?
- A. Gift Commitment Schedule and Gift Batches
- B. Gift Entry and Gift Batches
- C. Gift Entry and Data Import Wizard
Answer: B
Explanation:
In the Nonprofit Cloud (NPC) Fundraising module, the process of recording incoming revenue is managed through a modernized interface designed for high-speed data entry and accuracy. The two primary features used for this purpose are Gift Entry and Gift Batches.
1. Gift Entry (One-off Gifts):
The Gift Entry feature is a specialized Lightning interface (often powered by a Screen Flow) that allows a user to record a single donation quickly. It provides a "guided" experience where the user can search for a donor (Person Account), enter the amount, select the payment method, and designate the gift to a specific fund. It is optimized for "real-time" entry, such as when a donor calls in a gift over the phone.
2. Gift Batches (Batch Gifts):
When a nonprofit receives a large stack of checks in the mail (e.g., after a year-end appeal), they use Gift Batches. A Gift Batch is a container that allows the data entry clerk to process multiple transactions as a single unit.
* Control Totals: The clerk enters the total number of checks and the total dollar amount expected in the batch.
* Data Grid: The batch interface provides a spreadsheet-like grid for rapid-fire entry.
* Validation: Before the batch is "processed" or "committed," the system ensures that the individual gifts match the control totals, reducing the risk of clerical error.
* Post-Processing: Once the batch is committed, the system automatically creates individual Gift Transaction records and updates the donor's summary history.
Why other options are incorrect:
* Option B: While the Data Import Wizard can be used for bulk data migration, it is not an "Entry" feature for daily fundraising operations; it lacks the specific gift-matching and batch-control logic of NPC.
* Option C: Gift Commitment Schedules are used for automated recurring gifts, not for the manual entry of physical checks or one-off donations received through the mail.
NEW QUESTION # 35
A nonprofit organization is starting a new program that connects high school youths to college mentors. The organization wants to track this specific relationship in Nonprofit Cloud. How should the organization accomplish this goal?
- A. Create a new Party Role Relationship that has the Relationship Object Name field set to Contact Contact Relationship.
- B. Create a new Party Role Relationship that has the Relationship Object Name field set to Account Account Relationship.
- C. Create new picklist values for the Role field on the Person Account object.
Answer: A
Explanation:
In Nonprofit Cloud (NPC), individual constituents (like students and mentors) are modeled as Person Accounts. To track relationships between these individuals, Salesforce utilizes the Party Relationship Model
.
When a consultant needs to define a new type of connection-such as "Mentor" to "Student"-they must configure the Party Role Relationship object. This object defines the metadata for how two parties interact.
Step-by-Step Configuration:
* Navigate to Party Role Relationships: The consultant creates a new record in this object.
* Define Roles: You specify the roles involved, such as "Mentor" and "Mentee."
* Select the Relationship Object: This is the most critical step. Since the relationship is between two individual people (modeled as Person Accounts), the consultant must set the Relationship Object Name field to Contact Contact Relationship.
* Note: Even though the records are technically Person Accounts, NPC uses the ContactContactRelation object for person-to-person ties.
* Inverse Relationships: The consultant also defines the inverse role (e.g., if Person A is the Mentor of Person B, then Person B is the Mentee of Person A) to ensure the relationship is visible and logical from both records.
Why Option B is incorrect: Account Account Relationship is used for connections between two Business Accounts (e.g., a "Parent Company" and its "Subsidiary") or between a Person Account and a Business Account (e.g., an "Employee" and their "Employer"). For a mentor-student program where both parties are individual people, Contact Contact Relationship is the architecturally correct choice for the Party Role Relationship configuration.
NEW QUESTION # 36
A nonprofit is migrating from a legacy donor management database. The database has donor contact information, donation history, and payment information. How should the consultant load the data from the database using a single file to create the related records?
- A. Workbench
- B. Data Import Wizard
- C. Data Loader
- D. NPSP Data Importer
Answer: D
Explanation:
When migrating data into the Nonprofit Success Pack (NPSP), the most efficient and robust tool is the NPSP Data Importer. This tool was specifically built to handle the "multi-object" nature of nonprofit data in a single pass.
Why NPSP Data Importer is the Correct Choice:
* Single File Processing: Standard Salesforce tools like Data Loader or the Data Import Wizard usually require separate files and separate "upserts" for each object. You would have to import Accounts, then export the IDs, then import Contacts, then export those IDs, then import Opportunities.
* Complex Logic in One Row: The NPSP Data Importer allows you to put the Contact Name, the Household address, and the Donation Amount on the same row of a CSV file.
* Automatic Relationship Management: When you process the file, the Importer automatically:
* Creates or finds the Contact.
* Automatically creates the Household Account.
* Creates the Opportunity (Donation) and links it to the Account.
* Creates the Payment record (if payment info is included).
* Handles GAU Allocations and Campaign Memberships.
* Dry Run Capability: It includes a "Dry Run" feature that validates the data and checks for duplicates before any actual records are created, which is vital for a clean migration.
While Workbench and Data Loader are powerful technical tools, they lack the specific NPSP business logic that makes the NPSP Data Importer the fastest and safest way to move a legacy database into Salesforce using a single flat file.
NEW QUESTION # 37
A nonprofit on Unlimited Edition uses direct mail extensively as a fundraising channel. The nonprofit wants to automate the search for duplicate contact records. What should the consultant recommend implementing?
- A. Matching Rules
- B. Duplicate Jobs
- C. Duplicate Rules
- D. Scheduled Apex Jobs
Answer: B
Explanation:
While Duplicate Rules and Matching Rules are essential for preventing new duplicates from being created, they do not help with a database that already contains existing duplicates (which is common after large direct mail imports).12 The Solution for "Auto13mating the Search":
On Unlimited Edition, Salesforce provides a feature called Duplicate Jobs.
* Scanning the Database: Unlike rules that fire during a save, a Duplicate Job runs a scan across the entire existing database (or a specific segment) to find existing duplicate records based on your Matching Rules.
* Reporting: Once the job completes, it generates a list of "Duplicate Record Sets." This allows the nonprofit's data integrity team to review and merge records in bulk.
* Use Case: For a direct mail organization, running a Duplicate Job before a large mailing ensures they aren't wasting money by sending two identical letters to the same household.
Why other options are incorrect:
* Duplicate/Matching Rules (Options A & C): These act as "gatekeepers" during data entry. They find duplicates only when a record is created or edited; they do not proactively "search" the existing database.
* Scheduled Apex (Option D): This is a custom coding solution. A consultant should always recommend native, declarative features like Duplicate Jobs before suggesting custom code.
NEW QUESTION # 38
The development director wants all users to only see Engagement Plans on Opportunity records for donations with an Amount greater than 10,000. How should this be accomplished?
- A. Add the Related List - Single Lightning component to the Opportunity Lightning pa13ge. Add a component visibility filter to display the Engagement Plan when the Opportunity Amount field is greater than 10,000.
- B. Create a tab and associate the Engagement Plan object to the tab. Add the Related List - Single Lightning component and set it to Engagement Plans. Give read access for the Engagement Plan object to all profiles.8
- C. Add the Related Lists component to the Opportunity Lightning page. Set the component visibility filter to ensure the Opportunity Amount field is greater than 10,000. Assign the page to the development director's profile.
- D. Create a custom Lightning component that dis9plays all Engagement Plans. Add the component to the Opportunity Lightning Page. Assign the Lightning Page as the Org Default and Activate it.101112
Answer: A
Explanation:
To meet this requirement, a consultant should leverage Dynamic Lightning Pages, specifically using Component Visibility Filters. This allows for a declarative solution that does not require multiple page layouts or custom code.
Step-by-Step Implementation:
* Edit the Page: Navigate to an Opportunity record and select Edit Page from the Setup (gear) icon to open the Lightning App Builder.
* Add the Component: Drag the Related List - Single component onto the page layout.
* Configure the Component: In the component properties sidebar, set the Related List to "Engagement Plans."
* Set Visibility Filter: Scroll down to the Set Component Visibility section and click + Add Filter.
* Define Criteria: * Field: Amount
* Operator: Greater Than
* Value: 10,000
* Save and Activate: Save the page. When "All Users" (per the requirement) view an Opportunity, the Engagement Plan related list will simply be invisible if the amount is $10,000 or less. If it is $10,001 or more, the component will appear.
Why other options are incorrect:
* Option A: Assigning the page only to the development director's profile violates the requirement that
"all users" should see it when the criteria is met.
* Option B: This is an overly complex and disjointed user experience that doesn't actually filter the view based on the specific Opportunity's amount.
* Option C: A custom component is unnecessary "Technical Debt" since standard functionality meets the requirement perfectly.
NEW QUESTION # 39
A user has been assigned the System Administrator Profile in Nonprofit Cloud. The user discovers that they cannot see any Nonprofit Cloud for Fundraising objects. What is a possible cause of this issue?
- A. The Sharing Rules are missing for the Fundraising objects.
- B. The custom Tabs have not been created for the Fundraising objects.
- C. The Permission Set License is unassigned.
Answer: C
Explanation:
One of the most common configuration hurdles in Nonprofit Cloud is understanding the "Two-Key" access model. Unlike standard Sales or Service Cloud, where a Profile can grant access to almost any object, Industry Clouds (like NPC) require a Permission Set License (PSL) to be assigned before the objects even become "visible" or "available" in the system's schema for that user.
The "Two-Key" Access Model:
* The First Key (Permission Set License): The PSL "unlocks" the feature set at the organization level for a specific user. For Fundraising, the user must be assigned the Nonprofit Cloud Fundraising PSL.
Without this, the Fundraising objects (like Gift Transaction) literally do not exist from that user's perspective, even if they are a System Administrator.
* The Second Key (Permission Set): Once the license is assigned, the user then needs a Permission Set (e.g., "Fundraising Access") to grant the actual CRUD (Create, Read, Update, Delete) permissions.
Step-by-Step Resolution for a Consultant:
* Navigate to Setup > Users.
* Open the user record for the System Administrator.
* Scroll to the Permission Set License Assignments related list and click Edit Assignments.
* Locate and check the box for Nonprofit Cloud Fundraising (and any other relevant industry licenses like Nonprofit Cloud Grantmaking).
* Once the PSL is saved, the Admin will then be able to assign themselves the necessary Permission Sets to see and manage the Fundraising objects.
Option A is incorrect because Sharing Rules control which records you see, not whether the object itself is visible. Option B is incorrect because tabs are easily accessible via the App Launcher; if the objects are missing from the "All Objects" list, it is a licensing and permissioning issue, not a tab configuration issue.
NEW QUESTION # 40
A nonprofit organization uses Nonprofit Cloud and wants to ensure that members of the fundraising department cannot access the program department's Interaction Summaries. What should the organization use to accomplish this goal?
- A. Permission Sets
- B. Compliant Data Sharing
- C. Session Security Levels
Answer: B
Explanation:
In many nonprofits, "Interaction Summaries" (meeting notes) contain highly sensitive information. A caseworker's notes on a victim of domestic violence must be kept strictly confidential from a fundraiser who might be looking at the same constituent record for a donation appeal.
To solve this challenge, Nonprofit Cloud utilizes Compliant Data Sharing (CDS).
How CDS Secures Interaction Summaries:
* Record-Level Restriction: By default, Interaction Summaries can be set to "Private" in the Organization-Wide Defaults (OWD).
* Role-Based Access: Compliant Data Sharing allows the organization to grant access based on the user's specific role in relation to that record. For example, only the "Assigned Caseworker" and
"Program Supervisor" roles are granted "Read" access to the summary.
* Departmental Silos: Because fundraisers are not assigned a "Program" role in the CDS configuration for those specific records, they will not be able to see the Interaction Summaries, even if they have access to the Person Account record.
* Auditability: CDS provides a clear audit trail of who was granted access to sensitive notes and why, which is critical for legal compliance in social services.
Why other options are incorrect:
* Permission Sets (Option A): These grant the ability to use the Interaction Summary object (CRUD), but they do not control which specific records a user can see. If OWD is set to Public, Permission Sets won't hide specific department notes.
* Session Security (Option B): This deals with 2-factor authentication and login requirements, not record-level data visibility between departments. Compliant Data Sharing is the standard Industry Cloud tool for this level of granular privacy.
NEW QUESTION # 41
A consultant is implementing Salesforce for a nonprofit client who is inexperienced with Salesforce. The nonprofit wants to assign an NPSP fundraising training module to their staff. Which training resource should the consultant recommend?
- A. Trailblazer Community Dashboard
- B. Salesforce Help and Training
- C. Learning Path
- D. AppExchange Report
Answer: C
Explanation:
In the modern Salesforce Lightning experience, the Learning Path is the best tool for an admin or consultant to deliver targeted training directly within the flow of work.
What is a Learning Path?
A Learning Path allows a consultant to curate specific Trailhead modules, internal documents, or videos and assign them to specific users or groups based on the page they are currently viewing. For a nonprofit implementing NPSP, the consultant can:
* Curate Content: Select existing Trailhead modules like "Fundraising with Nonprofit Success Pack."
* Assign to Users: Target the training specifically to the "Fundraising" profile or "Gift Officer" team.
* In-App Access: Instead of forcing staff to leave Salesforce to search a separate help portal, the training appears in the "Learning" side panel (represented by the graduation cap icon) while they are actually looking at Opportunity or Contact records.
* Track Progress: Managers can see who has completed the assigned modules, making it a powerful tool for onboarding and change management.
Why other options are incorrect:
* Salesforce Help and Training (Option A): This is the documentation portal. While useful, it is a
"pull" resource (staff have to go find it) rather than a "push" resource (assigned by the admin).
* Trailblazer Community (Option C): This is a forum for discussion and peer support, not a structured training assignment platform.
* AppExchange Report (Option D): The AppExchange is for downloading apps; there is no such thing as an "AppExchange Report" used for assigning training.
NEW QUESTION # 42
A consultant is helping a nonprofit diagnose and address some issues they have with NPSP. The consultant sees the customer is hitting governor limit errors on a particular job. Which action should the consultant take to resolve the issue?
- A. Decrease the batch size for that job.
- B. Increase the batch size for that job.
- C. Schedule that job to run more frequently.
- D. Reschedule that nightly job.
Answer: A
Explanation:
Salesforce operates in a multi-tenant environment, which means all organizations share the same underlying computing resources. To prevent one organization's code from hogging all the power, Salesforce enforces Governor Limits (e.g., limits on CPU time, memory, or the number of database queries).
When a "Batch Job" (such as NPSP's nightly rollup calculation) hits a governor limit, it usually means the system is trying to process too much data at once within a single transaction "chunk." The Solution: Decreasing Batch Size:
* How it Works: In NPSP, batch jobs are broken into segments. If the batch size is set to 200 (the default), the system tries to process 200 records at a time. If those 200 records are complex (e.g., they have dozens of triggers, flows, and related records), the system may run out of memory or time.
* The Fix: By decreasing the batch size (e.g., from 200 down to 50 or 25), the consultant reduces the workload of each individual transaction. While the overall job might take longer to complete, each
"chunk" is more likely to stay within the allowed governor limits.
* Implementation: The consultant can adjust these settings in NPSP Settings > Bulk Data Processes > Batch Control, or by updating the specific batch size in the Apex code or job configuration.
Why other options are incorrect:
* Increasing Batch Size (Option A): This would worsen the problem by putting more strain on each transaction.
* Rescheduling (Option B & C): Changing when the job runs does not change how much data is processed per chunk, so it will still hit the same technical limits.
NEW QUESTION # 43
A nonprofit wants all donations related to a new direct mail appeal to be assigned to a designated restricted fund. How should the consultant advise the nonprofit to achieve this?
- A. Create a campaign for the appeal and use the Manage Allocations functionality to assign the fund.
- B. Run Batch Create Default Allocations bulk data process and specify the designated fund as the default.
- C. Create a campaign for the appeal and add a lookup field for the GAU for the designated fund.
- D. Enable Default Allocations and specify the designated fund as the default GAU.
Answer: A
Explanation:
In NPSP, the tracking of restricted funds is managed through the General Accounting Unit (GAU) and GAU Allocations. When a nonprofit launches a specific appeal (like a direct mail campaign) for a restricted fund, the system can automate the allocation of every gift received through that appeal.
Step-by-Step Implementation:
* The GAU: Ensure the restricted fund is created as a General Accounting Unit record.
* The Campaign: Create a Campaign record representing the "Direct Mail Appeal."
* Manage Allocations: On the Campaign record, a consultant uses the Manage Allocations button (a specialized NPSP interface).
* The Link: In this interface, the consultant selects the designated GAU and assigns it to the Campaign (usually at 100%).
* Automation: Because of NPSP's built-in logic, any time a donation is created and linked to this Campaign (as the Primary Campaign Source), the system will automatically create a GAU Allocation record for that donation, linking it to the restricted fund.
Why other options are incorrect:
* Option D: Setting a "Default GAU" is an org-wide setting. If you set the restricted fund as the default, then every gift in the system (even unrestricted ones) would go to that fund.
* Option C: Simply adding a custom lookup field to the Campaign does not trigger the complex NPSP automation needed to create the Allocation records on the Opportunity. You must use the "Manage Allocations" feature to "connect" the campaign to the GAU logic.
NEW QUESTION # 44
The admin at a nonprofit wants to delegate authority to two specific users to process gift entries. Which three permissions should the consultant add to a permission set so the users can perform this work with only the necessary level of access? (Choose 3)
- A. Grant the View All Data permission.
- B. Grant visibility to the Gift Entry tab.
- C. Grant create and edit access to all required objects and fields.
- D. Grant access to BOI_BatchOverride and BOI_DataImport Visualforce pages.
- E. Grant create, edit, and delete access to all required objects and fields.
Answer: B,C,D
Explanation:
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.
NEW QUESTION # 45
A nonprofit organization has a successful company match donation process. The development team wants to attribute the grouped check to the company, but also ensure that individual donors are credited for their individual match. How should the organization accomplish this goal in Nonprofit Cloud?
- A. Record the company as the donor on the Gift Transaction of the grouped check. Create a Gift Soft Credit for each individual donor and their respective amounts.
- B. Record the company as the donor on the Gift Transaction of the grouped check. Create a Gift Designation for each individual donor and their respective amounts.
- C. Record the individual as the donor on the Gift Transactions for their respective amount of the grouped check. Create a Gift Soft Credit for the company on each of those gifts.
Answer: A
Explanation:
In the context of a Solution Design for corporate giving, a consultant must balance the "Hard Credit" (legal
/accounting ownership of the funds) with the "Soft Credit" (relationship and influence credit).
When a company sends a single "grouped check" that represents the matching funds for multiple employees, the legal donor is the Company. Therefore, according to standard accounting principles, the Hard Credit must be assigned to the company's Business Account.
Step-by-Step Solution Workflow:
* Create the Gift Transaction: The consultant records a single Gift Transaction (or a batch gift) where the Donor field points to the Business Account of the company. This ensures that the organization's financial reports correctly show that the cash came from the corporation.
* Identify the Individuals: The consultant then identifies the individual employees whose gifts triggered the match.
* Assign Gift Soft Credits: For each individual donor, a Gift Soft Credit record is created and linked to the company's Gift Transaction.
* The Soft Credit Recipient is the individual's Person Account.
* The Amount is the specific portion of the matching check that applies to them.
* The Role can be set to "Matched Donor."
* Reporting: When the organization runs its "Total Giving" reports for individuals, it can include "Soft Credit" amounts. This allows the development team to recognize the individuals for their influence in bringing in the matching funds, even though the company technically provided the money.
Why other options are incorrect:
* Option B: This would incorrectly attribute the "Hard Credit" (the legal ownership of the money) to the individuals. This would cause issues with tax receipts and financial reconciliation, as the individual did not personally write the check for the matching portion.
* Option C: Gift Designations are used to track which internal fund the money is for (e.g., "Education Fund"); they are not used to credit people or organizations for their involvement in a gift. Using Soft Credits is the correct architectural approach in NPC for influence and matching-gift recognition.
NEW QUESTION # 46
A gift officer is entering donations and wants to track that the donor responded to the most recent direct mail campaign. Which feature should the consultant configure to record the donor's campaign response?
- A. Automatic Campaign Member Management
- B. Customizable Campaign Influence
- C. Customizable Rollups
- D. Sales Process
Answer: A
Explanation:
In NPSP, the most efficient way to link a donation to a donor's campaign participation is through Automatic Campaign Member Management.31 How the Feature Works:32
* The Link:33 When an Opportunity (donation) is created, it has a Primary Campaign Source field.
* The Automation: If Automatic Campaign Member Management is enabled in NPSP Settings, the system automatically looks at the Primary Contact on the donation and checks if they are already a Campaign Member of that campaign.
* Status Update: If they are already a member, the system can automatically update their Member Status (e.g., from "Sent" to "Responded").
* Creation: If they are not yet a member, the system can automatically create a new Campaign Member record for that donor with a "Responded" status.
Why other options are incorrect:
* Customizable Rollups (Option B): These summarize financial totals but do not handle the "Status" or
"Response" logic on a campaign.
* Customizable Campaign Influence (Option C): This is a Sales Cloud feature used to attribute
"Influence" across multiple campaigns for a single deal. While relevant to high-level ROI, it is not the primary mechanism for simply recording that a donor "responded" to a specific direct mail appeal.
* Sales Process (Option D): This defines the "Stages" an Opportunity goes through (Pledged, Won, etc.) and has no role in campaign response tracking.
NEW QUESTION # 47
A nonprofit organization has identified that some donations should be directed to one or more program areas in the financial accounting software. This information is identified when an Opportunity is being solicited. In the Nonprofit Cloud Fundraising Data Model, which object should be used to record the donor's intent during solicitation?
- A. Gift Transaction Designation
- B. Gift Default Designation
- C. Gift Designation
Answer: A
Explanation:
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.
NEW QUESTION # 48
......
Achieve the NP-Con-102 Exam Best Results with Help from Salesforce Certified Experts: https://torrentpdf.practicedump.com/NP-Con-102-exam-questions.html