Users at Cloud Kicks are reporting different options when uploading a custom picklist on the Opportunity object based on the kind of opportunity. Where Should an administrator update the option in…

Question

Options

• AFields and relationships
• BRelated lookup filters
• CRecord Type
• DPicklist value sets

• A
  7% (3)
• B
  14% (6)
• C
  75% (33)
• D
  5% (2)

Explanation

Record Types (C) control which picklist values are available to users based on the type of record - in this case, the kind of opportunity. An administrator assigns specific picklist values to each Record Type, which is exactly how you present different options to different users based on opportunity context.

Why the distractors are wrong:

• A (Fields and Relationships): This is where you create or define a picklist field, not where you control which values appear per record type.
• B (Related Lookup Filters): Lookup filters restrict which records appear in a lookup field - unrelated to picklist value visibility.
• D (Picklist Value Sets): Global value sets define a shared pool of values across objects, but they don't control which values are shown per record type.

Memory tip: Think of Record Types as "personas" for a record - each persona gets its own tailored picklist menu. If users see different options based on what kind of record it is, that's always a Record Type configuration.

No community discussion yet for this question.