CRT-101 · Question #55
An Computing needs to capture a loss reason in rich text field when an opportunity is Closed lost. How should an administrator configure this requirement?
The correct answer is B. Create a validation rule to display an error if stage is Closed lost and Loss Reason is blank. This is a conditional required field scenario: the Loss Reason field should only be required when Stage equals 'Closed Lost,' not for all opportunities. Validation Rules are the correct tool for conditional field requirements-the rule can check IF Stage = 'Closed Lost' AND Loss…
Question
An Computing needs to capture a loss reason in rich text field when an opportunity is Closed lost. How should an administrator configure this requirement?
Options
- ASelect the requirement checkbox next to the loss reason field on the page layout.
- BCreate a validation rule to display an error if stage is Closed lost and Loss Reason is blank.
- CCheck the required checkbox on the Loss Reason field in Object Manger.
- DConfigure a workflow rule to display an error if Loss Reason is blank
How the community answered
(30 responses)- A13% (4)
- B80% (24)
- C3% (1)
- D3% (1)
Explanation
This is a conditional required field scenario: the Loss Reason field should only be required when Stage equals 'Closed Lost,' not for all opportunities. Validation Rules are the correct tool for conditional field requirements-the rule can check IF Stage = 'Closed Lost' AND Loss Reason is blank, THEN display an error. Making the field required on the page layout (A) or on the field definition in Object Manager (C) would force the field to be required for all opportunity saves regardless of stage, which is too broad. Workflow Rules (D) cannot display validation errors; they can only perform actions like field updates or email alerts.
Topics
Community Discussion
No community discussion yet for this question.