Sometimes when you capture data the form is kept concise to keep it simple. One example of this is field reuse. For example an address in the US has a state, in Canada has a province and in the UK may have a county. What if you are simply using one field to capture all of these?
In your data you may get a mixed bunch of values as below:
| Name | State/Province/County | Country |
| Donald | FL | United States |
| Justin | ON | Canada |
| Theresa | Surrey | United Kingdom |
| Barack | IL |
How do you map the different fields in Importacular? Clearly there is no state called "Surrey" but equally you want FL to go into the state dropdown on the address.
Importacular evaluates each entry based on the country formatting in RE's international settings. For US, Canada and Australia formatting any value mapped to a state, a province or a county field will go into the State/Province dropdown. If they have a UK formatting then they will go into the county field. If they have a New Zealand formatting then they will go to the suburb field.
What happens where the country is not specified as is the case with Barack's address? Importacular looks at your system settings to determine what the default country is in RE and assign, in this example, IL to the state table.
What happens when the data includes both state and county data? This is more problematic and could, as of the version at the time of writing this article, cause an exception. If Donald's data also specified a separate county field with a value of Miami-Dade then Importacular would assume that this is a state and attempt to add it to the state dropdown which would fail.
As of version 3.3, there is a new setting in the field settings. This only appears for the state/province, county and suburb fields. It will override the international evaluation that Importacular does and instead, if you specify that these values should always go to one of these fields then Importacular will attempt to add these values directly.
