Version 4.008.624 - 4.008.627 - February 23, 2023

Added Other Locations (as Location #1-4) to the DataView export of the Item Listing report (IC:Reports).
Report DataView export maximum has been updated from 60 to 70 columns.
When adding a vendor item lookup (IC:Inventory:Lookup By) for a vendor without an electronic catalog, there will no longer be a check for the part number in the electronic catalog file.
On the handheld with large format screen selected, when doing IOR receipt, double-clicking the listing line allows changing that line’s quantity.
A file structure check has been implemented for ECatalog to prevent data corruption when doing a file repair.
Adding an existing or new model to a service ticket will now auto-fill and/or add the model (It will ask again to add if it’s on the same service ticket.)
Item Listing report now has the ability to include full 250 character values for memo fields (notes).
When emailing customer reports from the customer file, the customer’s email address will now be entered by default. Corrected

Reindex/Pack options (System:File Maintenance) may cause an error. Corrected
An error may occur at ring sale when selecting column prices for an item that doesn’t have column pricing values. Corrected
Auto-adding of item from ECatalog is not pulling in the appropriate average and last costs when stocking unit is different from purchase unit. Corrected
Sales order “Refresh Pricing” button is not updating the MSRP to current MSRP but to retail. Corrected
Mercury is ignoring the “After hours” setting for downloading the warehouse on-hands. Corrected
Auto-adding of items with multiple vendors may not respect the always primary designation on a vendor. Corrected
Auto-adding of items may incorrectly assign EA1 and EA units of measure. Corrected
An error may occur when two users attempt to recover a temporarily saved PO. Corrected
When drilling down to a customer in a report and changing the email address, the old address will be exported from DataView. Corrected
TransAct may crash while creating a PO generated from the reorder report. Corrected