Bug Fixes and Minor Adjustments

• Changed kits to set the product field (strProductID2) to “Comment” or “Bundle” rather than leaving them blank.
• Fixed the Dispatching Daily Transfers screen to stop multiplying transfer weight by the unit measure qty.
• P10: fixed to let the user set the cost to zero on an existing order line.
• Fixed: the cost rate to on a voucher detail line was getting rounded to the penny. (mainly seen when changing the unit of measure).
• Fixed: in certain situations, job transfers were trying to create receivables when posted.
• P10: the pricing adder on items with model options was getting added multiple times if user edited the model options a second time.
• P10: fixed issue where orders with a salesman of “Web” would throw an error when saving.
• P10: fixed issue where the “paper out” checkbox was not getting set for orders that were not on a trip, when the user printed the paperwork.
• P10: Fixed: Editing the product ID on the first detail line on a transaction, directly after opening the order was not updating the description on that line.
• P10: Added a back button to the universal search. Also added a button to open the CTRL+F popup. Also cleaned up some formatting and icons.
• P10: Fixed: the “Open Orders” and “Open Quotes” poups were not including estimates or backorders. Also fixed the missing “Edit lock” warning on the “Open Orders” popup.

Feature Additions and Major Changes

• P10: Added percent pulled/percent shipped progress bar into dispatching order list: this is very similar to the progress bar found in Fulfillment Pro.

Bug Fixes and Minor Adjustments

• The average cost field on Inventory items (used in some reports), will now use overall average rather than just the average from the last used warehouse.
• Added more indexes to speed up lot-related posting tasks.
• P10: Fixed: Prepayment history tab payments were showing as negative rather than positive.
• P10: fixed kit lines: it was using a comment line as the top line even if it was a bundle kit.
• P10: Fixed: sorting and moving the top line of a Kit to a different spot on the order was creating a second set of kit lines.
• P10: when pressing the “Open in Paradigm 9” button on an order, it will leave edit mode in P10, to avoid any editing conflicts.
• P10: Cleaned up the model option form to better handle if they change the warehouse on that line. Also made the reset button work in the model option popup.
• P10: Fixed issue where attempting to open a transaction that was already open would create an invisible copy of that transaction which could conflict with the changes made in the visible transaction view.
• P10: Fixed: if user clicked in the month part of the date field, entered a single digit month, and then clicked in the day portion, it was only allowing a single digit day (unless user retyped date).
• P10: Audit trail will not log email tables.

Bug Fixes and Minor Adjustments

• Fixed: if a user selects a new product , and the lm1/lm2 from the previous product are outside of the new linear measure min/max, it will set them to defaults.
• Fixed: distributing freight/other values as a discount on a voucher was not removing the original freight/other amount on the voucher.
• Fixed: when posting an invoice or voucher, it will validate that all accounts involved in the posting exist.
• Canceling or un-releasing an order will not be allowed if the order is on a trip.
• Fixed: updating the address on an order with a job should not use the state tax code to override the selected tax code gotten from the job.
• In the history tab of the customer form: changed to look at prepayments to determine if order should be marked as paid.
• P10: Fixed: Editing quote list filters and RFQ list filters did not work.
• P10: Fixed: ship to address was not getting populated on quote/order/invoices when selecting the customer.
• P10: Added a preference to disable the load date getting automatically set on new trips in dispatching.
• P10: Changed address map lookup to not add unnecessary commas in the URL if part of the address is missing (for example, if user entered coordinates as the address).