(Real Solutions + Interview Prep + Best Practices)

Hey Salesforce admins! 👋 Get ready to transform clunky forms into smart, efficient experiences. Here’s your ultimate guide to picklists and dependencies – with battle-tested solutions!

🛠️ Simple Setup Steps

Create a Picklist

  1. Setup → Object Manager → Your Object
  2. Fields & Relationships → New → Picklist
  3. Add values (one per line):textCopyDownloadIndia USA Japan Germany
  4. ✔️ Check “Display alphabetically”
  5. ❌ Never delete → Deactivate unused values

Build Field Dependency

  1. Create Country and City picklists
  2. Field Dependencies → New
  3. Set:
    • Controlling Field: Country
    • Dependent Field: City
  4. Map values:CountryCitiesIndiaMumbai, BangaloreUSANew York, Austin

🚨 Real-Time Scenarios & Fixes

⚡ Scenario 1: Inconsistent Customer Data

  • Problem: Sales team selects wrong cities for countries.
  • Solution:1. Create Country → City dependency 2. Add validation rule: ISBLANK(City) && NOT(ISBLANK(Country)) → Prevents submissions until valid city is selected!

⚡ Scenario 2: Slow Form Navigation

  • Problem: 200+ country options slow user selection.
  • Solution:1. Split into Continent → Country dependencies 2. Use global value sets for reuse → Cuts selection time by 60%!

⚡ Scenario 3: Historical Data Corruption

  • Problem: Deleted “Russia” breaks old records.
  • Fix:1. DEACTIVATE value instead of deleting 2. Use record types to hide from new forms

🔥 7 Critical Interview Q&A

  1. Q: Can a multi-select control a dependency?
    → A: ❌ No – Multi-selects can ONLY be dependent fields.
  2. Q: How to add new values without breaking reports?
    → A: Add at BOTTOM → Reorder alphabetically.
  3. Q: Why can’t standard picklists be dependent?
    → A: Salesforce locks them to protect system logic.
  4. Q: Fix: “Value exists but doesn’t show in dependency”
    → A: Check field-level security → Ensure value is ACTIVATED and mapped.
  5. Q: When to use picklist vs. record types?
    → A: Picklists for field values → Record types for entire page layouts.
  6. Q: How to migrate picklist values between environments?
    → A: Use Change Sets or SFDX → NEVER manual entry!
  7. Q: Why is “Display alphabetically” greyed out?
    → A: Global value sets require sorting during value creation.

âś… 10 Best Practices (Save These!)

  1. Limit Values → Max 250 per picklist
  2. Default Wisely → Set most common value (e.g., “India” for IN orgs)
  3. Multi-Select Caution → Avoid for >10 options
  4. Test Dependencies → In SANDBOX first
  5. Global Value Sets → For reusable options (e.g., Country)
  6. Deactivate → Never Delete
  7. Alphabetize Lists → Over 15 items
  8. Use Descriptions → Explain values (e.g., “Includes remote roles”)
  9. Control Visibility → Hide inactive values via Record Types
  10. Backup Values → Weekly if using manual entry

đź’ˇ Pro Tip: Combine picklists with Dynamic Forms for UX magic!

🚀 Try This Enterprise Exercise

Build a 3-tier dependency for a hotel chain:

  1. Continent → Country → City Asia → India → Mumbai Europe → Germany → Berlin
  2. Add multi-select “Amenities” dependent on Hotel Class Class = "Luxury" → ["Spa", "Butler"]