Enable and Disable State and Country/Territory Picklists
When you enable state and country/territory picklists, the picklists are immediately
available to users. However, it can take some time for Salesforce to populate the ISO code
fields on existing records. If users try to edit the state or country/territory on a record
before the code field is populated, they’re prompted to select a code value.
Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: All Editions except Database.com
User Permissions
Needed
To turn state and country/territory picklists on and off:
Modify All Data
From Setup, enter State and Country/Territory Picklists in the
Quick Find box, then select State and Country/Territory
Picklists.
On the State and Country/Territory Picklists setup page, click Enable
Picklists for Address Fields to turn on the picklists.
Note
You can also enable state and country/territory picklists when you finish
converting existing, text-based data to picklist values. See Convert State and Country/Territory Data.
When you enable State and Country/Territory Picklists, history tracking changes
from text to picklist fields.
To turn off state and country/territory picklists, click Disable
on the State and Country/Territory Picklists setup page.
Important
If you disable state and country/territory picklists:
For records that you haven’t saved since enabling picklists, state and
country/territory values revert to their original text values.
For records that you’ve saved since enabling picklists, state, country, and
territory integration values replace original text values.
References to state and country/territory picklists in customizations—such as
workflow field updates, email templates, and Visualforce pages—become invalid.
Columns and filters that refer to picklist fields in reports and list views
disappear.
You can’t edit state and country/territory fields in reports.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.