A Protected Set of Reusable Values
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 edit values.
When you create a custom picklist field and base it on the global picklist, its list of values is inherited from the global picklist. Users can’t change the values because they’re defined as a picklist value set. They also can’t add values through the API to the picklist value set or to picklist fields that use it.
Convenient Creation and Maintenance
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 value set for as many custom picklists as you want.
Specify the picklist value set when you create a global picklist. If you edit the global picklist definition, all of the picklist fields that use its picklist value set are also updated.
Say you want a picklist field called “Rating” on Accounts and Opportunities, with values Hot, Warm, and Cool. Instead of maintaining those picklist values separately on two different objects, create one global picklist with your value set. Then create a picklist field on each object, and set those picklists to inherit the global picklist value set. Each picklist automatically has the values Hot, Warm, and Cool.
- The list of inherited values doesn’t appear directly on the detail page for a picklist that’s based on a global picklist; but you can click a link to view the picklist value set.
- For custom picklist fields based on a global picklist, you can change from a single-select to multi-select picklist, and from a multi-select to single-select picklist. However, you can’t change the picklist to a different field type such as checkbox, currency, or text.