How to run two scripts after VI job across each invoice in batch?

Question

I have a VI Job that imports sales order invoices into a batch. I have scripting that does some zip code validations and then uses scripting to interact with 3rd party integration buttons that are installed (Vertex tax software). The scripts work perfectly during manual operation, but because the VI job is importing to tables the events that normally trigger the scripts aren't taking place. How can I fire these off after the VI job? I suspect I use Perform Logic but I have no experience with Perform Logic and need some help understanding how to tell MAS to run those scripts on the newly created batch from VI. One script is a UI script for all users all companies and is an Panel-On Exit trigger. The other is a Business Script and is a table pre-write.

David Speck · Accepted Answer

That should indicate they have a method in their override classes that match the button name. So if you know the button name you should be able to call the method from the correct class. However, whether that method is at the UI or Bus level needs to be determined, if at the UI level, you can't easily accomplish this from the VI perform logic. Ideally, you can write a well written email to Vertex describing what you are trying to do and hope they respond with the method name, class, and arguments to the method.

David Speck · Answer

You'll need to determine exactly what commands their buttons are executing, they could be either executing scripts (like vbs, js, or provideX) or calling methods that have been added as class overrides. 
 You can determine this by using Data File Display And Maintenance to open the .m4l file that contains the customizations. Depending on how the customizations were added, they should be either in MAS90\SO\Custom\<sub folder for user & company> or MAS90\SO. Not sure if they are added to Sales Order Entry (SO_SalesOrder.m4l) or Invoice Data Entry (SO_Invoice.m4l) so you need to open the correct library. 
 Once opened in DFDM, search for the button by name, you can open the panel in Customizer and select the button and view its control name in the status bar in the lower left. 
 Once you have located the button record, look at columns 13 and 24. See below for example of a custom button that executes a vbscript. 
 
 If column 24 is blank, then there should be a class method of the same name as the control that should be called when the button is clicked. 
 If you can figure out the method name and any applicable arguments, you should be able to call it from perform logic in VI. The exception to this would be if the methods only exist in the UI's class overrides and not the business object's. 
 Regarding the existing scripts, as Kevin said, the UI events will not be triggered by VI although the table event should be however you will need to inspect the script to see if it contains any one (of many) or more ways to limit a script to a certain start program, class, role, and/or other specific criteria that would cause it to exit early or not process the part of the script you are expecting to be processed.

Sage 100

How to run two scripts after VI job across each invoice in batch?

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING