Sage 100

2017 premium. The user has deleted several Ship Via codes in sales order and created several new Ship Via codes. They frequently use the Sales Order ""Copy From"" feature to create new sales orders from orders in SO history. When they copy from an order in SO history that has a Ship Via code that no longer exists, the order can be processed as usual. This creates issues in Starship as the Ship Via gets mapped and Starship (or the shipping staff) doesn't know what freight to charge. If you create a sales order manually, without copying from another SO, and enter the same invalid, non-existent Ship Via, a ""xxxx is not on file"" message appears and the SO cannot be continued until an on file Ship Via is entered. Is this a bug, or is there a workaround or process that needs to be implemented so sales orders with not on file ship via codes don't get processed?

The Copy From function does not use the business object to set the new order values and therefore the Ship Via validation doesn't trigger. To workaround not involving a script or mod, you can try Advanced Field Settings in Customizer. Don't know for sure but you could try adding validation to Ship Via with that and either copy all the current Ship Via values in there or validate against UDT (Ship Via shadow table). Of course then you need a script or mod to maintain the UDT. You'll have to decide the path of least evil for them.

Thanks Alnoor. I will take a look at custom office first. It is an interesting issue. Normally, field validation occurs immediately after entering a value in the field. It would be inefficient to validate all of the fields after hitting accept. However it seems this could be done only after a copy. Also, required UDFs are not validated at field entry time. They are validated either when moving to a new tab or when clicking accept, so there is precedence for this logic.