Sage 100

 View Only

  • 1.  VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 10:13
    Edited by Rhonda McNamara 05-31-2019 10:18
    Job imports into GL General Journal Header.  Two fields throw this error. SourceJournal and EntryNo, both of which are runtime assigned.   I still get prompted to run the import, but I have not had the client test it to see if it still works or not.  Hoping to resolve error first. 
    Guess they didn't test this during testing. And now it's Go Live day. :-P #Sage100 #Urgent

    UPDATE: Next step in my checklist was to delete all the records in VI_JobPerform.m4t. But I have no records in there.

    Set to read only in the dictionary


    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------
    ​​​


  • 2.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 10:24
    Created a new job in v2019 to mimic yours and received no error.  There is one difference - for your Batch Number you have "Assign" as the operation, yet no value.  Give the Batch No a value and try it again.

    ------------------------------
    Michelle Taylor
    ERP Team Manager, CS3 Technology
    918-388-9772
    ------------------------------



  • 3.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 10:36
    Try removing the Source Journal field and putting it back into the job or just create a new job.  The Batch # should be able to be Assign and value = blank or put it out to an empty field, but in the new versions, I use Assign & blank.
    ​​

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 4.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 10:41
    I'd suspect the L. fields above the H. fields, and try moving them down.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 13:27
    Hm, you may be on to smoething. I notice we're calculating the LINE Source Journal and Entry number and they were as shown below with the dollar sign. They looked like they might want to be more formal, along the lines of GLheader.sourcejournal$ when I used the wizard to select the header field, but that didn't resolve the error.
    But, the good news is i got a hold of a test file and the job runs despite the errors.  I'm going to try some of these suggestions, though. @Kevin Moyes Which would you move down?  This job is pretty OG, so we probably have work arounds that aren't even needed anymore, if they ever were!​

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------

    Original Message


  • 6.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 13:48
    Do you really need those Line fields?  I'm assuming Sage fills those in automatically.  I've never included them in an import.

    ------------------------------
    Beth Bowers
    Mom to Samson, Peanut, ChiChi, Canton, and Cagney
    Beth Bowers
    269-445-1625
    ------------------------------

    Original Message


  • 7.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 14:13
    Since you solved the problem, this is a bit academic, but generally speaking the order of VI lines does matter.  I try to put things in the order they will be used.  An L (line) field before the H (header) fields are set is nonsensical.  You can't add an item code to an SO before you've chosen the customer.  Sage "should" sort this out, and sometimes it works, but I try to remove potential issues by ordering fields logically.  Key Assigns, header, lines, LL... with temp fields listed before they are referenced.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 8.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 14:05
    I think you're all right.  The job works without those two lines referencing the header!  Thank you!

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------

    Original Message


  • 9.  RE: VI error message after upgrading from 2014 STD to 2018 STD.

    Posted 05-31-2019 16:26
    VI is so much better than pre framework, however, there is much work to be done......

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


Related Content