What if instead of using a checkbox and a hardcoded charge item code in the script, you use either a UDF to hold the charge item's item code or set up a standard bill for the item and only include the charge item's item code as the component. The UDF allows the customer more control if they want to use a different charge item on different items (although a UDT could work for this too, item code in the key column and charge item code in the second column) whereas the bill allows them more control to not only use a different charge item code but multiple charge item codes, if applicable, in addition to being able to specify a scalable quantity, if applicable and the charge item is not set up as a "Setup Charge".
The script would then read the appropriate table/field and go from there.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------
Original Message:
Sent: 05-15-2020 13:48
From: alan niergarth
Subject: Bundle and/or special charge
The item containing the BOM would have to be "received" ahead of time in order to use a standard bill. A script to add misc charge as described by @Kevin Moyes is the way to go. You could reference back to a checkbox UDF in the item file if a charge needs to be added when that item is sold.
------------------------------
alan niergarth
Velosio LLC
------------------------------
Original Message:
Sent: 05-14-2020 18:40
From: Moira Goggin
Subject: Bundle and/or special charge
Do they have BoM? BoM can contain regular and misc. items/charges.
------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.