What data loss considerations should an administrator keep in mind when changing a custom field type from Text to Picklist? Choose 2 answers

Question

Options

• AThere will be no data loss with use of a global value set.
• BAssignment and escalation rules may be affected.
• CAuto updates will be made to Visualforce references to prevent data loss.
• DAny list view based on the custom field is deleted.

• A
  8% (3)
• B
  5% (2)
• C
  15% (6)
• D
  73% (29)

Explanation

When converting a custom field from Text to Picklist, any list views that filter or sort on that field are automatically deleted - administrators must manually recreate them after the conversion, making D a clear data loss concern. Option B is a plausible trap because assignment and escalation rules can be affected by field type changes in general, but Salesforce flags list view deletion as the specific documented impact for this conversion, not rule disruption. Option A is incorrect because a global value set controls which values are available, but it does nothing to preserve existing free-text data that doesn't match those values - that data is effectively lost or becomes invalid. Option C is false because Salesforce does not auto-update Visualforce page references; developers must manually update any markup or controllers that reference the field's old behavior.

Memory tip: Think "LV = Lost Views" - converting to Picklist Locks down free text and Vaporizes list views. If it filters on the old field, it's gone.

No community discussion yet for this question.