Loading

Issue in enabling State and Country/Territory Picklists

Udgivelsesdato: Jun 30, 2026
Beskrivelse

When a user attempts to enable "State and Country/Territory Picklists" in a newly created Developer Sandbox, they can encounter a situation where the conversion process detects address data that requires mapping even though no transactional record data was copied. The problem occurs during activation when Salesforce requires completion of the step "Convert identified data in standard address fields." The process prompts the user to review and map many records before the feature can be enabled.

This raises the following questions:

  • Why does the State and Country/Territory Picklist conversion process identify and require mapping for a large volume of address data when no transactional records are copied into a Developer Sandbox?
  • What is the recommended approach to complete or bypass the conversion process so that the feature can be successfully enabled?

In these scenarios, querying the standard objects typically confirms that no business records exist in the sandbox. For example, the following queries return zero records:

SELECT COUNT() FROM Account
SELECT COUNT() FROM Lead
SELECT COUNT() FROM Contact

Despite the absence of records on any of these objects, the conversion wizard still detects address data that requires review and mapping before activation can proceed.
Løsning

Whenever a user encounters such scenarios, we need to understand that when creating or refreshing a Salesforce Developer or Developer Pro sandbox, configuration data — including reports, dashboards, price books, products, apps, and all Setup customizations — is copied from the source organization. A small sample of data from standard and custom objects, documents, files, and attachments may also be copied. Understanding what is and is not included helps admins plan sandbox-dependent testing and development work. 

Examples of what does and does not get copied over:

Copied over:

  • All code
  • All internal users
  • All architecture such as custom objects, custom fields, validations, workflows, etc.

Not copied:

  • Any records (other than internal users).
  • Community or portal users, since the associated contact/account records are not copied.

As the internal user records will be copied, we need to check for country and state data in the user records, which can cause issues in these scenarios because user records are often overlooked. Use the queries below to check this.

SELECT COUNT() FROM Lead
SELECT COUNT() FROM User
SELECT Id, Country, State FROM User WHERE Country != NULL OR State != NULL
SELECT Country, COUNT(Id) FROM User WHERE Country != NULL GROUP BY Country ORDER BY COUNT(Id) DESC
SELECT State, COUNT(Id) FROM User WHERE State != NULL GROUP BY State ORDER BY COUNT(Id) DESC


Vidensartikelnummer
005387020
 
Indlæser
Salesforce Help | Article