We turn on Country-State-Picklists on almost every Org we touch.
Assume we act on a NEW and BLANK Org, just fresh spun DE (Developer Edition) Org. But it is the same on any Org and we have tried lots of Orgs within the last 2 day... So rest assured, that the following is NOT related to any strange configuration or to bad data. We cleaned everything, i.e on the Orgs we have the issues there are
- 0 (zero!) records of Contact, Account, Lead, Contract, Opportunity, Lead, Task, Event
- we deleted all custom fields and all custom objects
- we deleted as much as we could (page layouts, etc)
Until now, we followed the work list provided here: yourMyDomain/i18n/AddressCleanerOverview.apexp?setupid=AddressCleanerOverview
Usually it's done from top to bottom and works.
Now with Winter'19 not anymore. At step 2 we scan and for sure fix everything we got as feedback. Then we scan again. Feedback come back clean. But if we proceed to step 3, we get
You must perform a scan of your data and customizations before you can map values to state and country/territory picklist values.
Which leads us back to step 2 - effectively creating an endless loop.
So we can never complete step 3 - hence never activate the country state picklists.
What is going on here? This looks like a severe Salesforce Bug in Winter 19.
UPDATE 1 (2018-10-31)
I got Feedback by Salesforce support:
I want to inform you that, the issue you are facing is a multicustomer issue and many other customers are facing it. The higher team are working on this issue. Will give you an update as soon as we get from the higher team.
UPDATE 2 (2018-11-02)
We have an update from R&D and this has been termed as a Bug.Known Issue link : https://success.salesforce.com/issues_view?title=cannot-enable-state-and-country-picklists-on-a-developer-org&Id=a1p3A00000031hg
As of now there is No ETA on this. This is in review status and probably we should get this addressed soon as the days go by - based on the impact and the users affected count.