Enhancements & Revisions



Adagio OrderEntry 9.3A


January 17, 2019



    ·    In OrderEntry 9.3A (2018.12.14), if you used the Customer button to edit the customer when creating a new order and selected the ‘None’ button when prompted with “Customer and/or shipto record have changed. Do you want to propagate the changes to this order?”, a data integrity error resulted. The previous order edited by the user was corrupted.

    ·    In OrderEntry 8.1C and higher, tax was not calculated correctly for Levy codes 11 to 15. They were based on price rather than the Levy amount from the item.

    ·    GridView views using the composite tables ‘OE Ord Detail /w Head’ and ‘OE Hst Detail /w Head’ for OrderEntry 9.3A did not work after installing OrderEntry 9.3A (2018.12.14). This has been corrected.

    If you already changed your views to correct the problem, you must edit the Definition for the view and change from the table having the word “(old)” in it (eg. ‘OE Ord Detail (old) /w Head’ and ‘OE Hst Detail (old) /w Head’), to the table without the word (old). Or, restore your views to the version before the correction.

    Any new views you create should use the tables without the word “(old)” in the name so all of the new fields are available to you.

    ·    In OrderEntry 9.3A, the Remember Form Options setting in User Preferences was not remembered for the Print Labels function.

    ·    Changes were made for a future release of SalesAnalysis 9.3A.

    ·    If the Contact Last Maintenance Date on the customer Shipto record was blank, this caused the message “Customer and/or shipto record have changed. Do you want to propagate the changes to this order?” to always display when editing an order if the shipping information had been changed.



© Copyright Softrak Systems Inc. All rights reserved.