2016 - 2020 First oScript.SetError Method doesn't trigger an error message in Lot/Serial Number Distribution

Question

This UDS is a Column Pre-Validate on QuantityShipped against the SO Sales Order Tier Distribution table at version 2016 Std through 2020 Advanced. The SetError doesn't always trigger the error message, but it does fail (i.e. clear) the distribution number entered. The error message appears in the TraceWindow, but not to the user. The code is simple and an Exit Sub is used immediately afterwards (also tried excluding the Exit Sub to allow a normal exit - same result). I always see the same entry in the TraceWindow "SCRIPT/CallScript - VB Run Error: <<message to user>>" whether or not the message is presented. The following three line script reproduces the problem. If a second SetError is run (with the test script just enter a quantity on the same row) then it will present its message. The behavior repeats on a new row.

retVal = oScript.DebugPrint("About to Test")
retVal = oScript.SetError("Test")
Exit Sub

You may also see the Pre-Validation script run twice in the trace which is another issue.

David Speck · Accepted Answer

The tier distribution objects are tricky. 
 I tried testing by clearing the line on a post read event script if a certain lot was entered/selected by using the UI objects' BT_RowDel method and the business' object's Delete, Clear, ClearLine, CancelDistribution, ResetLine, etc methods but they all resulted in a message saying the sales order number is required followed by the prompt asking if i want to delete the line because it is not distributed, followed by the distribution window closing on its own and forcefully returning to the Lines tab. Even trying to use oScript.InvokeButton "BT_RowDel" didn't work. 
 I found two ways to prevent the lot number from being saved. 
 Method one is by using the following on a post read event script of the tier distribution table. 
 LotSerialNo = "" : oBusObj.GetValue "LotSerialNo$", LotSerialNo
If oBusObj.EditState = 2 Then
	If LotSerialNo = "200827ABC0103" Then
 If oScript.UIObj <> 0 Then 
 oSession.AsObject(oScript.UIObj).SetVar "CMD_STR$", "X _obj'BT_RowDel(); %SYS_SS'UI'MessageBox$("""", """ & """""" & LotSerialNo & """""" & " is not a valid lot number."")"
 End If
	End If
End If 
 Method two is by setting up a script on a pre validate event of any available column of the tier distribution table. Then open CM_ScriptSettings with DFDM, locate the pre validate event you set up and change the column value to LotSerialNo, when prompted to remove the old key, click yes. Make sure to recompile the business event scripts. You can now use the oScript.SetError method. I did notice though that this did stop the repeated events however, the message was not displayed as expected so i ended up having to use MessageBox as well. 
 LotSerialNo = "" : oBusObj.GetValue "LotSerialNo$", LotSerialNo
If LotSerialNo = "200827ABC0103" Then
	oScript.SetError """" & LotSerialNo & """ is not a valid lot number."
	oSession.AsObject(oSession.UI).MessageBox "", "" & oScript.GetError()
End If

Sage 100

2016 - 2020 First oScript.SetError Method doesn't trigger an error message in Lot/Serial Number Distribution

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING