ITrack/Enterprise/Changelog Version 19

Release 19.0

Important

• Added: (case 28363) support for European style numbers and currency figures. Mainly, if the user's windows settings are set to use comma instead of period for the decimal separator, the software will correctly read and display figures.
• Added: (case 26026) POs now track the customer and vendor address that was selected. Also, POs always have a destination store, even when they are dropship POs.
• Changed: the UI for the PO header has been reworked to make data entry faster, clearer, and easier to read. In addition, the screen now follows the format of other screens more closely, and we have fixed hotkeys on the screen and added tooltips for various controls.
• Fixed: better keyboard navigation on document screens, and more tooltips.
• Changed: many database changes to help avoid deadlocks and lock wait timeouts. In addition, ITrack automatically retries deadlocked queries and queries that received a lock wait timeout without any user input. That way, during high contention periods, some operations may take longer, but the user should receive fewer error messages.
• Added: on document screens, double-clicking order request and order fulfillment icons now takes the user to document fulfilling/requesting that stock.
• Added: (case 27799) SOs and WOs in the home screen lists now show how 'ready' the document is (based on quantity being sold that is on hand). Also, another column has been added with what % ready the document is; this percent is colored blue for 100%, red for <100%, and green for <100% if an open order request is on the document.
• Added: (case 14034) performing a search including an interchange number and a sub-interchange number now orders the results by whether they are an exact match or not. Exact matches are at the top, and are shown with a small icon next to the interchange # to make this clear.

General

• Added: (case 28363) support for European style numbers and currency figures. Mainly, if the user's windows settings are set to use comma instead of period for the decimal separator, the software will correctly read and display figures.
• Changed: made function calls more specific to distinguish between operations that operate on raw numeric strings, user formatted numeric strings, and database strings.
• Added: various locale currency and number API functions for reading windows API locale settings.
• Changed: (case 28837) several database function calls have been transitioned to stored procedures to avoid database deadlocks.

Customer List

• Fixed: (case 26032) an issue where fulltext searches in boolean mode might throw MySQL errors in certain circumstances.

Database

• Renamed: (case 26100) f_monthly_inventory_sales has been renamed to f_inventory_usage_monthly, to more closely match other usage functions. References to the function in inventorysetting have been updated as well.
• Added: (case 27629) a vehicle id to all the pickable item views.
• Fixed: dropped several alternate names for a trigger that was dropped in version 18. This should resolve issues where different databases had different names for this trigger.
• Added: Case 27948: Add Worker Group as Display Field to Transaction List
• Added: an index to documentlinelocation that speeds up f_location_refresh significantly.
• Fixed: f_location_refresh now no longer throws an error if manual merging of locations causes duplicate entries on document locations.
• Added: (case 28539) a new function, f_merge_location, which accepts two locations and a storeid. All tables that reference the old location (or its id) will be moved to the new location (and id). An optional parameter dictates whether the old location should be deleted or not at the end.
• Added: (Case 285583) Schema creation queries added for Customer Response Management subsystem.
• Changed: some purchase order views to properly use the new destination columns.
• Added: (Case 28811) Add "Days In Inventory" as Display Field to Transaction List
• Changed: (case 28837) many database functions that change data have been moved to stored procedures to help avoid deadlocks.
• Added: (case 28837) all the document saved stored procedures now explicitly acquire all necessary write locks at the start to ensure they do not perform half of their queries and end up in a deadlock situation.
• Added: p_purchaseorder_void and p_transferorder_void stored procedures that properly reverse activity performed by those documents.
• Added: (case 28837) all stored functions call the new stored procedures for backwards compatibility. There is a @DEBUG session variable, which, if its TRUE, will throw exceptions instead. This will help finding and eliminating these calls.
• Fixed: p_document_allocation_refresh wasn't updating location holds right.
• Added: DB API function: p_salesorder_undo, which can reopen or void a SO that has been closed. This is now shared code between the ITrack SO screen and several scripts that also perform reopen actions.
• Changed: log_inventorytransaction is now engine type InnoDB, it appeared to be MyISAM still on some customer dbs.
• Changed: inventorymove is now engine type InnoDB.
• Changed: the address table has been renamed to workorderaddress to make usage clearer to people writing queries. Renamed several columns to match other address tables.
• Added: for backwards compatibility, there is now an address view, which attempts to emulate the old address table.
• Added: workorderaddress now remembers the customeraddressid the user chose.
• Added: Case 28813: Add Inventory Category as Filter to the Transaction List for the Inventory Source
• Fixed: the trigger on inventory update now sets locationid based on changes on the location field.
• Added: (case 28976) p_inventory_move_inventory_location the move operation now works if the item in question had 0 quantity on hand at a permanent location. Also, if the old primary location was permanent, so too is the new primary location.
• Removed: a couple triggers that existed on some databases that updated a log that we are deprecating.
• CHanged: log_vehiclechange and log_inventorychange_expanded have been deprecated. These logs only existed on some customer databases and have been superceeded by more modern logs. They will be removed out eventually.
• Added: (case 29272) vendorcatalog.vendorproductcode is now part of the vendor catalog import.

