Sage 100

 View Only

  • 1.  #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-20-2017 14:59
    #2018pioneer Head's up: I just ran into a Job Cost data conversion issue for a few fields in JC3 when coming from 2014 Std to 2018 Std or Premium. Opened a case with Sage, so I'll keep everyone in the loop. Any 2018 conversions with Job Cost out there yet?


  • 2.  RE: #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-20-2017 15:00
    I am in the process of scheduling one for early January, so I will be watching and sharing


  • 3.  RE: #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-20-2017 17:20
    @KelseyLeerkes you had one didn't you?


  • 4.  RE: #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-20-2017 18:52
    I am working on an upgrade from 4.10 with job cost, with a stop at v2014. It looks like the JCC-Cost code file didn't convert but I haven't looked that close yet. I'll update after I open a case with Sage.


  • 5.  RE: #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-21-2017 08:17
    I had heard (but not researched) there were resolutions in PU1 for the JC conversion. Was PU1 installed prior to conversion on yours?


  • 6.  RE: #2018pioneer Head's up: I just ran into a Job Cos

    Posted 12-21-2017 08:30
    Yeah, I tried RTM and PU1 but no luck with either. The columns that that burned me were the SourceCode and Comment, but there may be more affected. Shelley at Sage is on it.


Related Content