CiviCRM Community Forums (archive)

We encountered a problem with the interaction between country codes/abbreviations and state/province codes/abbreviations.

We have contacts from around the world, so we enabled all the countries for the state/province lookup function. But, the results were puzzling.

For example, records with the state code/abbreviation of "OR" (for Oregon) and "US" (for United States) showed inconsistent behavior.

In the main contact view, everything looked fine -- "OR" & "US" in the right places.

But, in the edit detail view, "OR" translated into "Orhei" (apparently the name of a province -- with the "OR" abbreviation/code -- in the country of Moldova), instead of Oregon, USA.

We are using Google mapping geocode data, as we import the records, but that seems to work fine.

When we got rid of all the countries except United States & Canada for the state/province lookup function, all the records imported okay without this problem.

Since we are done with our importing (for now), we would like to go back to suppporting all countries.

However, our fear is that if we go and turn on all the other countries again, that it will trash our existing data and move all our friends in Oregon to Orhei (great frequent flier miles, though :-) !?

Does CiviCRM documentation show anywhere how it applies these rules?

To be able to replicate this, I would need to have Admin rights on the demo server -- to set the state/province table to all countries. The server may also need to be set to Google geocoding too, since that is how our server is set. If we can replicate these conditions, I would be happy to test it with some fake data and send another happy Oregonian to vacation in beautiful Orhei :-)

thanks! aloha, orhei ...

*bumping*

I encountered this today, is there a workaround on this?