Data Management

• Changed: the database that backup tables are created in now defaults to the current database instead of `backup_importer`. This is because not all customer setups are able to create or put tables into other databases.

Deliveries

• Added: (case 27629) a vehicle stock # to the pickable line item view.

eBay Extension

• Fixed: Payments now correctly load into listings again.
• Fixed: (Case 28774) Free shipping checkbox removed. Free shipping is now determined by shipping cost being $0.00 or not.

Home

• Added: (case 27799) SOs and WOs in the lists now show how 'ready' the document is (based on quantity being sold that is on hand). Also, another column has been added with what % ready the document is; this percent is colored blue for 100%, red for <100%, and green for <100% if an open order request is on the document.
• Added: (case 27799) SO and WO lists now have an attention column which shows icons (with hover tooltips) similar to the document screens. Currently, this will show when a document can not be finalized due to insufficient QoH, as well as when there are open order requests and fulfillments.
• Added: (case 27805) SO Truck # column to the SO home screen.
• Removed: INI setting for the home screen URL, and moved it into a global setting.
• Removed: INI setting for the home screen minimum height, and moved it to a global setting.

ITrack Online

• Changed: the home page for the online page now defaults to a URL set a user preference, instead of a default from the ini.

libITSQLFramework

• Fixed: an issue where the 'footer' of a query in the query log would be written sometimes after another query run in order to report the error.
• Added: (case 28838) if a mysql connection gets a lockwait timeout error (1205) the query in question will automatically be silently retried up to 2 times before the user is presented with an error report. This should result in the user seeing fewer of these errors, though it does not necessarily make the error itself more rare. Auto-retry is MySQL's suggested error handling method in these cases.
• Added: (case 28838) if a mysql connection gets a deadlock error (1213), the query will automatically be silently retried up to 2 times before the user is presented with an error report. Unfortunately, this will not happen on queries that are in the middle of another transaction. This is because deadlocks automatically roll back the entire transaction, requiring the operation be retried.
• Added: query errors are now logged to the query log. Also, auto-retries and auto-reconnect operations get a special log entry for better debugging.

Location

• Fixed: (case 28088) a possible crash when adding new locations to the location tree.

Login

• Added: (case 28838) support for a special debugging mode in the database.

Master

• Added: the RemoveInitSetting function now returns the last found value before deleting it. This allows a relatively common case where we take the value from an ini setting as we delete it an move it into a database setting.

Parts

• Added: (case 23575) a checkbox to show/hide historical serial #'s that are not on hand. This checkbox remembers the user's preference.
• Added: (case 23575) an edit the user can type into to filter the serial # list.
• Added: (case 23575) the serial # filter list now can filter by the document # the serial was created and last used on.
• Added: (case 23575) the parts' screen's transaction list area now has a serial # column that shows all serial(s) that were referenced on a particular document. This should make finding documents that purchased/sold a serial # easier.
• Added: the Q&A tab now has tooltips to explain the new filters as well as the old fields.
• Fixed: (Case 28563) hitting enter while typing into the comments field in the change log would not close the dialog. The user had to hit escape first to close the comments edit.
• Fixed: an issue where the user could not enter fractional quantities for the quantity on hand, as well as minimum and maximum stock quantity.
• Fixed: weight can now have a precision of 6 digits, as intended, instead of just 2.
• Fixed: (case 25918) an issue where an assembly breakdown might distribute costs in a strange way if the user used ratios, and took several days before finalizing the WOs (and the assembly had cost added to it).

