Sage 100

 View Only
  • 1.  Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 13:09
      |   view attached
    Test upgraded client from 4.10 to v2016.1. I'm going into P/O Setup Options to change some settings but I get the following message that tells me several fields are required. I get a similar thing in S/O, but not in A/P or I/M. Anyone?


  • 2.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 13:13
    You could simply enable each of these options, save the record and then change it to N if you don't want them. Looks like there are blank/Null values and it wants Y or N only


  • 3.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 13:32
    Thanks, @RobertWhite, that's where I was gonna look at next. It's both companies, several fields. And with my last/successful data conversion attempt, I didn't set any of the P/O Hist settings because it seemed like that was causing an issue. Btw, I don't create the PO Hist at time of data conversion anymore. I just do it afterwards cause it seems to often cause issues, and it only takes a minute or two to run even for a client with a huge PO Entry file.


  • 4.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 14:16
    Yup, that was the issue. Those fields were set as 'null' (i.e., [ ] ) for some reason. I fixed 'em via DFDM.


  • 5.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 14:36
    Thanks for posting the resolution!


  • 6.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-20-2016 16:57
    Interesting @BrettZimmerman , I have always created PO history at conversion and have never had a hiccup...


  • 7.  RE: Test upgraded client from 4.10 to v2016.1. I'm go

    Posted 05-22-2016 15:41
    I did a test upgrade EES 4.4 to v2016.1 and had a similar issue with the PO options. I did enable the PO history during the conversion but when I viewed the PO options this field was unchecked, as soon as I checked I received a message similar to the one posted.