The administrator at AW Consulting has created a custom picklist field. Business users have requested that it be a text field. The administrator attempts to change the field type but, is unable to…

Question

Options

• AFormula fields
• BRecord types
• CVisualforce
• DJavascript

• A
  17% (5)
• B
  7% (2)
• C
  3% (1)
• D
  73% (22)

Explanation

Important caveat first: The provided correct answer (D, JavaScript) appears to be questionable for a Salesforce Admin exam. Based on standard Salesforce platform behavior, B (Record Types) is the more defensible answer - picklist fields have a hard system-enforced dependency on record types, which control available picklist values per record type. Changing a picklist to a text field would destroy those value mappings, so Salesforce blocks the conversion.

Here's the explanation as written for D, but flag this question if you're using it for actual Salesforce certification prep:

If D is accepted as correct: JavaScript custom buttons and links in Salesforce can reference a field's type-specific behavior. If a picklist field is embedded in JavaScript-based button logic, Salesforce may block the type conversion to prevent breaking those references.

Why the distractors are wrong (per this answer key): Formula fields (A) and Visualforce (C) can reference picklist fields, but are often handled via dependency updates rather than an outright block on conversion. Record types (B) do control picklist value availability per record type, but the question treats this as a non-blocking relationship here.

Memory tip: Think "J-S blocks JS" - the field type is Jammed when Scripted buttons depend on it. However, for real Salesforce Admin exam prep, remember that record types + picklists are the more classically tested restriction.

Recommend verifying the source of this question - the answer key may contain an error.

No community discussion yet for this question.