Purchase Orders

• Changed: (case 27772) recent updates removed the 'send electronic PO' system from PO saving. This has been added back in, but instead into the advanced option dropdown. This will transmit the last saved version of the PO.
• Fixed: the prompt to save message on the PO screen now match other screens' prompt to save.
• Added: the "send electronic PO" options in the advanced button now prompt the user to save the PO first.
• Fixed: (case 27979) adding a serial # to a PO or TO will now try not to set the 'used on document' field on that serial # if that serial has already been sold.
• Fixed: apparently transfer orders using order requests have not been working correctly since 2007. They were being saved, but not loaded. This may have disrupted multi-branch purchase orders, as a central PO supplied stock to transfer order to other stores.
• Fixed: on POs, if a user was hot ordering lineitems for an item in inventory where the tagnumber, manufacturer, or model had changed would not group those rows together when ordering. Now, the current tagnumber, manufacturer, and model are used.
• Added: (case 27751) double-clicking the 'open order requests' icon on an item now opens the fulfilling document if there is at least one open request with at least one fulfilling document. Otherwise, it opens the edit order requests dialog.
• Added: (case 26026) support for several new purchase order fields, including the id of the customer address that is the destination of the PO and the id of the vendor address that is the source.
• Changed: many tooltips have been updated to be more accurate and concise, and controls that were missing tooltips have had them added.
• Changed: the UI for the PO header has been reworked to make data entry faster, clearer, and easier to read. In addition, the screen now follows the format of other screens more closely.
• Fixed: (case 26025) an issue where drop-ship POs would not show the destination store of the PO or allow the user to choose it. This was causing issues where it would always assume the PO was going to the logged in user's store. Since drop-ship POs' inventory is still received into the destination store's inventory (so it can be sold to the customer), choosing the store is important.
• Changed: the user can no longer change the destination store of a PO after it has been saved or a PO # has been generated. This is to get rid of situations where a PO at store 3 will have a destination of store 2, undermining the meaning of the 'owning' store of the document.
• Added: more keyboard shortcuts for jumping around the screen. Also fixed situations where using a hotkey might take the user to the wrong control.
• Changed: background color of the address boxes has been changed to look more like other read-only fields.
• Added: the exact vendor address and customer address (for drop-ship POs) that the user selects will be remembered when the PO gets saved/loaded. This will now work even if the address gets updated on the PO or the customer/vendor screens. Previously a modified address would always show "Saved address" in the dropdown, keeping the user from knowing which vendor/customer address had been chosen.
• Fixed: customer billing address is now always available as a choice for destination address for drop-ship POs. Previously only shipping addresses were available.
• Changed: the transfer orders page has been re-arranged to work and look similar to the PO tab with tab order.
• Added: tool-tips to all controls on transfer orders, and better keyboard navigation on TOs.
• Fixed: the chosen vendor order address is now properly remembered when the user saves the PO, same as the shipping address.
• Changed: the TO # field is now grey like other read-only fields. And it displays a bold #, and "New" for an unsaved transfer order.

QuickBooks

• Fixed: (case 26025) an issue where a query error would appear when attempting to mark gl entries as exported.

Report Viewer

• Fixed: a possible crash that could occur when previewing a report if some very rare memory issues happened.

Reports

Billing Statement

• Added: (case 27926) when the report is run for a single store and the customer has a balance at other stores, a message is displayed at the bottom of the report.
• Changed: (case 27655) swapped vertical positions of customer companies and names
• Changed: (case 27932) report now uses the return address, remittance address, and logo from the store running the billing ({?storeid} parameter) unless it is billing centrally, in which case it uses a new setting to determine return store - default 1. Previously, it used customer default store/store 1.
• Fixed: (case 30901) cleared report links causing omissions for customers where default store was not store 1 when running central billing for multiple stores.

Customer Address Label

• Changed: (case 27655) swapped vertical positions of customer companies and names

Customer Address Label 5160

• Changed: (case 27655) swapped vertical positions of customer companies and names

Delivery Picking List By Document

• Changed: (case 27655) swapped vertical positions of customer companies and names

External Work Order

• Changed: (case 27655) swapped vertical positions of customer companies and names

GL Activity

• Fixed: (case 28467) finished replacing the deprecated field.
• Changed: (case 28477) payment store displays and is filterable

