x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 7 replies
  • Subscribers 87 subscribers
  • Views 919 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
47
topics
95
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
965
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
connex

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

SOLVED
Posted By

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 Reply Children
  • 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.

*Community Hub is the new name for Sage City