How to Export Controlling and Dependent Picklist Values in Salesforce?

If you’ve ever come across dependent picklists in Salesforce, you already know how tricky it can get to manage— especially when dealing with multiple objects and complex dependencies. Whether you’re documenting your org, migrating metadata, or cleaning up unused values, understanding and exporting these field dependencies is crucial.

But here’s the challenge: Salesforce doesn’t offer a direct way to export controlling and dependent picklist relationships to Excel. Admins often resort to manual screenshots or tedious copy-paste work just to review or migrate these dependencies.

That’s where BOFC (Bulk Object Field Creator) makes a real difference. With BOFC, you can instantly extract and export all picklist dependency values into a well-formatted Excel file — saving hours of manual effort and ensuring accuracy in your documentation.

In this guide, we’ll walk you through:

• What controlling and dependent picklists are
  
• Why exporting their mappings matters
  
• How to do it effortlessly using BOFC
  

Let’s dive in! 🚀

What Are Controlling and Dependent Picklists?

In Salesforce, controlling and dependent picklists help you create smarter, more dynamic data entry forms.

• Controlling Field: Determines which values are available in another field.
  
• Dependent Field: Displays values based on what’s selected in the controlling field.
  

For example, if you have a “Country” field (controlling) and a “State” field (dependent), selecting “United States” will display only U.S. states in the dependent field — keeping your data clean and relevant.

These relationships make forms easier for users and ensure consistent data across your org.

Why Exporting Their Mappings Matters

Over time, Salesforce orgs can grow complex — with dozens of objects, multiple picklists, and layered dependencies. Documenting these relationships helps you:

✅ Audit field dependencies: Understand how values are connected before making changes.
✅ Prepare for migrations: Move metadata between sandboxes or production without missing dependencies.
✅ Ensure consistency: Keep your admins, developers, and stakeholders aligned on field logic.

Manually tracking these relationships, however, can be time-consuming. That’s why tools like BOFC simplify the process — letting you export all your controlling and dependent picklist values to Excel instantly for review or documentation.

Example — Controlling vs Dependent Picklist Values

BOFC automatically extracts and displays such mappings in Excel format, ready for review or migration.

Step–by-Step Guide to Export Controlling & Dependent Picklist Values in Salesforce

Step 1: Launch the BOFC App

Go to your Salesforce org and open BOFC (Bulk Object Field Creator) from the App Launcher.

From the home screen, click on “Export Picklist Values for Multiple Fields.”

Step 2: Open the Export Screen

Once selected, a new screen will appear — this is where you’ll configure your export settings.

Step 3: Choose the Objects

Select the option “Export Picklist.”

Then, choose one or multiple Salesforce objects whose controlling and dependent picklist fields you want to export.

Click on “Fetch All Picklist Field(s)” to load all available picklist fields.

Step 4: Select the Dependent Picklists

From the list, select one or multiple dependent picklist fields whose controlling field relationships need to be exported.

Step 5: Start the Export Process

Once your selections are ready, click “Download Dependency Details.”

This will initiate the export process and display an Export Status section at the bottom of the screen.

Step 6: Download the Excel File

Wait a few seconds for the process to complete. When the status updates to “Completed,” a Download link will appear.

Click on it to export the XLS file containing all Controlling and Dependent Picklist Mappings for your selected fields.

Summary

With BOFC, Salesforce admins can export controlling and dependent picklist relationships instantly, without manual effort or configuration.

This saves hours of repetitive work, minimizes errors, and ensures clean, audit-ready documentation for admins and developers alike.