GL Entries By GL Account

• Changed: (case 28477) payment store displays and is filterable

Outstanding Cores

• Changed: (case 27655) swapped vertical positions of customer companies and names

Packing Slip

• Changed: (case 27655) swapped vertical positions of customer companies and names

Payment Receipt

• Changed: (case 27655) swapped vertical positions of customer companies and names

Pick List

• Changed: (case 27655) swapped vertical positions of customer companies and names
• Fixed: (case 28604) Misc line items are no longer excluded. Store column will be blank for Misc items.

Purchase Order Posting Report

• Fixed: (case 28520) subreport links
• Fixed: (case 28520) number formatting for storeid and purchaseorderid

Purchase Orders

• Added: (case 27542) user parameter
• Changed: (case 27542) column references to prepare for upcoming changes, tidied the report

Receiving Label

• Fixed: (case 28409) Model always referencing vehicle model, instead of part model where appropriate.

Sales By Customer Default Store

• Added: (case 27969) a new report that shows sales by customer default store. It can be filtered by customers with no default store.

Sales Order 11in

• Fixed: (case 27935) changed partnumber displayed to show lookup instead of (tagnumber, unless there is no tagnumber, then lookup)
• Changed: (case 27655) swapped vertical positions of customer companies and names

Teardown

• Fixed: (case 27622) flex field formatting to use underlined spaces instead of underscores due to linebreaking when the report was sent to a printer

Transfer Order

• Fixed: (case 28594) barcode formatting.

Unreceived Purchases

• Changed: (case 27542) major report layout overhaul, improved organization
• Added: (case 27542) vendor and user parameters
• Removed: (case 27542) the / between Ordered and Received columns

Sales Orders

• Added: (case 27751) double-clicking the 'open order requests' icon on an item now opens the fulfilling document if there is at least one open request with at least one fulfilling document. Otherwise, it opens the edit order requests dialog.
• Changed: (case 27751) double-clicking a fulfillment line in the order request popup dialog now opens the fulfilling document on that screen and closes the popup.
• Fixed: an issue where using a hotkey (alt + the letter underlined in a label) for the 'boxes' at the top of the screen would not take the user to the correct control.
• Fixed: (case 28544) an issue where serial #'s at virtual locations counted as being at non-sellable locations.
• Changed: the reopen and void operations on a SO now use a shared database procedure called p_salesorder_undo. This should standardize code between ITrack and other scripts that perform this task.
• Changed: voiding a SO no longer lets the user choose whether they'd like to not undo changes to inventory or document adjustments, as these are required parts of the document.
• Added: double-clicking the insufficient available/on-hand quantity icon now asks the user if they'd like to back order quantity or create an order request instead of assuming back order.

Search

• Added: (case 14034) performing a search including an interchange number and a sub-interchange number now orders the results by whether they are an exact match or not. Exact matches are at the top, and are shown with a small icon next to the interchange # to make this clear.

Updater

• Fixed: (case 28086) an issue where a query that was missing a close parentheses ")" could keep subsequent queries from being parsed correctly, even though it had a semicolon.
• Fixed: an issue where an open, unclosed parenthesis might disrupt the rest of the parse if it was in a function definition.
• Added: in debug mode, Master will now write all script files to the updates directory. In addition, the intermediate query string is written to ComprehensiveUpdate.sql and the parsed query list is written to UpdateQueryList.sql

Vehicles

• Fixed: an issue where saving a vehicle might throw an error if certain values were longer than the database allowed.

Vendor List

• Fixed: (case 26032) an issue where fulltext searches in boolean mode might throw MySQL errors in certain circumstances.

Warehouse Management

• Changed: (case 28837) several database function calls have been transitioned to stored procedures to avoid database deadlocks.

Work Orders

• Added: (case 27751) double-clicking the 'open order requests' icon on an item now opens the fulfilling document if there is at least one open request with at least one fulfilling document. Otherwise, it opens the edit order requests dialog.
• Fixed: (case 28553) an issue with the tab order in the job dialog.
• Fixed: (case 28906) an issue where SOs created from closing a WO would not set the customer's default terms, default salesperson, or default backorder/partial shipment preferences on the newly created invoice.
• Fixed: the address dialog now properly shows notes as you switch addresses.
• Added: work orders now save which customer address the user chose, even if it gets modified.