ITrack/Enterprise/Changelog Version 36

REVISION 23618-23814 database version 3600

Highlights

• Support for advanced Q&A on the work orders screen when filling out Q&A on new serials.
• Improved serial # support on many screens, including their locations and Q&A values
• Clarified and improved loading large numbers of customers or vendors via search to avoid crashes some users were having when running out of memory
• More support for PO accounting
• Signficant improvements to the eBay screen including speed-ups, crash fixes, added tooltips, better keyboard navigation, better naming of ebay shipping types, support for free or charged local pickup, the ability to map listings to local inventory, support for setting listings' Brand and MPN, copying part type templates, and more

General

• Fixed: an issue where lists could not save column order/column widths in lists with a lot of columns.
• Changed: users with very large list controls were finding it very slow to drag and drop items. To improve this behavior without removing precision, the longer the user drags a row in a list in the same direction, the faster the scroll will be.
• Fixed: there was a report that tooltips were not working inside popups. The tooltips would only show if you alt+tabbed away and back, forcing the main window to be focused instead of the popup. This has been fixed
• Fixed: several improvements made to screen based tooltips, including piercing through transparent overlapping windows.
• Added: all top level windows in the application will now respect the windows user's 'darkmode' vs 'lightmode' setting with regards to the title bar.

eCommerce Synchronizer

• Fixed: a crash/error that could occur if there was no local online sales history, which would happen on first run.
• Added: (case 57564) when creating new sales orders, the same default shipping method that would be used by the desktop will now be set on the new document. This is based on a setting in ITrack Enterprise ("Sales Orders"->"Default Ship Method") and hard-coded to None in ITrack Pro.
• Fixed: Store id of 0 is now treated as 'unset', since that is never a valid store id in the system and would trigger foreign key errors.
• Fixed: an issue where if the remote transaction table was missing the paid attribute, it would crash instead of importing documents. Now it should just consider those documents never paid.
• Fixed: (Case 58672) When a new customer is created in ITrack, the customer should now get all payment methods marked as being for new customers assigned to them as available payment methods. Previously, no payment methods were assigned to newly created customers. Additionally, for Enterprise deployments, the customer will inherit the same storeid as the document.
• Added: handling for when the store_id in the config file is invalid. In that case, the new_customer.storeid value is not set, allowing it to remain NULL in the database.

Database

• Changed: (case 56724) support for inventory conditions to be up to 50 characters long.
• Added: (Case 57393) ability to look up Payments by the invoice # they are applied to, OR if they aren't applied
• Fixed: Case 56776 Fast moving "work in progress" serials no longer changes the status to found.
• Added: Case 57967 Recreated WOMP Tag# Filter for the Work Order Source, delete old Master Part Tag# Filter
• Changed: (case 57704) Clarify WORK_CLOCK_ADMINISTRATOR permission must be set at global level
• Added: (case 55752) a new stored procedure for replicating job templates between stores.
• Deleted: several user settings that no longer matter because they have been replaced by global settings that do similar things. Since these settings may be recreated by other users that don't update in time, they'll be deleted again next version.
• Changed: (case 57916) the log_customer_merge table, which logs all customer merge operations has been expanded to keep track of two new flags for tax exemptions and messages.
• Added: log_customer_merge now has a 'set' type column to make what merge operations were performed more obvious than a sequence of binary flags. The previous mergeflags column has been kept for backwards compatibility, but will be deprecated in a future version. A trigger has been added to keep the old merge flag bits in sync with the new mergeoptions set. An insert can reference either one and the other will be updated.
• Added: (case 57916) a new stored procedure p_customer_merge_by_id. This procedure will merge one customer into another. The third argument is a set of operations to perform during the merge; if left NULL, all merge operations will be performed.
• Fixed: p_vendor_merge_by_id did not notify the user if an error occurred during merge. Now any error that occurs will be sent, making it easier to use.
• Added: (case 56723) when creating core banks for a part, instead of assuming a category of 'Core' a global setting will now be checked to see what new cores' category should be. This defaults to Core for backwards compatibility.
• Added: (case 58702) the ability to filter payment transaction list searches by payment #
• Added: a unique key on ebayshippingtype.
• Added: "Local Pickup" shipping type for ebay.

Accounting

