|Available in: Developer Edition and sandboxes by default, and All other editions with pilot participation.|
A global picklist is a restricted picklist by definition. When you create a global picklist, the list of values you specify is protected. Only you can add or change values by editing the “master” picklist.
When you create a custom picklist and base it on the global picklist, its list of values is automatically populated and non-editable. Users can’t load extraneous values to the global picklist or to picklist fields that are based on it through the API.
Create a global picklist from the Setup tree. Then create custom picklist fields the way you always have. But now you have the option of using a global picklist definition for as many custom picklists as you want.
Create your global picklist and specify its values.
- Global picklists can be packaged with an app only in Developer Edition and sandbox orgs.
- The list of inherited values doesn’t appear on the detail page for a picklist that’s based on a global picklist.
- For custom picklist fields based on a global picklist, you can’t change the custom picklist from a single-select to a multi-select picklist.