Sage 100

 View Only

  • 1.  Script trigger changes v2021

    Posted 08-10-2021 12:06
    FYI,
    New upgrade to v2021.1 on the weekend with strange errors opening Invoice/Shipping entry, and again after choosing an SO.  Sage support pointed me at *ESC to isolate the problem to scripting, and I found the problems to be a Column Post-Validate script (SalesOrderNo) triggering earlier than it used to. 

    • Error @12: File does not exist (or already exists) File: BM_Options
      • Note, customer doesn't have BM, but it was pre-installed on SPC so that was a big waste of time chasing the false error text to nowhere.
    • IM_ItemWarehouse does not have correct permissions.
      • Info: Error #13: File access mode invalid... SY_Maint.pvc Line 729
      • Click Retry and it scrolls through different Last File Name values (other than IM_IW)

    The error 12 was when opening the panel before the batch selection (so obviously there is no invoice / SO#...) and the error 13 came after setting an SO#, but before the CustomerNo was actually loaded in memory. The script itself does a GetChildHandle on CustomerNo (and UDT lookup too), and I think trying to open the objects too early is the issue.  Adding script filters to stop the script trying to run without the required values in memory seems to have fixed the errors.

    Posting here to help everyone else chasing down the misleading error messages.
    ​​

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


  • 2.  RE: Script trigger changes v2021

    Posted 08-10-2021 12:29
    Any feedback from Sage regarding these finding?  Perhaps @Alnoor Cassim has some thoughts?
    ​

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 3.  RE: Script trigger changes v2021

    Posted 08-10-2021 12:44
    This is fresh off the press today.  I've posted the same information to Sage City where I expect Sage development will see it.  Support stopped when it was isolated to a script issue.

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

    Original Message


  • 4.  RE: Script trigger changes v2021

    Posted 08-12-2021 11:20
    Kevin - Thanks for posting about this here and on Sage City!

    ------------------------------
    Alnoor Cassim

    Email: alnoor@asifocus.com
    Ph: 949-689-9887
    Orange County, CA
    ------------------------------

    Original Message


  • 5.  RE: Script trigger changes v2021

    Posted 08-12-2021 11:27
    No problem.  In addition to what was posted there, Elliott emailed me saying the additional triggers were likely in v2020, when adding the document date warning feature.

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

    Original Message


  • 6.  RE: Script trigger changes v2021

    Posted 08-12-2021 12:08
    Interesting how Sage Support drops you like a hot potato when they find out it was a script, even if the script worked in the most recent version.  But nice that they will dialogue via The Community.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------

    Original Message


Related Content