Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Nonprofit Cloud Consultant Topic 6 Question 107 Discussion

Actual exam question for Salesforce's Nonprofit Cloud Consultant exam
Question #: 107
Topic #: 6
[All Nonprofit Cloud Consultant Questions]

A nonprofit using Salesforce configured with Person Accounts has recently installed NPSP into its org.

Which two configurations should a consultant set to ensure that Person Accounts and NPSP can coexist?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C

To ensure that Person Accounts and NPSP can coexist within the same Salesforce org, follow these configurations:

Different Household Record Type in NPSP Settings:

Navigate to NPSP Settings.

Ensure that the Household record type specified in NPSP settings is different from the Person Account record type.

This prevents conflicts and ensures that NPSP correctly distinguishes between Household Accounts and Person Accounts.

Default Record Type for Profiles of Users Converting Leads:

Go to Setup > Profiles.

Ensure that the default record type for any profiles of users who convert leads is not set to the Person Account record type.

This ensures that when leads are converted, they do not automatically become Person Accounts, which could disrupt the NPSP data model.

By following these configurations, the nonprofit can effectively manage both Person Accounts and NPSP functionalities within the same Salesforce environment.


Salesforce NPSP Documentation: NPSP Configuration.

Salesforce Person Accounts Guide: Person Accounts.

by Elly at Jan 13, 2025, 11:06 AM

Limited Time Offer

25%

Off

Get Premium Nonprofit Cloud Consultant Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Meghan
7 days ago
A and C are the obvious choices. Gotta make sure the record types don't overlap and cause issues.
upvoted 0 times
...
Lacresha
9 days ago
Haha, I'm just imagining the person who came up with option B. 'Let's just completely disable the feature we're trying to use!' Real bright idea there.
upvoted 0 times
...
Shantell
20 days ago
But if we prevent the creation of Person Accounts with a validation rule, how will they coexist with NPSP?
upvoted 0 times
...
Sommer
22 days ago
D is way too extreme. Blocking access to Person Accounts for everyone except Admins is overkill.
upvoted 0 times
Coleen
10 days ago
C) The default record type for profiles of any user who converts leads is different than the Person Account record type.
upvoted 0 times
...
Hildegarde
14 days ago
A) The Household record type in NPSP Settings is different than the Person Accounts record type.
upvoted 0 times
...
...
Yolando
24 days ago
I disagree, I believe B and D are the correct choices.
upvoted 0 times
...
Margot
1 months ago
B is just silly. Why would you want to prevent Person Accounts altogether? That defeats the purpose of using them in the first place.
upvoted 0 times
Dannette
22 days ago
User 2: C) The default record type for profiles of any user who converts leads is different than the Person Account record type.
upvoted 0 times
...
Winfred
27 days ago
User 1: A) The Household record type in NPSP Settings is different than the Person Accounts record type.
upvoted 0 times
...
...
Tony
1 months ago
A and C seem like the right choices to me. You don't want Person Accounts and NPSP record types conflicting.
upvoted 0 times
Verda
14 days ago
User 3: Yeah, that's important for the coexistence of Person Accounts and NPSP.
upvoted 0 times
...
Desmond
18 days ago
User 2: Agreed, we need to make sure the record types don't conflict.
upvoted 0 times
...
Kenneth
1 months ago
User 1: I think A and C are the right choices.
upvoted 0 times
...
...
Shantell
1 months ago
I think we should choose A and C for the configurations.
upvoted 0 times
...

Save Cancel