We have some instances where the address zip in Google Maps are incorrect, and can not be validated. In these instances we add the zip to the Zip Codes module in Astea.
But I now have an case where even adding a Zip Code here allows me to save the address. I get the dreaded:
The zip does not show up during validation:
But is added in the Zip Code module:
And there is no error in the event log
Best answer by Phil Seifert
Hi Bjørn,
After some investigation, the problem seems to be reported correctly per the mapping service provided Alliance is using which is Google in this case. I checked the following to retrieve the zip codes:
Google zip = 1400
Bing zip = 1404
TomTom zip = 1423 (this is what you wanted). I was able to retrieve the lat/long from TomTom should you want to manually insert this:
After some investigation, the problem seems to be reported correctly per the mapping service provided Alliance is using which is Google in this case. I checked the following to retrieve the zip codes:
Google zip = 1400
Bing zip = 1404
TomTom zip = 1423 (this is what you wanted). I was able to retrieve the lat/long from TomTom should you want to manually insert this: