Loading
Prepare for Email to Become the Default Login ExperienceRead More
Intermittent freezing when using using certain browser versionsRead More
Set Up and Maintain Your Salesforce Organization
Integration Values for State and Country/Territory Picklists

Integration Values for State and Country/Territory Picklists

An integration value is a customizable text value that’s linked to a state or country/territory code. Integration values for states, countries, and territories default to the full ISO-standard state, country, and territory names. The way integration values function is similar to the way API names of custom fields and objects function. Configure integration values so integrations that you set up before enabling state and country/territory picklists continue to work.

Required Editions

Available in: both Salesforce Classic and Lightning Experience
Available in: All editions except Database.com

When you enable state and country/territory picklists, your text-typed State/​​Province and Country fields are repurposed as Integration Value fields. In reports and list views, your Integration Value fields are called State/​​Province (text only) and Country (text only). In addition, for each of your State/​Province (text only) and Country (text only) fields, a picklist-typed State Code or Country Code field is created. The state and country/territory picklist values set up in your org determine the available values on these code fields.​

Among the fields on each state or country/territory picklist value are Active, Visible, Name, Code, and Integration Value. All your state and country/territory picklists—​for Billing Address, Shipping Address, and so on—can access the state and country/territory picklist values you create. By storing a state or country/territory code, your records to access other information about your states, countries, and territories.

By default, Name and Integration Value fields for your states and countries contain identical values. We show the value in the Name field to users who interact with your picklist. Integration Value is used by:

  • Apex classes and triggers
  • Visualforce pages
  • SOQL queries
  • API queries and integrations
  • Rules for assignment, AutoResponse, validation, and escalation
  • Workflow rules
  • Email templates
  • Custom buttons and links
  • Field set customizations
  • Reports and list views

If the Integration Value is different from the value in the Name field, all values in State/​​Province and Country fields for the listed contexts must match the Integration Value. For example, if the Integration Value for the state of Tokyo has been updated to Tokyo1 in the UI, then all references to Tokyo must be replaced with Tokyo1.

When you update a code value on a record, that record’s State/​Province (text only) or Country (text only) column is populated with the corresponding integration value. Likewise, when you update a state or country (text only) column with a valid integration value, we keep the corresponding state or country/territory code column in sync. You can change your org’s integration values after you enable state and country/territory picklists. However, when you update your picklists’ state and country/territory integration values, the integration values on your records aren’t updated. Name values aren’t stored on records. Instead, they’re retrieved from Salesforce based on a record’s State Code or Country Code value. If the states, countries, or territories in your picklists have different field values for Name and Integration Value, make sure your report or list view filters use the correct values. Use names in State and Country filters, and use integration values in State (text only) and Country (text only) filters. Otherwise, your reports can fail to capture all relevant records.

Edit your integration values in Setup or using Metadata API. The Name field of states, countries, and territories are editable only in Setup. In Metadata API, the Name and Integration Value fields are called label and integrationValue, respectively.

 
Loading
Salesforce Help | Article