Eliminate Picklist Clutter with Restricted Picklists (Beta)

Enforce the integrity of your picklist data with restricted picklists. This feature is now in beta, so you can easily try it out. A restricted picklist field includes only the values that you’ve defined. Your picklist data stays clean, because users can’t add erroneous or redundant values. This feature is available in both Lightning Experience and Salesforce Classic.
Available in: Developer Edition and sandboxes by default, and All other editions with pilot participation.

Here’s another reason to try restricted picklists: You can take advantage of them in custom metadata types. Custom metadata types are custom-defined types of application metadata that can be packaged and used along with an app. They save time by letting you define configurations and create reusable app components and features. Picklists on custom metadata types are always restricted, so enable restricted picklists to use custom metadata types.

Note

Note

If you have a Developer Edition org or sandbox org, no setup is required to use restricted picklists. You can package restricted picklists with an app only in Developer Edition or sandbox orgs.

For all other editions, restricted picklists are available as a beta feature, which means they’re highly functional but have known limitations. Contact Salesforce to enable restricted picklists.

You define the list of values for a picklist when you create the custom picklist field. However, users can introduce other values by loading them through the API. To enable validation of picklist values against the defined list of values, select Strictly enforce picklist values. This prevents users from adding values through the API.

Defining a Restricted Picklist Restricted picklist setting

Only a new custom picklist field can be a restricted picklist. You can’t convert an existing non-restricted picklist to a restricted picklist.