• Added: (case 30385) the user can now rebuild Purchase Order accounting in the "Recreate GL Entries" advanced popup. To facilitate this, the recreate dialog now warns the user if they attempt to rebuild PO accounting with the 'delete old entries' checkbox checked, since POs don't support partial rebuilds.
• Fixed: several bugs with the PO accounting rebuild dialog.
• Added: icons to several buttons on the Activity Detail page.
• Added: support for PO accounting with a different effective transaction date than 'now'. Document date will use the PO date, and "date closed" will use the posting date.
• Fixed: (case 58334) performing PO accounting for void documents should now work correctly.

CrystalReportsExtension

• Changed: to avoid confusion, the "Favorite" checkbox in the "Choose report to print" popup has been replaced with a star icon. This dialog appears if there is more than one report option when performing a print job. This will make it clearer that the user is simply choosing a favorite, not checking which report to print.

Customer List

• Changed: it was possible the user could search for so many customers that windows would run out of memory to display items in the list. I tried to make this possibility smoother and less likely to crash. Also, if huge numbers of customers are loaded, their Q&A values will be loaded in batches to avoid query errors.
• Changed: there was a user setting called "Maximum # of results to display". It did not actually control a maximum set of results, but instead caused a warning to appear. This user setting has been removed and replaced with two new global settings:

Search result maximum size (defaults to 5000) Search result warning threshold (defaults to 1000) These two settings control the number of search results to trigger a warning popup and the hard cap on how many results a user can load. This enables an administrator to keep users from doing searches so large that they run out of memory.

• Added: the warning dialog that would appear if the user's search would return too many results has been better formatted and it now tells them the hard cap on number of items to load if their search result will exceed that limit.
• Added: (case 57916) the merge customers dialog now has two new checkboxes for controlling whether to migrate custom messages and tax exemptions as part of a customer merge.
• Added: the merge customers dialog will now merge customer contact tickets if the "Contacts" check is checked. Historically this merged a different kind of customer contact data, but it is rarely used.
• Fixed: (case 59110) a crash that could occur during assessing finance charges when the screen would attempt to calculate the previously assessed month if that month rolled over into a previous year.

eBay

