Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Platform App Builder Topic 3 Question 102 Discussion

Actual exam question for Salesforce's Platform App Builder exam
Question #: 102
Topic #: 3
[All Platform App Builder Questions]

Northern Trail Outfitters wants to change a master-detail relationship on

Account to a lookup relationship with a custom object Park. The app builder tries to

reconfigure this but is unable to do so.

What could be causing this?

Show Suggested Answer Hide Answer
Suggested Answer: C

When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity:

C . The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll-up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed.

To resolve this, follow these steps:

Identify and delete all roll-up summary fields on the Account object that reference the Park object.

Convert the master-detail relationship to a lookup relationship.

Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries.

For more guidance, review Salesforce's documentation on Changing Field Types.


Contribute your Thoughts:

Richelle
2 months ago
Hold up, is this a trick question? The Park object needs a master-detail field, but the Account has roll-up summary fields? Sounds like a real Salesforce conundrum.
upvoted 0 times
Lizette
11 days ago
User 4: Let's check if any existing formulas are causing the issue.
upvoted 0 times
...
Elvera
13 days ago
User 3: Could be a conflict with the roll-up summary fields.
upvoted 0 times
...
Rosio
15 days ago
User 2: Maybe the Account record needs to be updated first.
upvoted 0 times
...
Jerrod
16 days ago
User 1: It does sound like a tricky situation.
upvoted 0 times
...
...
Solange
2 months ago
Ah, I bet it's because the Park object needs at least one master-detail field for reporting. Gotta love those Salesforce requirements.
upvoted 0 times
Wynell
23 days ago
User 3: It could also be that the park records have existing formulas on the Account.
upvoted 0 times
...
Gilma
1 months ago
User 2: Maybe the Account record includes Parks roll-up summary fields as well.
upvoted 0 times
...
Laine
1 months ago
Yeah, that could be it. Salesforce can be picky with those relationships.
upvoted 0 times
...
...
Junita
2 months ago
I think it could also be because the Account record includes Parks roll-up summary fields.
upvoted 0 times
...
Sol
3 months ago
You know, this reminds me of that classic Salesforce joke: 'How many Salesforce developers does it take to change a lightbulb? None, it's a known issue.'
upvoted 0 times
Lauryn
1 months ago
C) The Account record includes Parks roll-up summary fields.
upvoted 0 times
...
Nada
1 months ago
B) The Park object needs at least one Master-Detail field for reporting.
upvoted 0 times
...
Mendy
2 months ago
A) The Account is included in a flow process on the Park object.
upvoted 0 times
...
...
Elouise
3 months ago
I agree with Craig. The flow process might be causing the problem.
upvoted 0 times
...
Craig
3 months ago
I think the issue could be with the flow process on the Park object.
upvoted 0 times
...
Vallie
3 months ago
I'm just glad I don't have to deal with these Salesforce relationship shenanigans in my day-to-day. Though, I do miss the occasional 'Why is my Visualforce page not rendering?' mystery.
upvoted 0 times
Elly
2 months ago
C) The Account record includes Parks roll-up summary fields.
upvoted 0 times
...
Dudley
2 months ago
A) The Account is included in a flow process on the Park object.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77