SF-Admin Object Manager and Lightning App Builder Practice Question
An administrator has created a custom formula field that returns a text value. The business team now requests that this formula field be used as the controlling field for a dependent picklist on the Opportunity object. What is the platform limitation regarding formula fields and dependent picklists?
⚠ Common exam trap
Candidates often assume that because a formula returns a text value, it functions like a standard text field. They fail to realize that the dynamic nature of formulas prohibits their use as controlling fields.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Formula fields cannot be used as controlling fields for dependent picklists under any circumstances.
Salesforce platform architecture does not support formula fields as controlling fields for dependent picklists because formula values are calculated dynamically on the fly. Dependent picklists require static field types such as standard or custom picklists and checkboxes to accurately map dependent dependency matrix values. Recognizing this constraint prevents administrators from designing broken schema configurations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Formula fields can act as controlling fields only if they return numeric values rather than text.
Why it's wrong here
Controlling fields for dependent picklists are restricted to standard or custom picklists and checkboxes, regardless of the data type returned by a formula field. Even numeric formulas are completely ineligible to serve as controlling fields in Salesforce metadata.
- ✓
Formula fields cannot be used as controlling fields for dependent picklists under any circumstances.
Why this is correct
Salesforce explicitly prohibits formula fields from acting as controlling fields for dependent picklists because their values are computed dynamically rather than stored as static database values. The controlling field must be a standard or custom picklist or checkbox.
- ✗
Formula fields can be used as controlling fields only if they are referenced in validation rules first.
Why it's wrong here
Validating a formula field against rules or workflow criteria does not alter its underlying dynamic calculation nature. It remains ineligible to act as a controlling field for dependent picklists regardless of how many validation rules reference the field.
- ✗
Formula fields can serve as controlling fields provided they use the TEXT() conversion wrapper.
Why it's wrong here
Formula fields cannot act as controlling fields at all, regardless of any TEXT() conversion, because dependent picklist controlling fields must be picklist or checkbox types. The conversion claim is tempting since TEXT() changes the displayed data type, but it does not change the underlying field type.
About these practice questions
This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.