• Fixed: an issue where the default ebay customer might show as a blank if the selected customer had no company contact name. Now the company name is shown, if present, otherwise it falls back on the contact name, and then the customer ID #.
• Changed: (case 56609) double-clicking an auction will now always open in an external browser instead of the internal browser built into ITrack. This is because eBay does not support Internet Explorer anymore and shows an incorrect message that the auction could not be found.
• Fixed: an issue where the user's focus would always come back to 'date range' whenever the user left the auctions page and came back.
• Added: focus is automatically put into the auction list if the default search finds at least one auction. This allows better keyboard navigation.
• Fixed: an issue where sending items from search to a new ebay auction might put the user's focus into the wrong page. This makes it so that the user can immediately arrow through the items sent to the screen.
• Added: hitting enter on the new listings page will automatically pop up the edit item dialog. This makes editing new listings easier.
• Added: (case 42573) support for brand and manufacturer part number on all new listings. These used to always be passed as "Unbranded" and "Not Applicable", but the user can now edit them on any given listing before sending it.
• Fixed: a rare crash when using the enter key to open the currently selected listing.
• Fixed: a display issue that could occur in the rare case that quantity on hand for a SKU was negative.
• Fixed: an issue where a dropdown on the config page wasn't working right. Also, rearrange several default fields to closer match the edit list dialog.
• Fixed: tooltips were not working on the config page. Also added some tool tips to new controls.
• Added: (case 42573) brand and manufacturer part number default fields. These defaults accept template syntax so that a company can decide what format of data they'd like to put in these fields on listings. By default, we ship with a mapping to inventory Manufacturer and Model, but the user can switch to vehicle make or OEM number as desired.
• Added: help buttons next to brand and manuf part # fields to teach the user about templates.
• Changed: shipping type of "Not Specified" and "Calculated Freight" no longer require any shipping methods to be specified, as they don't make sense in these scenarios.
• Changed: renamed the "Not Specified" shipping type to be "Not Specified/Local pickup only" to more accurately reflect its use.
• Added: if "Not Specified/Local pickup only" is selected, the shipping method area will be grayed out and none of the defaults will be transmitted, as ebay doesn't allow shipping methods in this scenario.
• Fixed: a misspelling in "Other Freight service" shipping type.
• Added: (case 58537) it was found that local pickup was not working correctly in some ebay categories. To resolve this, if no shipping methods are passed, a special 'no delivery' option is passed that seems to make those listings work. In addition, a more obvious shipping type of "Not Specified/Local pickup only" has been fixed for those scenarios.
• Added: "Local Pickup" shipping type to ebay screens. This is useful for scenarios where local pickup is available in addition to domestic shipping. Local pickup can be free or not. Some examples have been added to the wiki article at (https://wikido.isoftdata.com//index.php?title=Internal:Ebay_shipping_options#Shipping_Method%2FOption_Combinations) to outline pickup mixed with shipping.
• Removed: a deprecated field in the ebay API ("NoHitCounter"). It isn't causing an error, but it causes an unnecessary warning.
• Added: the part type dropdown in the ebay listing template dialog now shows part type name and number and is an auto-complete for easier selection.
• Added: the ebay template list now shows both part type # and name in the template list. Also, the description field is resized to fill the list and can be clicked into to view all text in a scrollable window.
• Added: keyboard navigation to the ebay template list. Enter edits the selected item, arrows to move around.
• Added: (case 50557) a copy button to ebay template list. When clicked, the selected template and all of its data is made as a new copy and opened for editing.
• Added: when the user adds, copies, or edits a template, their selection will no longer be lost.
• Fixed: if there was an error during template saving, the dialog will no longer close, allowing the user to make changes and retry the save.
• Fixed: an issue where opening the same template multiple times might lead to duplicate shipping options.
• Fixed: broken tooltips in the template list and template edit dialog.
• Added: deleting templates now has a confirmation popup.
• Fixed: a couple potential crashes related to documents and eBay.
• Fixed: tooltips on the auctions page, and added more tooltips.
• Fixed: an issue where loading auctions from ebay with no SKU set at all might incorrectly pull the SKU of a previous auction listing.
• Added: (case 57713) a Map Inventory button. This button allows the user to associate a local inventory record to a remote eBay listing. This is particularly useful when dealing with auctions created outside of ITrack. When this operation is run, ITrack will attempt to revise the SKU stored on the auction listing. If that is impossible (because the auction is closed/ended) the mapping will be created on the ITrack side only.
• Added: doubleclicking a red "<NOT FOUND>" cell for items not found in inventory will automatically perform the Map Inventory function for faster inventory mapping.

Locations

• Fixed: a crash that could occur if the user selected a box not associated with a Location
• Fixed: an issue where clicking boxes would not select the correct location unless the user clicked the location tree first.
• Fixed: an issue where deleting a top-level box or text would not save due to order of operations during the delete.
• Fixed: (case 57653) an issue where location codes were being cut off at 10 characters when it was supposed to cut off at 50.
• Fixed: (case 58167) the code that checks whether the system has 'virtual' locations enabled or not will now check both "Enforce Location Heirarchy" as well as "Enforce Location Hierarchy". This will allow us to rename the setting in a future version without causing any issues with users checking different settings for this value.

Login

• Changed: the password recovery popup has had several labels reworked to make the password recovery process more obvious.

Parts

• Fixed: (case 57402) an issue where cloning a part would move all alternate part lookup rows to the newly created part instead of copying them to the new part. Now they are correctly copied.
• Added: (case 56724) support for inventory conditions up to 50 characters long.
• Changed: (case 57369) if the user changes part types, if any of the 4 'flex' fields are filled out, if the new part type has any fields with the same names, the values will automatically 'carry forward' instead of being thrown out. If the flex field titles don't match, the value will still be lost.
• Added: (case 56778) a print tag button next to the serial # list.
• Fixed: the 'choose tags to print' popup should no longer select items other than the suggested serials on first load. This was leading to the wrong serial tag printing in some scenarios.
• Fixed: an issue where printing serial tags might not uncheck the 'print tag' checkbox on the Q&A tab correctly.
• Added: the 'choose tags to print' popup will now load unavailable serials if specific serial #'s are being passed in to print.
• Changed: if the user closes a serialized part and all that has changed is the 'locations' tab, the user will not be shown any change detection popup. This was happening because the system was rebuilding location quantities based on serial #'s whenever the user opened the screen. Now they won't be bothered by this automatic recovery process.

Part Configuration

• Added: support for selecting more than one question in the inventory question list. This makes moving groups of questions easier as well as mass-deleting.
• Added: (case 57354) the inventory options/questions area now has send up/down as well as send to top/bottom icons next to the question list. These buttons allows the user to send one or more questions up or down in the list easily.
• Added: tooltips to inventory question edit area.
• Added: the inventory question filter box now filters by part type, part type number, category, manufacturer, and model in addition to the question text.
• Fixed: an issue where using the up/down arrows to move Q&A options around would not keep those items in view. Now the user will be scrolled to follow the item.
• Added: improved moving Q&A options around in the list using drag & drop. Namely, if the user has a very large list, the longer they drag an item, the faster the list will scroll, making large lists easier to manage.

Part Modification

• Fixed: (case 57882) a minor issue where deleting a column in the part mod screen on the right would not redraw the main list content to the right of that. This would lead to weird display issues until the user caused the list to redraw again.

Purchase Orders

• Fixed: an issue where 'created by user' box would be blank on newly created serials on the TO tab.
• Changed: serials will now show "NONE" for the created on document instead of "NONE 0-0 #0"
• Changed: serials created on the currently document will now show "Transfer Order N/A" instead of "Transfer Order -1"
• Fixed: a bug where transferred serials would get the wrong locationid at the destination store if the location name the serial was being received into matched a location at the source store.
• Fixed: (case 58009) several minor issues that could occur if the user loaded an inventory item onto a PO, then went back into the lookup field and loaded a miscellaneous item from the vendor catalog. Some of the behind-the-scenes info from the inventory record would end up saved on the misc item, most notably the tag number. This could lead to some confusion about which item was being purchased.
• Fixed: (case 58334) voiding a PO now properly reverses all previous accounting activity. This adjustment will show as "purchase order voided" event on the accounting history screen.
• Fixed: (case 58380) an issue where attempting to search for a vendor by the vendor number would only use the first digit, leading to incorrect results. Now looking up vendor by # should work correctly. This issue affected vendor lookups on the Inventory Overview and Vehicles screens as well.

Quickbooks

• Added: (case 58828) previously, PO accounting was not included in QB exports. Now PO accounting is allowed in exporting, as the company has a separate setting for controlling whether to generate PO accounting if they wish to skip PO accounting.

Sales Orders

• Fixed: (case 57556) the gl accounting for adjustments is now refreshed when the user saves an open sales order. This fixes issues where adjustment types have had their gl account changed and open SOs did not grab the new account when finalized.
• Fixed: (case 57835) an issue where return documents using a two-tier tax item would not correctly tax the amount above the break point.
• Fixed: if a tax quote failed because the ITrackOnline module was not loaded, the screen would show "Calculating..." forever instead of showing an "ERROR" output. Now the user is shown an error correctly.

Search

• Added: (case 57699) "range search" options on the part search such as "Quantity Through" now show up in the search defaults tab so that users can choose to save range based options as a default.
• Fixed: (case 58057) an issue where the user-assignable hotkey for "send selected items to part modification" could not be set in the configure hotkeys dialog. The default hotkey was also incorrect and collided with the POs hotkey, it now defaults to Ctrl + D.

Vendor

• Fixed: (case 58096) an issue where the user was allowed to enter vendor codes up to 10 characters long, but only 8 were allowed to save. Now the user is restricted to 8 characters correctly.

Vendor List

• Fixed: (case 58258) a couple edge cases where the vendor search results might show vendors not assigned to the current user as a purchase agent. Namely, smart searches that found a result by alternate address were ignoring this restriction as well as searching for vendor by vendor id.
• Changed: it was possible the user could search for so many vendors that windows would run out of memory to display items in the list. I tried to make this possibility smoother and less likely to crash. Also, if huge numbers of vendors are loaded, their Q&A values will be loaded in batches to avoid query errors.
• Changed: there was a user setting called "Maximum number of vendors to display". It did not actually control a maximum set of results, but instead caused a warning to appear. This user setting has been removed and replaced with two new global settings:

Search result maximum size (defaults to 5000) Search result warning threshold (defaults to 1000) These two settings control the number of search results to trigger a warning popup and the hard cap on how many results a user can load. This enables an administrator to keep users from doing searches so large that they run out of memory.

• Added: the warning dialog that would appear if the user's search would return too many results has been better formatted and it now tells them the hard cap on number of items to load if their search result will exceed that limit.
• Fixed: (case 58385) a regression where vendor smart searches for using vendor code were not working. This was originally caused by a desire to make vendor list match customer list search, which searches by # only. To match the PO screen's vendor lookup and the previous behavior, vendor smart search will now look for exact matches on vendor code (if any are found, stop searching and show results), if that finds nothing, the normal smart search will be performed. To facilitate 'new' style searches by vendor #, the vendor # is now part of the main smart search. This should bring vendor list smart search behavior into parity with the PO screen's smart search box.

Vehicles

• Added: per user request, the vehicle email dialog now has the Odometer reading as an option.
• Changed: (case 57369) if the user changes vehicle whole unit types, if any of the 4 'flex' fields are filled out, if the new type has any fields with the same names, the values will automatically 'carry forward' instead of being thrown out. If the flex field titles don't match, the value will still be lost.
• Fixed: (case 57530) a bug where loading a vehicle with no purchase date would change the purchase date to 'today' which would be saved if the user hit save. This was only true if the "Purchase date automatically set to title received date" setting was set to False.
• Fixed: (case 56489) an issue where really long categories (longer than 20 characters) would not be saved on bid items. This could cause issues when converting the bids into a teardown and that teardown into inventory records.
• Added: (case 58265) when the user builds an email from the vehicle screen, vehicle type name (labeled Vehicle Type) is now an available piece of information to put into the email.
• Fixed: an issue where accepting a bid, even if the user unchecked the 'change user status', the user status would still be updated.

Work Orders

• Added: (case 57692) previously, it was possible to reopen a WO that had already sent its jobs to an open invoice, add more jobs, and re-finalize. The new job(s) would not be invoiced, so accounting would not complete, leading to confusion. Now, if the user re-finalizes a WO after sending its jobs to a SO, any new jobs will also be sent to that same invoice automatically. If a historical WO is in this state, the user can click the 'open associated invoice' button on the WO screen, and any missing jobs will be sent to the current open SO. Then, upon finalization of the invoice, all jobs will be present and accounting will be created correctly.
• Fixed: an issue where the icon on the edit unit/master part button was very small.
• Fixed: an issue where editing a master part, then clicking cancel would lead to an incorrect attention icon.
• Fixed: tab order in choose serial # popup.
• Fixed: some weirdness that could occur if the user created a new serial # on an item that already had a serial # chosen.
• Fixed: new serial #'s should get default Q&A correctly.
• Fixed: the user should be able to edit Q&A on the selected serial # correctly now. This uses the new dynamic Q&A system added recently. Per-serial option defaults, modified value indicators, required value indicators, choice lists, etc should all work now.
• Fixed: changing Q&A values for the selected serial # should save correctly now.
• Changed: (case 55753) significantly reworked the 'choose serial' pop-up. Now, there is a serial location dropdown above the Q&A and it lets the user set the location of the chosen serial #. This makes it so that a serial being created or consumed on a WO can have its location changed even after the serial was first created. This is useful for setting a final location on serials created by a WO master part.
• Fixed: several issues where changing the location or Q&A of a serial on a job part would not save or display correctly.
• Fixed: several issues where the 'locations' on a job part would not recalculate correctly if the user changed the location of the serial that was chosen.
• Fixed: an issue where changing the location of a serial on a WO master part would not work correctly during the finalization process.
• Fixed: an issue where the 'add multiple jobs' button was clickable even on closed WOs.
• Fixed: tool tips were not showing up in the new job/edit job popup. This has been fixed and several tooltips have been expanded and clarified, especially around the function of the shop fees box to make it clearer it can be either a fixed $ amount or a %.

v36.0.1

Changes:

• Fixed: (case 59367) an issue where deleting a serial with Q&A answers might make the "Default Q&A answers" list get cleared out. Also, fixed an issue where deleted serials might complain about missing required fields.
• Fixed: (case 59383) an issue on sales orders where inventory adjustments that 'found' inventory would sometimes not get cost assigned from the original 'loss' if something from the original adjustment document had already been found. Now every line quantity is able to be claimed and returned separately, fixing a situation where found items would come back in with $0 cost even though a valid previous loss existed.