Question

Difficulty: EasyPage Layouts and Record Types Assignment

An administrator recently created a new Record Type for Support Cases named 'Tier 3 Incident'. However, support agents report that when creating a 'Tier 3 Incident' case, they can still select picklist values that apply only to standard Tier 1 support cases. What administrative action was omitted during configuration?

  1. Modifying and assigning the selected picklist values specifically available for the new Record Type.Answer
  2. B
    Assigning a new Permission Set to grant access to the newly added picklist values.
  3. C
    Setting component visibility rules using Dynamic Forms on the Case Lightning Record Page.
  4. D
    Updating Organization-Wide Defaults for the Case object to restrict picklist field access.

Answer

The administrator omitted editing the picklist values for the newly created Record Type in Object Manager.
When a new Record Type is created on an object, Salesforce automatically includes all existing values from master picklists. To display only relevant picklist options, the administrator must explicitly edit the picklists available under that Record Type's configuration page.

Step-by-Step Solution

1
Identify the cause of irrelevant picklist options appearing on a newly created Record Type.
When a new Record Type is created, Salesforce automatically includes all values from the master picklist.
Record Types allow administrators to restrict available picklist values for specific business processes.
2
Determine the necessary administrative step to resolve the issue.
The administrator must open the Record Type in Object Manager and edit the picklist field settings to remove unneeded values.
Configuring available picklist values per Record Type ensures users only select values relevant to that specific record type.

Key Concept

Record Type Picklist Value Assignment
Rate this question