Sage 100

 View Only
  • 1.  Upgraded customer from v2013 Adv to v2016 Adv on 9

    Posted 10-06-2016 15:32
    Upgraded customer from v2013 Adv to v2016 Adv on 9/20. Installed the Canadian ZIp Codes as I do on all systems now. Today customer emailed that 383 Canadian Customer's zip codes are gone from Customer Maintenance (but still in ship to address screens). They are also questioning the no space in the zip. Any idea of what would make them go missing? It's not all Canadian Customers, as I browsed their Customer Maintenance and some are still there with the space. They want me to fix NOC and I can import but they still have to populate a spreadsheet. Help! Are these Canadian zip codes overwriting any existing zip codes?


  • 2.  RE: Upgraded customer from v2013 Adv to v2016 Adv on 9

    Posted 10-07-2016 07:23
    I've never heard of this one and have done many Canadian upgrades to 2016. Sage's installed Postal Codes don't have spaces, which is unusual but I've not seen it cause problems. Just checking an upgrade from 4.4 to 2016 that I'm working on now, and the Customer Maintenance Postal Codes still have a space, but the Zip Code table has the codes without a space. There must be some sort of conversion algorithm tossing out the ""duplicates"", leaving the no-space version... but I can't think of a reason they'd disappear. (You can set up a DSN to the 2013 system for a query, to make getting the data for importing a bit easier).


  • 3.  RE: Upgraded customer from v2013 Adv to v2016 Adv on 9

    Posted 10-07-2016 08:33
    I posted a similar issue last month regarding Canadian zip codes, Avalara and UPS. If you validate the address with Avalara, it will change the zipcode. Mapping the Canadian address to Worldship results in UPS unable to understand the three character country code in Sage. https://90minds-com.socialcast.com/messages/31845509?ref=stream Oh, for some consistency...


  • 4.  RE: Upgraded customer from v2013 Adv to v2016 Adv on 9

    Posted 10-07-2016 12:12
    Well this is interesting... found in v2013 the zip code was in AR_Customer but not in Sy_ZipCode. Yet when i removed the zip in Cust Maint, hit accept, then go back and enter the zip, it didn't prompt me 'is this a new zip'. If I entered a totally new bogus zip code, it did prompt me. So chalked it up to corruption in Sy_ZipCode in v2013. Did find in v2016 that even though the zips have no spaces, if they enter them into Cust Maint with a space, Sage appears to recognize it and returns the city/state.