Looks like the SetValue occurs AFTER the condition is evaluated so you can't refer the LastErrorMsg or returned value in the condition of the same field you want to test.
If you don't mind a bit of perform logic, you could either use the After Assign event or use Calculated as the operation and handle everything in the field properties of the transaction quantity field.
Below are two variants using perform logic in the calculation of the TransactionQty field. Both require changing the "x" within the brackets of the IMP$[] variable at the beginning to a number that represents the column position in the source file that you want to use for the transaction quantity.
This first one will first attempt to set the value BUT if the business object returns anything other than 1, it will reset it to 0, set and use the RETURNEDVALUE variable in the Condition to control whether or not the import log reports it as assigned or not assigned.
Calculation:
EVN("NUM(IMP$[3])",0); RETURNEDVALUE=0; IF VAR<>0 THEN { RETURNEDVALUE=coBusiness'Lines'SetValue("TransactionQty",VAR); coBusiness'Lines'SetValue("TransactionQty",0) }
Condition:
RETURNEDVALUE=1
This second one will first attempt to set the value BUT if the business object's LastErrorNum is "IM_ExceedsQty.X3", then it will reset it to 0, set and use the RETURNEDVALUE$ variable in the Condition to control whether or not the import log reports it as assigned or not assigned
Calculation:
EVN("NUM(IMP$[3])",0); RETURNEDVALUE=0; RETURNEDVALUE$=""; coBusiness'Lines'LastErrorNum$=""; IF VAR<>0 THEN { RETURNEDVALUE=coBusiness'Lines'SetValue("TransactionQty",VAR); RETURNEDVALUE$=coBusiness'Lines'LastErrorNum$; coBusiness'Lines'SetValue("TransactionQty",0) }
Condition:
POS(UCS("IM_ExceedsQty.X3")=UCS(RETURNEDVALUE$))=0
Both rely on the following selection criteria to not select the line if the transaction quantity ends up being 0.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------
Original Message:
Sent: 10-30-2021 01:19
From: David Speck II
Subject: VI job to import into IM Transaction Entry for Transfers
Could always put in the condition for the quantity that the coBusiness'Lines'LastErrorMsg$ is blank or not equal to that particular message. Although to reliably use this, you would need to clear the property before the transaction quantity is set. I would imagine that the returned value when being set is probably a -1 since it is setting a warning. I can't recall off the top of my head if you can refer to the variable in the condition field but I can check it in the morning.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------
Original Message:
Sent: 10-29-2021 18:35
From: Barbara Goldstein
Subject: VI job to import into IM Transaction Entry for Transfers
No, I can only pull from IM_TransactionHeader or IM_Warehouse.
------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
San Jose CA
800.627.9032 x221
Original Message:
Sent: 10-29-2021 17:20
From: Kevin Moyes
Subject: VI job to import into IM Transaction Entry for Transfers
Can you get the warehouse QoH into a Temp field (file assign...), and add a condition to the quantity field based on that?
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON