In Sage 100 2023, why does the HandleScriptUI method now get Error #88 after InvokeButton?

Solved

To reproduce, in either 32-Bit or 64-Bit Sage 100, create an "Execute Script on Server" button in either Customer Maintenance or Item Maintenance (maybe any panel) that runs a simple two line script:

retVal = oScript.InvokeButton("BT_LINK_2")
retVal = oUIObj.HandleScriptUI() 

Where the target button (BT_LINK_2) runs another script with any valid statement (MsgBox "Hello World" 'works) and the result will be an Error #88 and the MsgBox is not invoked. This worked in 2022 and 2021

Parents
  • 0

    The hot fix for the error 88 will be available next week (Jan 8 - Jan 12) provided it passes QA.

    LM7204T - 32 bit Sage 100
    LM7205T - 64 bit Sage 100

    John Nichols
    Sage

  • 0 in reply to jcnichols

    This appears to have corrected the some of the 88 errors we've been experiencing; however, it did not resolve the issue our client is experiencing mentioned above.

    If a button script creates a business object for another module (i.e. Sales Order entry button creating a PO_PurchaseOrder_bus object) any field validation (post / pre) script found in that newly created object still causes an error 88 upon execution.

    The line numbers in SY_Maint.pvc most reporting error 88 are 3450, 3455 and 3556.

Reply
  • 0 in reply to jcnichols

    This appears to have corrected the some of the 88 errors we've been experiencing; however, it did not resolve the issue our client is experiencing mentioned above.

    If a button script creates a business object for another module (i.e. Sales Order entry button creating a PO_PurchaseOrder_bus object) any field validation (post / pre) script found in that newly created object still causes an error 88 upon execution.

    The line numbers in SY_Maint.pvc most reporting error 88 are 3450, 3455 and 3556.

Children
No Data