Forum Discussion
Zip code (geography type) no longer provides Admin Division 2 (County/district/other)
As title suggests, I was previously able to extract county from zip code (as geography data type), using Admin Division 2. Starting August 28th, I was no longer able to extract this same information ...
You may extract first city and from it county. Or by formula to exclude intermediate step
- I'm experiencing the same issue and while I did notice that the method you've described here was a workaround, I'm also now experiencing new, different issues with the geography data as well. Specifically, certain accurate zip codes (e.g., 72206, 72207 in Little Rock, and 63129 in Saint Louis) are unable to populate the associated 'city' column. It just appears with a #FIELD! value. I am able to accurately populate the 'Name' and 'Description' columns from the zip code, but only the 'City' column appears to be able to generate the Admin 1 and Admin 2 columns. This wasn't occurring as of last month, to my knowledge. I'm just curious if you have encountered anything similar to this or may have any ideas.
Unfortunately I have no idea why so. You may Send a Frown to Microsoft. On ribbon Help->Feedback->Report a problem. Not sure it'll be fixed, at least Microsoft monitors such feedback.
- Your formula tries to pull the city from the zip, and even though all zip codes have a county, not all zip codes have a city, or some zip codes have more than one city. In those cases this formula will stall at the city determination step (and will results in a result of "#FIELD!")
If a city is successfully determined by the formula, the formula may still fail if a city correlates with more than one county.
So, your work around is definitely helpful, but unfortunately doesn't work to replace directly determining county from zip. I'm not sure of any other better solution yet, but I'm working on it (which is how I came across this thread).
