Configure State and Country/Territory Picklists
Configuring state and country/territory picklists means choosing which states and countries you want to be available in your Salesforce org. It lets you make state and country/territory picklists available for purposes like importing data, working with external systems, and accessing picklist data from the Metadata API.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: All Editions except Database.com |
| User Permissions Needed | |
|---|---|
| To configure state and country/territory picklists: | Modify All Data |
Configuring picklists isn’t required for you to enable state and country/territory picklists for users, but it’s highly recommended. Configuring picklists helps ensure continuity and data integrity with existing state, country, and territory data and customizations.
When configuring states, countries, and territories, you start with countries and territories, and then drill down to their states or provinces. State and country/territory picklists include 235 countries and territories by default. They also include the states and provinces of the United States, Canada, Australia, Brazil, China, Japan, India, Ireland, Italy, and Mexico. State and country/territory picklists that contain more than 1,000 states or countries/territories can cause degraded performance. For the complete list of default countries, see Standard Countries and Territories for Address Picklists.
- Integration values for state and country/territory picklists can also be configured through the Metadata API. For more information, read about the AddressSettings component in the Metadata API Developer Guide.
- State and country/territory picklists aren’t supported in Salesforce change sets or packages. However, you can move integration value changes for state and country/territory picklists between sandbox and production orgs by using the Metadata API. To edit the existing states and countries in a picklist, configure your state and country/territory picklists in your sandbox org. Then, use the Metadata API to retrieve the sandbox configurations, and deploy them to your production org. You can’t deploy new ISO codes or update ISO code values using any API.
- 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 page, click Configure States, Countries, and Territories.
-
On the Configure States, Countries, and Territories page, select from the following
options:
- Active: Makes the country or territory available in the Metadata API so that records that contain the country or territory can be imported. However, unless you also set it as visible, the country or territory isn’t available to users in Salesforce. Otherwise, users can still make updates to an invisible country or territory through the API.
- Visible: Makes the country or territory available to users in Salesforce. A country or territory must be active before you can make it visible.
- Click Edit to view and edit details for the country, including to configure its states or provinces.
- (Optional) Under Picklist Settings, select a Default Country/Territory. The Default Country/Territory automatically populates country/territory picklists for new records in your org, but users can select a different country or territory. Default countries and territories must be both active and visible.
- To save your configuration, click Save.
- Active states and countries not marked Visible are still valid filter lookup values. You can use invisible states and countries when creating filters in reports, list views, workflows, and so on.
- If Custom Address Fields is enabled in your org, the Active checkbox for all countries and states is greyed out and cannot be changed. This limitation persists regardless of whether State and Country/Territory Picklists is enabled for standard fields. To manage which values are available to users when Custom Address Fields is active, use the Visible checkbox instead.
