The Global picklist value set are independent and reusable. We can use a single picklist in many custom picklist fields. Global picklist helps us to share picklist values throughout all the objects by letting us create picklist fields based on a default list of values. They can keep our picklist data lean by preventing users from adding erroneous or redundant values through the API. We can have a maximum of 500 global picklists in one Org.
A global picklist is by its name a restricted picklist. Only the system administrator can change the picklist values. When we create a global picklist, the list of values we specify are “locked”; so, that we can add or rename the values only by editing the global picklist.
This feature is available in both Lightning Experience and Salesforce Classic.
So far, when a user enters an invalid picklist value or a value that is not available in the picklist options, that value will be still created as a new value, thus it creates inappropriate data. By using Global Picklist functionality, we can create a single picklist and use it for multiple objects per business needs. This reduces data redundancy, saves time and consumes less space. E.g. Create a global picklist value for data like “State”, “Country”, “Yes”, “No”, “In progress”, “Completed”, “Pending”, “Denied” etc.
From Setup, enter Picklists in the Quick Find box, then select Picklists.
Next to Global Picklists, click New.
Enter a label for the global picklist and Click save.
In the Picklist Value Set section, click New.
Add picklist values by clicking New, then entering the values one per line and Click Save.
To reorder the values, click Reorder. Optionally, choose to sort values alphabetically or to use the first value as the default value.
Finally, we have the global pick list in place and available for all objects. You can use this global picklist field while creating a new custom field for any object, as shown below.
The Global Picklist helps to share the picklist values across all the objects in the system, by letting to create the picklist fields based on a master list of values. They keep the picklist data clean by strictly enforcing only valid values can be selected or added to database.