Changelog

Release 15.2

Sales Orders

• Fixed: (case 25263) an issue where (while selling a vehicle) the "choose parts to leave in inventory popup" would end up putting cost onto the components left in inventory equal to the amount already allocated to these parts. This had the effect of doubling the intended allocation of cost onto the components left in inventory.
• Fixed: the popup for choosing which vehicle components to leave in inventory now correctly calculates the remaining/unallocated vehicle cost. In addition, this popup now properly takes into account the company settings that control whether cost and/or average cost are considered when computing the amount of vehicle cost 'allocated' to parts off of that vehicle. If the user updates the 'cost' field in this popup, the difference will be put into average cost or cost, depending on which the company uses to store vehicle cost allocations. The cost field on this popup is not editable if the company does not consider either field when dealing with vehicle cost allocations. The tooltip on the cost column has been changed to more accurately reflect its use.
• Fixed: if the user sells an assembly with components that are in stock (and chooses which 'child' components to leave in stock), the cost of the assembly on the invoice should no longer be set to 0.

Release 15.1

Master

• Fixed: if the user is looking at the update download dialog and they do Actions->reset updates, the dialog is no longer closed and reopened.
• Fixed: (case 25241) a crash that could happen if the user hit "Hide" on the update download dialog, and then the system automatically checked for updates again in 5 minutes.

Sales Orders

• Fixed: (case 25042) an issue where the first item that would be added to an existing SO would get a quantity of 0 if the user did not explicitly set it to anything else.

Work Orders

• Fixed: (case 25184) when a WO that has not been finalized is loaded, all calculated values are now recomputed. This fixes an issue where WOs with work clock entries might not re-compute shop supplies when t hey are a percent of the labor charge.

Release 15

Highlights

• Work orders can now be reopened with proper permission. This works similarly to reopening sales orders.
• Work orders and sales orders save and reopen processes now happen inside a single database transaction, meaning if there is an error or database interruption, the entire operation will be rolled back, preventing issues where partial finalization was possible. (Similarly approving jobs on the warehouse management screen are inside a single transaction now)
• Accounting entries tab improved filters
• Items with average core cost that is non-zero now automatically add core charges to sales order and work order lines. Also, inherent core lines with a non-zero cost cannot be deleted from documents. This is to prevent 'losing' core inventory value.
• Various improvements to right click graphing, including fast-viewing of saved graph templates.
• Update downloader is now less intrusive and can be hidden permanently by unchecking the "show this dialog in the future"
• Exporting vehicles to berryhill auctions now supported
• Purchasing and transfering serials is much smoother now, and the status of the serials should make more sense in these cases. In addition, if the TO is not marked as ordered yet, any serials on that document should still be available at the source store.
• Vehicle costs/performance on the vehicle screen have been made more accurate. Final and projected costs should match the documents better, and the values are now colored (vehicle cost shows in red if total COGS exceeds it)
• Vehicle costs now includes inherent core charges from vendors as well as dirty core returns to the vendor, as both of these now affect a vehicle's total cost pool.
• Many improvements to the vehicle break even graph to make it more accurate and usable.
• Better show/hide hotkey support for the image popups on the parts and vehicles screens
• Added support for entering third party shipping tracking #'s and to have shipping progress web pages opened. URLs have automatically been added for many common shippers, and users can customize them if they'd like to send tracking URLs to their customers.
• Appraisal support for part collections, such as assemblies.
• Support for a separate customer memo for printing onto invoices based on invoice payment terms.
• Added a new setting ("Work Orders"->"Master part costing: put core inventory items' cost into average core cost") that controls whether inventory core bank items (inventory marked with "Is A Core" checked) have their cost put into the core cost of master parts. This was existing functionality that was always on before. This setting defaults to True.
• Added a new setting ("Work Orders"->"Master part costing: put inherent/dirty core line items' cost into average core cost") that controls whether inherent core charges have their cost put into the core cost of the master parts. This is new functionality. This setting defaults to True.
• Counting 'single quantity' parts (like whole units or vehicle parts) now always moves the part instead of ever putting any quantity in variance (lost and found)
• Better ability to manage the location serial #'s created on WOs go into.
• The user's work is now saved if they hide the assess finance charges dialog. This makes it much easier to go back and forth between that popup and the customer and SO details. (TIP: when this dialog is up, you can interact with the rest of ITrack without closing it)

Accounting

• Fixed: (case 23071) an issue where the document type dropdown on the entries page of the accounting screen did not correctly filter down to gl activity on sales orders of the specified document type.
• Changed: the entries tab has had its document type dropdown replaced to allow the user to choose types of Enterprise documents instead of just sales order document types.
• Added: the entries tab now has filters for document store, document # range, and a checkbox for filtering out entries that have not been exported yet.
• Added: the date range filter of the entries tab now allow both date and time.

Appraisal Extension

• Fixed: a possible database error caused by invalid inventory type #'s in sales appraisals.

Approval

• Fixed: Removed an unnecessary popup if the user did not have permission to the credit approval screen.
• Removed: a redundant permission for controlling whether a user can perform credit approvals.
• Added: (case 24131) the price approvals tab now uses the list of stores the user has permission to approve prices at to build the list to display. This allows users to be granted permission to approve prices at more than one store.

Common Resources

• Fixed: the picture pop up dialog now allows the user to use global hotkeys.

Core Management

• Fixed: (case 23406) the part type dropdown was not usable.

Crystal Reports Extension

• Fixed: an issue where the advanced print dialog would sometimes appear when the user was previewing a report, if the user had no default printer set for that report type.
• Changed: holding the advanced print button while previewing a report will no longer show the advanced print dialog, as previewed prints don't pay attention to most of the options.

Customer

• Fixed: an issue where the configure regions dialog might show items incorrectly.
• Fixed: (case 22957) an issue where, if the user edited an existing payment and changed its payment method, the gl that that payment hit didn't get modified. Now, it is updated if and only if the payment method changes, causing accounting to be corrected to match.
• Fixed: (case 23102) an issue where the user could cancel a payment that had been entered through the credit card terminal.
• Added: if the user uses the next/prev arrows when no search had been done, a message is displayed, like on the vendor screen.

Customer List

• Changed: (case 23171) customer smart searches with multiple words will now automatically require all words to be present in the results.
• Fixed: customer smart searches now correctly order results with the 'best' matches at the top.
• Fixed: (case 23407) an issue where the application could crash if the user uses the next/previous arrows when no search had been done.
• Fixed: (case 24250) an issue where the assess finance charges dialog could crash if the user searched, viewed a customer or invoice, closed and reopened the dialog.
• Changed: the close button on the assess finance charges dialog is now labeled "Hide". If the user hides the dialog and comes back, their work is saved.
• Added: minimize/maximize buttons to the assess finance charge dialog.

Database

• Removed: some settings that are not used anymore.
• Changed: added a default to the salesorderline.type column so that new rows won't get NULL.
• Added: several inventory import fields that were missing from some databases.
• Fixed: (case 22334) an issue where instances where there were multiple parts with the same tag # might throw off an inventory import updating those rows.
• Added: (Case 22934) A new function fhasaging, which tells the caller if a given customerid has any data worth checking aging on. Used for aging report performance improvements.
• Changed a previous update to ensure that the list control graph template exists, no matter what.
• Added: as per suggested by Chad@VHI, the queries that added a unique index to to scanjobaction will now remove duplicates first.
• Added: (case 22915) when the user transfers any 'single quantity' items (monolithic parts as well as vehicles) between stores, all open SOs and WOs that have that item on hold now have their lineitems transitioned to point to the item at the destination store and use the location at the destination store.
• Fixed: an issue where the vehicle bid item table was not allowing full-length categories to be saved in the table.
• Changed: (case 23306) add-on core costs now properly factor into vehicle cost pools. Also, add-on core costs now count as allocated vehicle costs.
• Changed: (case 23306) inherent cores on vehicle items can now have add-on costs that pull out of the vehicle cost pool, similar to add-on costs on standard inventory items associated with vehicles.
• Added: Case 23338: add support for monthly history out to 12 months on part modification
• Added: Case 22695: add 3 and 9 month usage history to the 6 and 12 month options on part modification
• Fixed: an issue where fserialavailable would say that serials were on hold even if the TO hadn't been marked as 'Ordered', which normally controls whether serials are on hold.
• Added: PO dirty core returns to vendor associated with a vehicle now lower the total vehicle cost pool.
• Removed: vehicle break even graph, since it now uses the standard list control graph.
• Fixed: (case 23445) salesorderline and jobpart can no longer have a type of NULL.
• Removed: (case 22171) vendor.category, which is an unused column.
• Changed: (case 23531) made significant adjustments to various tables, functions, procedures, and events to synchronize various databases, which had become somewhat different over time.
• Added: taxitempart, taxitemparttransaction, which is in use at some yards, and standardizes various databases.
• Added (case 23563): New permission for whether a user can make changes to the parts on a job(add/remove).
• Added: (case 9098) shipping tracking # is now a field tracked in the sales order table.
• Changed: all the standard 3rd party shipping methods now have more up to date tracking URLs.
• Fixed: (case 23504) an issue where the inventory transaction list search would throw an error if the user used the Default Vendor filter.
• Added: (case 23570) term.customermemo, which is a customer-visible memo that will be shown on invoice printouts.
• Fixed: an issue where prunforeachtable might not skip all tables we don't care about during an optimize operation.
• Fixed: (case 23738) an issue where historical inventory usage would report based on document store instead of inventory store.
• Fixed: the Inventory Part Type name filter in Transaction List. It was looking up names as inventorytypeids instead of by the actual name
• Removed: (case 23781) references to various views, such as vinvoice, vquote, v_opentransferorder, etc from many enterprise functions. Its been found that views inside functions were causing increased execution times and locks on databases after mysql version 5.6.23. This was causing a lot of slowness on customer balance calculations especially. In most cases, this makes these functions as much as 50% faster even on older versions of MySQL.
• Changed: (case 22989) singlequantity flagged parts now move rather than use variance during counts.
• Fixed: (case 23902) an issue where gl entrys' gl deparment id would sometimes have an invalid value instead of NULL.
• Added: gltransaction.type now supports 'Work Order Reopened'.
• Added: (case 23915) accounting for work order master parts now correctly move both normal cost and core cost from work in progress to inventory instead of just base average cost.
• Added: (case 24118) filters and display fields for inventory.dateentered on the Transaction List screen.
• Fixed: an issue where replicating an inventory record that had quantity on order would carry that over to the new part. We also call finventoryinserted after replicating the part now.
• Added: Transaction List Filters and Display Fields for WO Inventory Category.
• Added: Transaction List Search Filters and Display Fields for Sales Order Inventory Categories.

Data Management

• Added: (case 23792) the backups created as part of imports are now created much faster and take much less space. Mainly, we now use ARCHIVE database engine and don't create indices on backups.

Ebay Extension

• Fixed: (Case 22323) Ebay now displays friendlier shipping names
• Fixed: (Case 24024) The error when refreshing auctions no longer occurs.
• Fixed: (Case 24023) Images from one listing will no longer be applied to later listings when multiple items are listed at once in eBay.

Graphing

• Added: (case 22765) any list with saved graph templates can now be run easily by right-clicking on any list with saved graph templates.
• Added: better support for date/times in right-click graphing for x-axis values.
• Fixed: an issue where sending data with line breaks to right-click graphs could cause errors.

Global Settings

• Changed: saved chart templates are now only loaded once, making graph dialogs and right clicking in list controls faster.
• Fixed: an issue where the Edit->User hotkeys dialog could get stuck off of the screen.
• Fixed: modified column orders and column widths should no longer be lost if the number of columns in the list has changed since the last time the column order was saved.

Image Synchronizer

• Fixed: (Case 23414) The DELETE statement that was used for syncing has been split into multiple components and now it runs faster.

Interchange

• Fixed: (case 22907) an issue where entering a first or last year for an interchange record above 2050 might automatically change the year the user entered to something in the 2000 range.

Login

• Fixed: a minor issue where, if the stores a user had access at was changed, it might not take effect until the next login.

Mas90 Accounting

• Fixed: (case 23902) an issue where gl entrys' gl deparment id would sometimes have an invalid value instead of NULL.

Master

• Changed: (case 7808) the update downloader dialog has been combined with the update log dialog. This prevents the issue where the user's focus was being moved automatically to this popup when downloads finished. This avoids interrupting the user's work.
• Added: the update downloader dialog can now be hidden or closed immediately instead of having to wait for the downloads to complete. If the user wants to reopen the dialog, they can double-click on the update status in the status bar.
• Added: the update progress dialog now has a "Show this dialog in the future" checkbox. If the user unchecks this, they will only see the update progress/change log dialog if they double-click on the update status string on the status bar.
• Fixed: screen list now properly resizes if the user has non-standard windows zoom.

Parts

• Changed: (case 22420) for clarity, the 'print tag' check on a part and its serial #'s have been switched to "Tag Printed", reversing the meaning of the checkbox.
• Fixed: (case 22420) newly created serial numbers now correctly mark themselves as having not printed a tag yet.
• Changed: (case 9153) if the user loads a vehicle whole unit on the parts screen, many fields are now greyed out, to prevent the user from accidentally breaking the vehicle.
• Fixed: (case 10205) an issue where the user could get past the "no manufacturer selected" error when saving an aftermarket part by typing something into the manufacturer code field that was valid but did not match anything in the manufacturer dropdown.
• Fixed: (case 23410) an issue where the show/hide image dialog hotkey was not showing up in the user hotkey dialog. The default hotkey has changed to ctrl+alt+P.
• Fixed: (case 10964) an issue where hitting copy part might cause the new part to not have the correct store, which could cause the location dropdowns to have no options in them.
• Added: (case 23607) the transaction history page now shows 0 in the affected quantity column for all voided document types.
• Added: (case 17753) added support for HTP, auction, and local sales appraisals to assembly collections.
• Added: the collection list now has a totals footer.
• Added: new assembly child parts now get the correct location id. Also, entering an interchange # with a letter at the end now correctly splits the letter into the "Sub-interchange #" field.
• Removed: several redundant queries that were part of loading. Now, manufacturers and part types are loaded only once as part of the auto-completes.
• Changed: (case 23722) in order to decrease the memory footprint of the part history page, many of the text columns are now limited to 100 characters instead of 250.
• Changed: the transaction page should no longer trigger a "Table full" error for parts with a lot of history.

Purchase Orders

• Fixed: an issue where settings were being created under the locations "Purchase Order" and "Transfer Order" instead of "Purchase Orders" and "Transfer Orders".
• Fixed: an issue where the 'On Save' area in the bottom right of POs was partially off the screen.
• Fixed: an issue where, if the user loaded a PO posting using the posting number (such as 1, 2, 3, etc), PO adjustments were not properly loaded.
• Changed: (case 23337) transfer orders now leave serials as status 'Available' until the TO is marked as ordered.
• Added: the transfer order error popups that would occur if the gl category was not configured for transferring are now more useful and clear, and they describe what action the user should take to continue.
• Fixed: an issue where serials added to transfer orders that were not ordered would be shown as In Transit instead of Available, despite the fact that those items are not on hold.
• Fixed: (case 22813) an issue where changing the destination location of a serial on a transfer order might not correctly affect the transferorder locations.
• Changed: (case 23422) the attachment dialog is now editable even if the document that is loaded is void or finalized.
• Fixed: (case 24383) an issue where loading items onto a PO or TO that had messages would cause the user's focus to move away from the list control.

Quickbooks

• Fixed: some memory leaks on the journal push and QB accounts pages.

Report Viewer

• Fixed: a potential issue where advanced print dropdowns might not work.

Reports

Billing

• Changed (case 22934): Optimization pass. Moved the interval balances to a subreport and filtered using a new function.
• Added (case 23382): the ability for the report to be scheduled with Report Commander.

Core Tag

• Removed (case 22969): text below the barcode

Core Tag (Large)

• Removed (case 22969): text below the barcode

Credit Summary

• Fixed (case 23222): current balance and the blue balance line on the graph were not considering unallocated payments.
• Added (case 21080): Weighted Average Days to Pay and other informational fields.
• Added (case 21080): a start date parameter, so range can be selected instead of automatically set to 12 months. If too long of a date range is selected, the report will alert the user and use the longest range it can instead.
• Improved (case 21080): Speed. This is a major performance update.
• Fixed (case 21080): a rounding issue in the formula that determines whether or not a sales order is balanced. 0.00 balance SOs were showing up in the unbalanced SO informational fields.

Customer Address Label 5160

• Added (case 24206): a new report. It prints Avery 5160/8160 labels from the Customer List screen.

GL Activity

• Added (case 22988): GL account number, and a new parameter that allows you to choose whether the date range filters by gl entry date or associated document date

Inventory By Default Vendor

• Added (case 21506): a new report, replacing Inventory By Vendor. This report is similar, but not misleading about what it does. It is an inventory report primarily but also includes purchases and sales related to the inventory line in a date range. It has several different summary modes and also points out vehicles with cost remaining that are not A or H like Inventory Summary and Inventory Detail By Part Type.
• Changed (case 22577): excluded status T vehicles from vehicle inventory that was previously included because it has cost remaining

Inventory By Vendor

• Removed (case 21506): deprecating. Report was misleading. Inventory By Default Vendor will absorb the functionality.

Inventory Count Sheet - LXW

• Added (case 21508): inventory with no location, when the location parameter is '*'
• Changed (case 21508): the true/false parameters to strings. Previously, one was a string and one was a Boolean. With Crystal, either would work; but strings look friendlier if this were ever run from the Report Viewer.

Inventory Detail By Part Type

• Fixed (case 22522): Extended Cost column 0 quantity whole units with cost remaining - because 0 x something = 0. So the average cost sum wasn't matching up with Inventory Summary. Also changed when the query considers quantity > 0, so those 0 quantity with cost remaining items aren't excluded in the query either.
• Changed (case 22577): excluded status T vehicles from vehicle inventory that was previously included because it has cost remaining

Inventory Quantities

• Removed(case 21514): deprecating Inventory Quantities report.

Inventory Summary

• Fixed (case 21506): quantity multiplier in the vehicle section of the query, which throws off cost when you have vehicles with multiple quantity. That is not something that is supposed to happen, but…
• Changed (case 22577): excluded status T vehicles from vehicle inventory that was previously included because it has cost remaining

Label

• Removed (case 22969): text below the barcode

Label By Location

• Removed (case 22969): text below the barcode

Labor Summary By Employee

• Fixed (case 23261): high labor hours when incomplete/unbilled jobs used the ratio and job.billinghours to calculate billing hours. Billed hours are no longer included until they are actually billed on an invoice. The report will indicate what is outstanding, if anything.

Picking Tag

• Removed (case 22969): text above the barcode (j)

Receiving Label

• Removed (case 22969): text below the barcode

Receiving Tag

• Removed (case 22969): text below the barcode

Sales By Invoice

• Fixed (case 23930): a query issue that could leave out some data that was too similar to other data.

Sales Order 11in

• Fixed (case 23559): a issue with the job and labor subreport leaving out labor rows when they were the same as other rows.
• Added (case 23570): term memo, a message specific to the payment terms, if present.
• Fixed (case 22154): extra space in footers on pages that are not the last page
• Added (case 22154): conditional suppression to the line item header - it will no longer print at the top of the page/section if there are no line items to print on that page
• Fixed (case 21892): optimization pass.

Serialized Tag

• Removed (case 22969): text below the barcode

Tag

• Removed (case 22969): the text below the barcode
• Added (case 21021): QR codes, this time disabled by default. A reliable internet connection is required to use them.

Tag By Location

• Removed (case 22969): text below the barcode

Tag Landscape

• Removed (case 22969): text below the barcode

Vehicle Value Analysis

• Changed (case 22577): excluded status T vehicles from vehicle inventory that was previously included because it has cost remaining

Sales Orders

• Fixed: an issue where a setting was being created under the location "Sales Order" instead of "Sales Orders"
• Fixed: (case 23028) an issue where menus in ITrack would not work while the SalesOrder screen was open and active.
• Fixed: (case 22912) an issue where removing the hold checkbox on items on an invoice still left those items on hold.
• Fixed: (Case 23102) an issue where the user could delete a new payment that had a valid credit terminal transaction associated.
• Changed: (case 23102) the user can no longer close a SO without saving it if there are any payments that have valid credit terminal transactions associated.
• Fixed: an issue where the 'cost' of inherent core lines could be incorrect on the first load, though they would be corrected on save.
• Added: (case 22341) the user is now prevented from deleting inherent core charges from an invoice if there is cost on the core charge. This is to prevent issues where that cost wasn't hitting accounting properly.
• Changed: (case 23314) now, items with average core cost (core inventory value) will automatically add inherent core charges to the document.
• Fixed: (case 23419) an issue where the "Can change lineitem taxable" permission was not affecting newly added lineitems.
• Added: (case 9098) support for shipping tracking #'s on each invoice.
• Added: a button to view the tracking information for the current SO based on the tracking URL, if its filled out. If it is not filled out, the user is notified that it will need to be entered first.
• Added: (case 15871) if the user enters a lineitem quantity before performing a part lookup, that quantity will no longer be lost. Also, price is now preserved if the user loads misc item info.
• Changed: the user can now use the stock # and vendor columns to perform full 'non-stocked vehicle' or 'non-stocked vendor' lookups on items that just have a description/item/price (pure-misc items) in addition to empty rows.
• Added: (case 23570) support for a 'customer memo' field for terms in the configuration dialog.
• Fixed: (case 23735) an issue where returned items would get an invalid SKU, causing them to not properly increase inventory QoH.
• Fixed: (case 23662) an issue where adding new payments to a SO would no longer correctly automatically select the customer's default payment method.
• Added: voiding and reopening SOs now happens within a single transaction, so that if there is any error, the entire operation is reversed.
• Fixed: (case 23764) an issue where the default payment amount was no longer defaulting to the remaining invoice balance.
• Fixed: an issue where changing the document number or amount of a previously saved payment was not being saved.
• Fixed: (case 23919) an issue where payments that had an impact on more than one invoice could have their amount changed each time the user opened and resaved an associated invoice.
• Fixed: an issue where saved payments on SOs could not have their amount set to $0 by users with the ability to edit payments. The user would see a popup with an option to "Remove $0 payments" but instead, their changes would not be saved. Now, newly created $0 payments are removed in this case, but existing payments save.
• Added: in order to avoid issues where SOs are finalized with open or void WO jobs on them, closing SOs is now impossible if any lineitems are from jobs that are in an invalid state.
• Added: the user can now delete job lineitems that point to invalid work orders now. This is because they cannot close a SO with documents in an invalid state.
• Added: job lineitem prices and costs are now correctly updated on load and on refresh so that reopened WOs don't get invoiced for the incorrect amount.
• Fixed: (case 24002) crediting inherent core charges back to the customer (forgiving core charge) now uses the GL Context of "Core Sale" instead of Return. This is to make sure that core credits don't hit inventory sales accounts. This does not affect dirty core exchanges.
• Changed: (case 24059) the warning that the user received when returning an item on another open return SO is now an error to help avoid users returning items more than once.
• Changed: (case 23422) the attachment dialog is now editable even if the document that is loaded is void or finalized.
• Fixed: (case 24383) an issue where loading items onto a SO that had messages would cause the user's focus to move away from the list control.

Search

• Fixed: an issue where the inventory type dropdown wasn't getting set right when the user typed a type # in the edit next to it.
• Added: support for exporting results in all result lists to graphs like other lists in the software. This may not be very useful in the part search.
• Fixed: (case 22011) vehicles can now be exported to berryhill auctions using the auction export feature, same as inventory.
• Added: (case 20428) auction exports now include the store id the inventory is currently at.
• Changed: (case 22420) to match the changes to the part screen, all Print Tag check boxes have been renamed to "Tag Printed", reversing the meaning of the checkbox.
• Fixed: (case 23108) an issue where image data from previous searches were not cleared when the user performed a new search.
• Fixed: (case 23136) an issue where the model lists were based on the id of the currently selected part type instead of the type set id of the currently selected part type.
• Changed: (case 23722) in order to avoid an issue where exporting search results to CSV might overflow the maximum temporary table size, we now use the default engine type.

Vehicles

• Added: (case 23034) misc parts on a vehicle teardown will no longer copy the year/make/model/VIN/body style from the vehicle when it is changed. Only Standard parts will automatically copy that information to all associated parts.
• Changed: the bid page now has more and clearer tooltips for the suggested bid fields on the bid tab.
• Added: the vehicle 'costs' tab now includes inherent core charges from the vendor as well as dirty core returns to the vendor, as both of these now affect a vehicle's total cost pool.
• Fixed: (case 23306) the costs and performance tabs now more correctly match the current cost system.
• Changed: vehicle costs are now sorted by date and colored based on whether the costs are received or on a finalized WO.
• Changed: the performance tab of vehicles now takes various global settings into account as to whether inventory records average cost and/or override cost allocate vehicle costs on inventory.
• Changed: (case 23306) core costs are now properly taken into account as vehicle cost allocations.
• Added: on the performance tab, if the costs allocated on documents and inventory is greater than the total vehicle costs, the cost field will show in red text.
• Changed: the break even graph is no longer written out to a file in the operating system. This should make rendering graphs faster.
• Changed: clearing the vehicle screen now clears the break even graph.
• Added: the break even graph now shows a 'no vehicle loaded' message if no vehicle is loaded.
• Fixed: An issue where the vehicle costs line on the break even graph did not include costs where the posting was missing.
• Fixed: (case 23410) an issue where the show/hide image dialog hotkey was not showing up in the user hotkey dialog. The default hotkey has changed to ctrl+alt+P.
• Fixed: an issue where the show/hide image dialog hotkey was not working.
• Added: a new global hotkey to perform a vehicle search, similar to the part lookup hotkey. The default keystroke is shift + F4.
• Fixed: the vehicle costs tab no longer shows master parts from work orders if those work orders have been turned into external work orders.

Vendors

• Fixed: an issue where the terms and payment method dropdowns on the advanced information page were very short, making it tough for the user to use.

Vendor List

• Changed: (case 23171) vendor smart searches with multiple words will now automatically require all words to be present in the results.
• Performance: removed some unnecessary searching that happened as part of a vendor smart search that may have added slowness to these searches, especially when no results were found.
• Fixed: (case 23407) an issue where the application could crash if the use uses the next/previous arrows when no search had been done.

Warehouse Management

• Fixed: (case 23835) it was possible that approving jobs could partially perform the approval process and hit an error, causing the parts in the count to be partially moved. Now, if there is an error, all activity is rolled back.

Work Orders

• Added: (case 22341) the user is now prevented from deleting inherent core charges from a job if there is cost on the core charge. This is to prevent issues where that cost wasn't hitting accounting properly.
• Changed: (case 23314) now, items with average core cost (core inventory value) will automatically add inherent core charges to the document.
• Added: (case 15871) if the user enters a quantity before performing a part lookup, that quantity will no longer be lost. Also, price is now preserved if the user loads misc item info.
• Added: an "Advanced…" button to the bottom of the screen, similar to the one on the Sales Order screen for performing advanced operations, such as reopening the document.
• Added: voiding WOs now happens within a single transaction, so that if there is any error, the entire operation is reversed.
• Added: voiding a WO should now properly reverse changes made to the locations of any master parts.
• Fixed: work orders can no longer be voided/reopened if it has been sent to a finalized SO. That SO must be reopened or voided first.
• Added: when work orders are reopened/voided, their 'last changed' fields are set correctly, to avoid another user performing the same operation from another machine.
• Fixed: reopening a WO now marks produced serials as Work In Progress instead of deleting them entirely.
• Fixed: closed WOs no longer show an uneditable 'new' line in the master parts list.
• Added: adding a new master part that creates serial numbers now allows the user to pick a location for the new serial #.
• Added: new setting ("Work Orders"->"Master part costing: put core inventory items' cost into average core cost") that controls whether inventory core bank items (inventory marked with "Is A Core" checked) have their cost put into the core cost of master parts. This was existing functionality that was always on before. This setting defaults to True.
• Added: new setting ("Work Orders"->"Master part costing: put inherent/dirty core line items' cost into average core cost") that controls whether inherent core charges have their cost put into the core cost of the master parts. This is new functionality. This setting defaults to True.
• Fixed: new serials created on a WO now correctly inherit the default new inventory location for WOs (specified by the setting "Work Orders"->"Location for new master parts (special value $PRIMARY allowed)").
• Added: the new serial # dialog now has a full location dropdown so that the user can properly add the new serial # to any location.
• Fixed: (case 10837) an issue where voided or open documents would throw an error if they were reopened or voided.
• Changed: only closed or voided WOs can be reopened, and only if the user has permission.
• Fixed: an issue where deleted jobs or line items with bad data were keeping the user from saving.
• Fixed: if the user reopens a WO and refinalizes it, the "choose SO to send to" dialog won't pop up if the jobs are already on another open SO.
• Changed: (case 23422) the attachment dialog is now editable even if the document that is loaded is void or finalized.

Release 14.7

EBay Extension

• eBay dropdown behavior is now more reasonable.
• Images on eBay listings now attach correctly when listing multiple items.
• Several eBay errors when updating eBay records no longer occur.

Release 14.6

Database

• Removed: (case 23781) references to various views, such as vinvoice, vquote, v_opentransferorder, etc from many enterprise functions. Its been found that views inside functions were causing increased execution times and locks on databases after mysql version 5.6.23. This was causing a lot of slowness on customer balance calculations especially. In most cases, this makes these functions as much as 50% faster even on older versions of MySQL.
• Case 22989: Make singlequantity flagged parts move rather than use variance during counts.
• Releasing some reworked queries to not use views

Sales Orders

• Fixed: (case 24002) crediting inherent core charges back to the customer (forgiving core charge) now uses the GL Context of "Core Sale" instead of Return. This is to make sure that core credits don't hit inventory sales accounts. This does not affect dirty core exchanges.

Release 14.5

Manage Warehouse

• Fixed: (case 23835) it was possible that approving jobs could partially perform the approval process and hit an error, causing the parts in the count to be partially moved. Now, if there is an error, all activity is rolled back.

Sales Orders

• Fixed: (case 23919) an issue where payments that had an impact on more than one invoice could have their amount changed each time the user opened and resaved an associated invoice.
• Fixed: an issue where saved payments on SOs could not have their amount set to $0 by users with the ability to edit payments. The user would see a popup with an option to "Remove $0 payments" but instead, their changes would not be saved. Now, newly created $0 payments are removed in this case, but existing payments save.

Work Orders

• Added: new setting ("Work Orders"->"Master part costing: put core inventory items' cost into average core cost") that controls whether inventory core bank items (inventory marked with "Is A Core" checked) have their cost put into the core cost of master parts. This was existing functionality that was always on before. This setting defaults to True.
• Added: new setting ("Work Orders"->"Master part costing: put inherent/dirty core line items' cost into average core cost") that controls whether inherent core charges have their cost put into the core cost of the master parts. This is new functionality. This setting defaults to True.

Release 14.4

Sales Orders

• Fixed: (case 23764) an issue where the default payment amount was no longer defaulting to the remaining invoice balance.
• Fixed: an issue where changing the document number or amount of a previously saved payment was not being saved.

Release 14.3

Customer List

• Added: support for single-letter words in customer list search. This feature requires a change to the server as well.

Sales Orders

• Fixed: (case 23735) an issue where returned items would get an invalid SKU, causing them to not properly increase inventory QoH.
• Fixed: (case 23662) an issue where adding new payments to a SO would no longer correctly automatically select the customer's default payment method.

Vendor List

• Added: support for single-letter words in vendor list search. This feature requires a change to the server as well.

Release 14.2

Vehicles (18352)

• Fixed: (case 23306) the costs and performance tabs now more correctly match the current cost system.
• Changed: vehicle costs are now sorted by date and colored based on whether the costs are received or on a finalized WO.
• Changed: the performance tab of vehicles now takes various global settings into account as to whether inventory records average cost and/or override cost allocate vehicle costs on inventory.
• Changed: (case 23306) core costs are now properly taken into account as vehicle cost allocations.
• Added: on the performance tab, if the costs allocated on documents and inventory is greater than the total vehicle costs, the cost field will show in red text.
• Changed: the break even graph is no longer written out to a file in the operating system. This should make rendering graphs faster.
• Changed: clearing the vehicle screen now clears the break even graph.
• Added: the break even graph now shows a 'no vehicle loaded' message if no vehicle is loaded.

Work Orders (18363)

• Fixed: (case 23579) an issue where the cost field on the edit item dialog would keep the user from typing anything into it.

Release 14.1

Core Management (17564)

• Fixed: (case 23406) the part type dropdown was not usable.

Customer (17572)

• Added: if the user uses the next/prev arrows when no search had been done, a message is displayed, like on the vendor screen.

Customer List (18279)

• Fixed: (case 23407) an issue where the application could crash if the user uses the next/previous arrows when no search had been done.
• Fixed: (case 23429) an issue where customer smart searches with short words (less than 3 letters) or certain ignored words (like WAS or THE or ABOUT) would cause a search to return no results. This is due to a MySQL bug and although these words are still not considered as part of the search, at least the search is performed using all OTHER words.

Sales Orders (17685)

• Fixed: (case 23419) an issue where the "Can change lineitem taxable" permission was not affecting newly added lineitems.

Vendor List (18278)

• Fixed: (case 23407) an issue where the application could crash if the user uses the next/previous arrows when no search had been done.
• Fixed: (case 23429) an issue where vendor smart searches with short words (less than 3 letters) or certain ignored words (like WAS or THE or ABOUT) would cause a search to return no results. This is due to a MySQL bug and although these words are still not considered as part of the search, at least the search is performed using all OTHER words.

Release 14.0

Highlights

• Brand new ability to accept payments through external credit card swipe terminals. Talk to ISoft for more information about compatible swipe terminals. Integrates with the sales order and customer screens.
• Better support for duplicate attachments on all attachment interfaces.
• Customer and vendor searches are faster and date based searches are much easier.
• Tooltips and easier flow on the interchange interface
• Ability to quickly update inventory to the last price it was purchased for on POs
• Some speed improvements to part smart searches
• Transaction list date filters can now move forward when they are run later, as well as support for date ranges like 'This month', 'Last Year', etc.
• Attachments can now be added to documents

Accounting

• Changed: removed the code that disabled the ability to set recreated gl entries to a previous date. This was disabled due to complexities between SOs and WOs.

Common Resources

• Fixed: (case 22440) an issue where the popup attachment dialogs might not correctly add new attachment files to unsaved items.

Credit Card Processing

• Added: a new interface for integrating with a some new Heartland credit card hardware.
• Added: a new 'configure terminal settings' options page.
• Added: if the user attempts to process a credit card and no terminal is configured, the user is prompted to configure these settings.
• Added: if the user fails to process a credit card because there was a problem connecting to the terminal, they are prompted to retry or configure terminal settings.
• Added: the response from a successful credit sale now returns the approved amount.
• Changed: the default timeout in the credit card options dialog is now 0 (unlimited) since it seems like the best bet.
• Added: a new page to edit->options that allows the user to configure credit card terminals.
• Added: an 'edit payment from terminal' dialog which is a staging area the user will see that will provide information about the current status of accepting payment from the customer through a credit card terminal.
• Added: "Test connection settings" button to the configure credit terminal page. When the user clicks it, it saves the current settings and attempts to connect to the terminal with the current settings. The user is told whether this succeeded.
• Added: the user can now cancel an in-progress connection to the credit terminal.
• Added: better error reporting to the user for failed payment connections.
• Added: configure credit terminal button to the 'accept credit payment' dialog, this allows a user to easily fix any configuration issues while accepting payment.
• Added: if the customer chooses a tender type, the user interface will be changed to reflect this choice.
• Changed: standardized the error messages shown to the user.
• Fixed: an issue where sometimes no status message would be shown if the user cancelled between requests to the terminal.
• Added: many read-only fields returned by the credit card interface are now shown to the user for debugging purposes.
• Added: there is now a 'automatically close dialog on successful payment'. This is a user setting. When checked, it saves the user a click for confirming payment addition after the swipe completes.
• Added: authorization # to the credit card dialog, as that is a useful piece of information during debugging.
• Changed: if a payment finished successfully, the user can no longer edit amount or charge type.
• Added: the user can void a successful payment now. This will only work on payments that have not yet been posted.
• Added: the UI is updated in realtime as the customer chooses options on the swipe terminal.
• Added: when a payment is processed successfully, host code, transaction id, authorization #, name on card, and host trace number are all properly saved to the database.
• Added: 'cash back amount' is now returned by a successful payment transaction.
• Added: support for payment method selection. Also, the payment method of 'auto select' is the default, and an appropriate payment method will be selected based on the card type and tender type.
• Added: store level default payment method for card payments that will be selected if no valid payment methods are found by name.
• Added: payments now save what transaction they were created by, if any.
• Added: payments now save a successful transaction's authorization number into the document/check# field.
• Added: support for SSL for communication over the Ethernet to the terminal.
• Added: support for viewing payments that are not editable.
• Added: short acct number is now always padded out to 4 digits.
• Added: support for negative credit payments (returns).
• Added: voiding a credit transaction now sets the document # field to empty so that it can be populated by a subsequent transaction.
• Added: since returns do not get authorization #'s, we now put host number into the document # field for returns.
• Fixed: an issue where cancelling while the user is being prompted for tender type could result in payments that stayed in an intermediate state.
• Changed: some error messages to be clearer.
• Added: since voiding payments is done by heartland reference #, and that is not as unique as an authorization number, there is now a step where we ask the terminal if the specified payment is still 'open' or not. If it is not, the void operation is not attempted.
• Added: support for launching the CC payment dialog with the amount locked, which is useful in some cases.
• Added: support for tracking/remembering what type of entry mode was used, as well as whether a signature is required.
• Added: we now retrieve and store several fields required to be printed on receipts when chip and pin (EMV) transactions are made.
• Fixed: a bug where some chip and PIN features were not being correctly read from the terminal response.
• Added: if the customer uses a credit card to pay, they are now prompted to sign digitally. If this operation fails or is cancelled, the receipt printout will have a signature line.
• Added: support for retrieving HREF (host reference number) from the payment information.
• Fixed: an issue where, when the user was prompted to choose between credit and debit, the prompt was being cut off.
• Added: support for 'PIN Verified' status for debit card transactions.
• Added: support for automated signature collection through the S300 hardware, removed custom signature collection.
• Added: support for automated prompting the customer between credit/debit, removed custom choice.
• Added: we now support the CVM return from the S300 hardware which is the way the customer verified the payment (EMV only).
• Fixed: an issue where 'user choice' tender type wouldn't automatically select Credit if the user chose credit.
• Added: a voided transaction now overwrites the host reference number of the void operation.
• Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds.

Crystal Reports

• Added: (case 20389) the report adder script export now correctly includes the fileid and category in the ON DUPLICATE KEY SET section.
• Fixed: (case 20389) an issue where clicking "Replace" when adding a new report file in it would instead leave the previous report file in the system.
• Fixed: (case 20389) the report adder script export now has a query that attempts to find 'empty' AU reports and replace them instead of inserting a duplicate. This will no longer be necessary once report.filename becomes unique.
• Fixed: an issue where, if the user showed the advanced print dialog, previewing the report would not work.
• Changed: new reports created from the auto-updater are now created as not user visible so that they wont' show in the report viewer until the database update is run.

Customer

• Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
• Fixed: (case 20872) an issue where the customer option list wasn't displaying the options it should show.
• Added: the payment dialog now shows the external payment transaction's reference number if the payment was entered through a payment terminal.
• Added: a 'card' button that launches a payment terminal interface dialog for accepting credit and debit payments on account.
• Added: if the user changes the amount of a payment such that it no longer matches the amount of the external transaction, they are presented with a warning popup that they are causing the values to mismatch between original transaction and customer credit/accounting.
• Fixed: (case 21196) an issue where customer default invoice terms were not being selected correctly when a customer was loaded.
• Added: the credit card payment button is hidden if the credit card module is not loaded.
• Fixed: (case 22484) an issue where a user without permission to edit customers might get an erroneous change detected message when they open the customer screen.
• Added: (case 20883) the print statement dialog now has an advanced print option for specifying print options.
• Added: (case 20883) the print statement dialog now has an email button. Hitting that button automatically fills out the print dialog with the customer's email address.
• Added: (case 21378) there is now a permission that controls whether the user can change the total of an existing payment. This is to restrict situations in which the user can accidentally do something to a saved payment that changes the accounting impact after the fact.
• Fixed: (case 23012) an issue where the user could possibly cancel a payment after accepting payment from the credit card terminal.

Customer List

• Changed: position of controls on the screen has been standardized with other screens.
• Added: date based searches now use a date-time picker to avoid ambiguity of date formatting.
• Performance: date based searches should now be slightly faster.
• Fixed: an issue where printing the customer list wouldn't work if the user chose to preview the report.
• Changed: (case 21158) some recent changes added searching alternate addresses and significantly slowed down customer smart searches. The customer smart search has been rewritten to be much faster. Also, if the user performs a smart search, the results are ordered by how well they match the user's input. Smart searches are now 'full text' searches meaning words can appear in any order. However, this has the downside that searching for words that start with wildcards will not work ("*obert" will not match "Robert"). Also, the order of the results of a smart search will not carry over to printing the customer list.
• Fixed: some issues where hitting "Show All" would not work correctly.
• Fixed: (case 15426) an issue where the user's column order and widths were not saved when the user closed the screen.
• Added: (case 12093) there is now a permission that controls whether the user can merge customer accounts. It defaults to off for all users.
• Changed: (case 23171) customer smart searches with multiple words will now automatically require all words to be present in the results.
• Fixed: customer smart searches now correctly order results with the 'best' matches at the top.

Database

• Added: (case 19307) a new table for tracking what default printers should be used for various report type categories. These entries can be per-user, per-plant, or per-productcode (or any mix of those 3).
• Added: fgetreport_printer returns the printer to be printed to for a specific report type based on input criterion.
• Removed: a couple indices on the salesorderdocument table. They are not very selective and were preventing more useful indices from being used in some scenarios, such as core management loading. This table is so small, indices will probably not improve load speed any anyways.
• Fixed: (case 20389) report.filename is now unique. This resolves issues where duplicate reports could could exist on the system due to the auto-updater. In order to do this, duplicate reports got their filename modified to have a "DUP" added to the end. These duplicates should get cleaned up at some point, as the auto-updater won't maintain them.
• Changed: renamed interchangepricing to DEPRECATED_interchangepricing, as this table is not referenced by the application.
• Fixed: an issue where an inventorysetting record that could cause an error on part modification (part of the version 12 update).
• Fixed: an issue where the popularity code was not editable on the part modification screen.
• Added: a new table: paymentterminaltransaction which will contain information about all credit card transactions handled by the system, including all fields that must be printed on the receipts.
• Added: Voided status for payment terminal transactions.
• Added: payment terminal transactions now save host code, which is apparently required to be on the receipt, where appropriate.
• Added: payments now remember the terminal transaction that spawned them, when appropriate.
• Added: an index to inventoryserial for looking rows up by status.
• Added: (case 21158) a full text index to customerlist, which allows us to speed up customer smart searches significantly.
• Added: (case 7280) a new table for associating attachments to sales orders.
• Added: support for attachments on POs, TOs, and WOs.
• Added: support for a verification status of PIN Verified for debit card transactions.
• Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds. Both default to on for any user who could previously void payments in the system.
• Changed: the right click list graph template to no longer show scrollbars when rendered inside an embedded IE window.
• Fixed: (case 22371) an issue where clicking to show/hide series on a stacked column graph without trendlines would not work correctly.
• Fixed: an issue where showing an hiding a series with a point type other than Circle would cause the newly unhidden points to be circular.
• removed: an unused setting.
• Added: (case 22332) Sales Order transaction list search now has a "Condition" option for both search filter and results.
• Fixed: an issue where the parts screen might continuously say that the location id was being changed and the user had to log a reason why even though it was not changing anymore.
• Fixed: the chart template now supports aggregate column charts.
• Fixed: chart data with invalid X axis values is now ignored.
• Added: (case 20434) support for a new table (charttemplate) that stores shared chart templates.
• Added: a new permission controlling whether a user can manage saved chart templates.
• Added: (case 22811) a new status to inventoryserial called 'On Order', for unreceived PO serials.
• Changed: all unreceived serials on open purchase orders have had their status moved from In Transit to On Order.
• Fixed: (case 22824) an issue where the model lookup on the inbounding import might throw a database error.
• Added: (case 12093) a new permission for merging customers.
• Fixed: (Case 21613) Added support for auction cancellations.
• Added: support for a verification status of PIN Verified for debit card transactions.
• Added: 2 new permissions, controlling whether the user can void transactions and whether the user can perform refunds. Both default to on for any user who could previously void payments in the system.
• Added: (case 22915) if a 'singlequantity' item is transferred between stores, change the inventorystoreid of any salesorderline/jobpart rows that used to reference the old store. Also, update any documentlinelocations, do pick + move at the destination store and update all hold quantities.
• Fixed: (case 22912) an issue where invoices with lineitems not on hold would still hold quantity

Deliveries:

• Fixed: (case 4926) a crash that would happen if the user removed the last item from a run sheet.
• Fixed: an issue where the first time the user clicked on the document list would be ignored.
• Fixed: the document list would load more times than necessary, slowing things down.
• Fixed: a crash that could be caused if the user clicked the checkboxes in the document list too fast.
• Added: (case 14353) the picking page now has a shipping method filter. Choosing something in this dropdown will filter to match just SOs, POs, and TOs with that shipping method. Only the shipping methods the user has set up on the configuration tab will be shown here.
• Added: (case 14353) the shipping method column in the list can now be used to quickly change the shipping method of the selected document without opening that document on the document screen. If the user switches to a shipping method that is auto-picked, they will be alerted that this will cause the items to be picked automatically and that the list should be refreshed.
• Changed: all the dropdowns on the picking tab now allow auto-complete as the user types.
• Added: 3 new permissions that control whether the user can edit the shipping method on TOs/POs/SOs that the user loads onto the screen.

EBay Extension

• Fixed: (Case 21050) ebay image uploads option hidden.
• Fixed: (Case 21047) Listing durations now save correctly and show correctly.
• Fixed: (Case 21245) The auction and transaction tab now both load auctions based on auction start time.
• Fixed: (Case 21246) Freight shipping cost is no longer 8,000,000,000, but is 0.00 as intended.
• Fixed: (Case 17479) Image counts on the listing screen of eBay should now be accurate regardless of whether the image is a url or a file.
• Fixed: (Case 21212) Global Shipping now has a global default. a checkbox is added to the global config screen, as well as to the edit dialog for a specific listing.
• Fixed: (Case 21210) We can now add up to 12 images to an ebay listing, not just in the description anymore!
• Fixed: (Case 21036) Empty dropdowns in the edit dialog no longer cause crashes on ok. Missing items are bolded, but are obviously still not being noticed. If the user tries to list an item with empty dropdowns, it will throw up an ebay error dialog like it does for other things (like a missing description) instead of crashing.
• Fixed: (Case 21210) Fixed a bug where listings with more than twelve images would upload no images instead of just being limited to the first twelve.
• Fixed: (Case 21475) Now with support for auctions in addition to the already supported fixedpriceitem listings.
• Fixed: (Case 21613) Added support for auction cancellations as well as the necessary database column for this feature.
• Fixed: (Case 21613) Error handling added for auction listings.
• Fixed: (Case 21611) Implemented error handling from sales and quotes screen.
• Fixed: (Case 18603) eBay can now create new customers with the standard defaults.
• Fixed: (Case 18035) Added a setting, configurable from the config screen, for whether the BuyItNow price is retail + core or just retail.
• Fixed: (Case 22231) Global Shipping setting now pulls into the edit details screen and the listing.
• Fixed: (Case 21971) Free shipping now correctly disables cost and sets it to 0 in the edit dialog. Unchecking re-enables the cost column for modification, but does not revert the cost change.

General

• Added: the user can now drag items to the edge of all list controls that support drag and drop to scroll the list.
• Fixed: if the user drags anything other than files into an attachment area, the 'no drop' icon is shown.
• Added: if the user drags a file over an attachment area, the list's attachment system is disabled so that the user can drop files into the list as well.
• Changed: when the user drags items within a list control, they are stored in a special clipboard format so that other applications don't think they can get them.

Global Settings

• Added: (case 20434) support for saved chart templates in right-click graphs.

Graphing

• Changed: (case 21229) to make the graph options dialog easier to use, the chart type dropdown is now a list with graph icons. Also, many of the controls in the dialog now have tooltips and clearer names.
• Added: (case 14508) the graph options dialog now has a preview chart pane next to the chart options. This allows the user to see what the graph will look like without having to generate the final graph. The chart automatically refreshes whenever anything changes that affects it.
• Added: a 'preview in external browser' button that shows the chart in an external browser window without having to close the dialog.
• Added: an instructions field that tells the user what they still need to do before the current options can generate a chart.
• Added: a series point shape column so that the user could choose what shape the points will be.
• Added: trendline dropdown where the user can choose what degree of trendline they'd like to add to the graph for each series.
• Added: the right click graphing dialog now has the following new features:
• Advanced mode: the user can go into 'advanced mode' when building a chart. This shows various extra options that may not always be required when generating a basic graph. The user's selected mode will be remembered.
• Trendlines: the user can choose to display trendlines for each data series on the graph. If the user is in advanced mode, they can choose the type of trendline as well as whether the trendline's formula and fitness should be displayed in the legend.
• Point shape: (Advanced mode only) the user can choose the shape of the points in a line/scatter chart for better black&white printout or colorblind accessibility.
• Cumulative series: (Advanced mode only) the user can choose to make a data series cumulative, making it so that all values will include all previous values in the same series.
• Changed: current graph template has been modified to no longer show scrollbars in embedded IE windows (required a slightly bigger buffer around all sides). The way the graph resizes has been optimized slightly to better use available screenspace.
• Changed: current graph template has been modified to properly handle cumulative data series, trendlines, point shape selections, etc.
• Added: an error message to chart generation that will stop the user if they choose a discrete (non-numeric, non-date) x axis for a line or scatter graph. While these graphs technically work, they are not very useful.
• Added: (case 20434) support for saving chart templates as well as using saved chart templates.
• Fixed: an issue where the right click graph template would show unnecessary 0.00 points in line charts if the series was cumulative.
• Fixed: line charts with missing points are now smoother and interpolate between those points.
• Fixed: a crash when adding new saved chart templates.

Interchange

• Fixed: if the user hits enter when they're in the 'search area' of the interchange screen, a search will be performed, but hitting enter when entering interchange records down below will treat the 'enter' as a spreadsheet enter.
• Fixed: a crash that could occur if someone doubleclicked an item with a dropdown where an invalid model was in a dropdown.
• Removed: the sales meta-data no longer looks at non-stocked item sales.
• Added: the sales meta-data now also looks at work order usage history.
• Fixed: (case 21159) an issue where changing the sub-interchange # of an application might not correctly change all other applications in the group if the rows were new.
• Added: tooltips to various controls on the screen to make it easier to use.
• Changed: the minimum size of the choose interchange # popup has been increased to attempt to solve issues where some of hte information was not visible initially.

Login:

• Added: support for a new permission for managing chart templates in right-click graphing.

Master

• Fixed: an issue where the thread progress dialog that showed "X/Y processes still running" would sometimes show an incorrect # of elapsed seconds if some of the tasks took a long time.

Parts

• Fixed: (case 20163) clearing the parts screen now correctly sets the available and hold quantity.
• Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
• Fixed: (case 20860) several issues related to tab order on various tabs.
• Performance: saving large collections/breakdowns can now be as much as 3 times faster, especially on slow connections. Many queries that were being run to see if inventory on the collection had been modified since it had been loaded has been combined or eliminated.
• Fixed: (case 20728) an issue where sending parts from the parts screen to the part modification screen wouldn't load anything up.
• Changed: the save confirmation dialogs that are launched from many of the buttons and functions on the parts screen now look like the ones in use on the vehicle screen and some others (where the pages that changed are displayed). Also, the buttons have more specific verbs.
• Changed: the save confirmation dialogs have had their phrasing adjusted to be more concise.
• Fixed: (case 20896) an issue where parts wouldn't save reordered attachment ranks if they hit the save button instead of the close button.
• Fixed: (case 21206) an issue where the location dropdown was not wide enough.
• Changed: the change log dialog now puts newer entries at the top, like all historical logs in ITrack.
• Added: the change log dialog now puts the user's focus into the first new item, and uneditable items show their comment in a multi-line readonly edit.
• Fixed: an issue causing variance locations to be created when the user opened a part that had unreceived serials 'In Transit' on a PO.
• Added: (case 11280) the store dropdown at the top is no longer read-only. This dropdown has 2 functions:
• 1. on new (unsaved) parts, this allows the user to choose what store to create the part at.
• 2. on existing parts, this loads the part at the other store. This makes it so that the user doesn't need to use the search screen to look at a part record at other stores.
• Changed: (case 11280) the parts screen now only puts the user onto the aftermarket page when the user clicks the Replenishable stock type radio, and not when they load a part or switch plants on a part.

Part Configuration

• Fixed: (case 16267) an issue where the user could see a database error if a part type had a category that didn't match the displayed category name by case only. Now the interface shows which categories are in use, ignoring case.

Purchase Orders

• Added: (case 20388) if a purchased item has a price different than the replenishment cost on inventory, an attention icon is shown. If the user double-clicks this icon, the inventory record will be updated.
• Fixed: (case 20857) an issue where the 'core exchange' column in the POs return dialog was hidden, making it impossible for the user to specify that a return associated with an inherent core charge was an exchange instead of just a credit. This issue was introduced in version 12.
• Fixed: an issue where the return dialog defaulted to just showing purchases from today instead of the last 90 days, as intended.
• Fixed: (case 20893) an issue where some of the right click options in the return dialog were not working.
• Fixed: (case 21052) a crash that could be caused by returning an item to a vendor.
• Added: (case 7280) support for attachments on purchase orders. The attachments dialog is automatically shown to the user if the document has any attachments. Whether the user wants to view this dialog can be toggled with the attachment button, this preference is remembered.
• Added: attachment support to transfer orders.
• Fixed: attachment dialogs now correctly close on POs/TOs if the user switches screens.
• Added: the PO and TO attachment dialogs now properly hide themselves when the user switches document pages.
• Added: (case 21768) if the user added an inherent core line to a non-stocked purchase line that had an order fulfillment on it no longer copies that order fulfillment to the inherent core line.
• Fixed: (case 21865) an issue where POs would automatically be marked as done receiving when a user without permission to receive inventory would save them after all quantity was received.
• Fixed: (case 22419) an issue where transfer orders that were created due to a multi-store purchase from inventory overview would not properly update the 'on order' and 'on hold' quantities.
• Fixed: an issue where, if the user's current store doesn't match the store inventory is being received into (POs and TOs both), the wrong store's settings might be used for the default inventory location and the receiving location.
• Changed: the location column in the choose serial popup is now labeled Dest. Location to make its purpose clearer.
• Added: (case 11065) the user can now set a 'Receiving location' for the entire PO posting. This sets all quantity/serials being received on a posting to got to the specified location. This can be accessed through the advanced operations button or the right click menu.
• Fixed: (case 22811) an issue where unreceived purchase order serials were causing the parts screen to creating variance locations. Now, those serials are marked as On Order instead of In Transit, and On Order serials are not considered as part of the on hand quantity.

Reports

Billing

• Added: (case 20164) settings for displaying "CONTINUED ON NEXT PAGE….." at the bottom of multiple-paged documents, except on the last page and displaying balance at the top of the document (per customer).
• Fixed: (case 21515) updated period applied payment logic to include invoices with date = End Date. It was a < previously, not a <=, so it was possible for some payments to show incorrectly as unallocated.

Billing OIA

Removed: (case 20888) deprecating the report. Functionality is now covered by the OIA setting on standard Billing report.

Credit Summary

• Fixed: (case 20780) the subreport and fixed the single values not showing up sometimes because the query used joins instead of left joins + aesthetic improvements.
• Fixed: (case 20780) the graph was flipped horizontally.

Customers Added By Date

• Added: (case 22261) customer email. Also tidied the report.

Customers With No Purchases After Date

• Added: (case 20048) a sortby parameter, tidied the report

GL Activity

• Added: (case 22063) a new parameter that lets you sort by Associated Customer, then Document Type instead of the standard Document Type if desired.

GL Entires By GL Account

• Added: (case 20733) set the Document and GL Entry level group header to repeat with " continued…" suffix if applicable.

Inventory By Part Type & GL Category

• Added: (case 18417) the ability to sort by the part type total columns (In Stock, Sales, Percent Profit) and an option to exclude the GL Category totals if you just want a summary. The ordering functionality required a substantial change to the report structure.

Inventory Detail By Part Type

• Added: (case 8217) vehicles with cost remaining even if they are not status A or H (noted on report).
• Added: (case 2086) a column for average core cost.

Inventory Summary

• Fixed: (case 22572) now includes vehicles with overallocated cost regardless of status and quantity in addition to vehicles with cost remaining regardless of status and quantity. (updated condition from > 0 to <> 0)

Inventory Summary By Source

• Added: (case 20507) a new third summary option, which will show each unique inventoryid/inventorystoreid item by tagnumber, store, and part type. Summarize option is no longer True or False; it is Part, Part Type, or Source. Tidied the report.

Inventory Exhausted

• Changed: (case 2086) updated the way average cost is calculated

Inventory Misc

• Changed: updated the way average cost is calculated, added a column for average core cost, and tidied the report.

Inventory Summary

• Added: (case 8217) vehicles with cost remaining even if they are not status A or H (noted on report).
• Added: (case 20172) the thousands comma separator to store quantity total. It was missing.

Inventory Summary With Cores

• Removed: (case 8217) deprecated. Inventory Summary includes cores, so this is not needed.

Label

• Added: (case 22257) Category. Category was on the standard inventory section of the report, but not the whole unit section.

Label Delivery Picking

• Added: (case 21160) a new report for printing picking labels from the delivery screen.

Labor Detail By Employee

• Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.

Labor Log By Employee

• Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.
• Fixed:(case 20738) hours rounding so decimals would always line up.

Labor Summary By Employee

• Fixed: (case 20315) report query; removed the JOIN to wagerate. user.wagerateid can be NULL.
• Added: (case 20165) estimated labor hours billed and labor charge for fixedlabor charge jobs using default workordertype rate or customer's custom labor rate.

Payment Receipt

• Added: (case 21365) payment terminal transaction fields for credit card payments through the terminal.
• Changed: (case 21365) some formatting in the terminal transaction section to make things more clear, added ----- header and footer and suppression on the authorizationcode line when it is absent
• Added: (case 21365) terminal-captured customer name and lines for PIN VERIFIED, SIGNATURE CAPTURED ELECTRONICALLY, and SIGNATURE NOT REQUIRED as applicable

Pick List

• Removed: (case 22486) cores.

Purchases From Vendor

• Changed: (case 22456) expanded grand totals, splitting them across two lines and giving them more horizontal room to grow and don't show the number mask.

Purchase Order Posting Report

• Changed: (case 22435) updated Posting # at the top to show actual Posting #, not purchaseorderhistoryid.

Purchase Order Receiving List

• Changed: (case 22430) location ordering. It now considers rank.

Received Items

• Added: (case 21793) the ability to group by source, if desired. Tidied the report and added back in Misc items, which were excluded previously. This report is absorbing the functionality of Received Items By Source.

Received Items By Source

• Removed: (case 21793) deprecating the report. Use the Receieved Items report instead.

Sales By GL Category

• Fixed: (case 22063) switched to using salesorderline.averagecost instead of salesorderline.cost for the cost column. Changed column header for clarity.
• Fixed: (case 21976) changed the UNION to a UNION ALL in the query.

Sales By Category, Detailed

• Removed: (case 21549) deprecating the report.

Sales By Invoice

• Added: (case 22489) a top level store grouping with tiered subtotals.

Sales By Lookup

• Removed: (case 21549) references to an old view, v_salesorderitem.
• Added: (case 21549) cleaned up the report, and added wildcard support to the lookup parameter.

Sales By State

• Fixed: (case 22692) a bad JOIN in the query that had been throwing off the totals due to row duplication.

Sales By Store Region

• Added: (case 21507) adjustments, which were missing.
• Fixed: (case 21507) Got rid of a superfluous JOIN to state in the query. Totals match against Sales By Invoice in testing.

Sales GL Entry Reconciliation

• Added: (case 20640) adjustments and a comment header.

Sales Insights

• Added: (case 21078) more options. Report now has an interval parameter that lets you pick Weekly, Montly, or Quarterly. A week is now considered Sunday-Saturday. Report is smart enough to know if an interval is incomplete and prints "so far" with the values. Widened bars in the bar graph. Improved all the queries with the new approach. Added customer # and part type # to the second and third sections respectively. Got pagenumber and N of M back in there in the page footer.
• Removed: (case 22139) decimals on the invoice and line count on the Sales Insights section.
• Added: (case 22139) partnumbers to top parts list.
• Fixed: (case 22139) Job Lines and Misc Lines grouping together in the part list and pie graph; they are separate now.

Sales Order 11in

• Fixed: (case 20831) replaced customerunit.customerunitid with customerunit.unitnumber when present.
• Added: (case 20164) setting for displaying "CONTINUED ON NEXT PAGE….." at the bottom of multiple-paged documents, except on the last page
• Fixed:(case 21122) fixed labor charge not showing up when there was no workclock activity
• Changed: (case 21122) firstname + lastname to just user name when printing labor detail.
• Added: (case 21365) payment terminal transaction fields for credit card payments through the terminal. An SO can have multiple payments, and therefore multiple paymentterminaltransaction sections - and there is handling for that.
• Changed: (case 21365) some formatting in the terminal transaction section to make things more clear, added ----- header and footer and suppression on the authorizationcode line when it is NULL. Added a section in the footer for when paymentterminaltransaction.amount * -1 <> paymentline.amount. I don't want to misrepresent the credit card transaction amount, but we can't apply the wrong amount to the balance.
• Added: (case 21365) terminal-captured customer name and lines for PIN VERIFIED, SIGNATURE CAPTURED ELECTRONICALLY, and SIGNATURE NOT REQUIRED as applicable
• Changed: (case 21762) job part and labor sections to show separate group totals when showing details.

Sales Order Lines

• Removed: (case 21976) deprecating this report.

Tag

• Added: (case 18604) a QR Code that links to the part on HTP if it is public/worldviewable. This can be disabled with a setting, but is on by default.
• Fixed: (case 20780) company product code in the QR Code - it was still hardcoded with a fake for testing.
• Added: (case 20967) dynamic formatting to Category so up to 50 characters can fit, with resizing.
• Removed: (case 20967) QR code functionality. This is temporary and will be added again when we can improve speed.
• Changed: (case 21794) updated barcode format for serialized parts to D
• Added: (case 21668) serial number below barcode when present and when the setting to show tag below barcode allows it (same setting affects both).

Top Parts Age Trending

• Added: (case 20780) a part type parameter.
• Fixed: (case 20780) the line graph data not populating correctly for the Make/Man grouping.

Top Part Sales

• Added: (case 21551) a new report showing top part sales, renamed "Top Sales Per Part Type" to "Top Part Sales" and cleaned up the report.

Top Sales Per Part Type

• Removed: (case 21551) deprecated the report, the updated and renamed version is "Top Part Sales"

Transfer Order

• Changed: (case 22436) the way serials are displayed, showing which serials go with which locations in the source and destination location columns

Vehicle Profitability

• Removed: (case 8217) deprecating. Vehicle Value Analysis is a superior report that covers this functionality.

Vehicle Upside Down

• Removed: (case 8217) deprecating. Vehicle Value Analysis is a superior report that covers this functionality.

Vehicle Value Analysis

• Changed: (case 15147) replaced fvehiclecostalloated with the new function fvehiclecostconsumed, which cuts out manual costing, pre-allocations, etc…

Weekly Sales Insights

• Added: (case 20780) percentages to the bottom 2 charts and added a 5th column to the top chart for averages. Swapped "Other" color from purple to gray to match all the other Trending reports.
• Changed:(case 20836) broke jobs out of "Misc Line Items" to have their own line.

Work Clock Times

• Fixed: (case 22255) a time duplication issue. The Internal Entries section now excludes activities tied to a work order type to prevent duplication of time clocked on a workorder and an activity.

Work Order Internal

• Fixed: (case 20909) updated margins, verfified database for every subreport, and fixed subreport parameter link for storeid - which may have been causing an "error formatting field object" issue.

Report Viewer

• Fixed: (case 20702) an issue where some fixed report parameter value defaults would act strangely when the user selected them.
• Fixed: an issue where date pickers for report parameters might show the year 1899 as the default value.
• Fixed: an issue where date report parameters with fixed values might not get formatted correctly.

Sales Orders

• Added: (case 19339) if the user voids a closed invoice and chooses to not void the payments, those payments are now unattached from the SO. This is to make it easier to find those payments in the future to associate them with another invoice.
• Added: if the user switches from a document type that locks prices to $0 to one that doesn't, the lineitem prices automatically go back to the default customer prices.
• Fixed: switching customers on an inventory adjustment document should no longer recompute the prices to not be $0.
• Fixed: (case 10321) manually adding items to an inventory adjustment document should no longer load prices that are not $0.
• Fixed: a recent regression where unnecessary popups were appearing when a SO was being voided (these warnings/errors don't matter if a document is being voided).
• Fixed: an issue where switching to a document type that doesn't care about price violations might not correctly clear price warnings.
• Added: a new "Card" payment button that allows the user to add a new payment from an external credit card terminal.
• Fixed: (case 20854) an issue where opening the return dialog for a saved SO might show the saved line items on that SO twice.
• Fixed: an issue where adding a new manual payment wouldn't always put focus into the first editable field in the list.
• Fixed: (case 20893) an issue where some of the right click options in the return dialog were not working.
• Fixed: hitting add payment buttons on the SO now properly puts the user into the payment list for immediate editing.
• Fixed: (case 21102) a query error that would be thrown when the user sent an item from the warehouse management screen to an inventory adjustment document if that item had been written down more than once previously.
• Fixed: (case 21157) edit closed SOs permission is now checked for whether the user can edit return reason on a closed document.
• Fixed: an issue where saving changes on a closed SO (required a special permission) would not save any changes on the last item.
• Added: if the user double-clicks a payment on the SO, the payment detail/external transaction dialog is brought up again. This allows voiding a payment that was accepted by mistake as well as viewing info about the transaction that created it.
• Added: the credit card payment buttons are hidden if the credit card module is not loaded.
• Fixed: (case 23012) an issue where the user could possibly delete a payment after accepting payment from the credit card terminal. Also, the user can no longer close a SO with an unsaved payment from the credit card terminal, as that would lose the transaction. The user must either void the transaction or save.
• Added: (case 7280) a non-modal attachments pop-up dialog for the user to manage attachments with. This dialog appears by default, but can be toggled on and off with the attachment button. If the user opens a document with attachments on it, the dialog is automatically opened.
• Fixed: an issue where text blinking stopped working due to a change in 2014.
• Fixed: (case 18835) an issue where sales orders for customers who required PO #'s wouldn't pop up the requirement dialog if they weren't buying at least 2 items. Now, the PO # field blinks and the warnings pop up if the invoice subtotal is greater than $0.
• Fixed: (case 22490) an issue where the "None Selected" option in the choose serial # popup wasn't working.
• Fixed: the "In use" checkbox in the configure adjustment types dialog now correctly accounts for sales order adjustments and fees on bids.
• Fixed: (case 22090) an issue where all modified job parts would always set the inventory id on save, overwriting any 'in-progress' action a user might be doing on the core management screen.

Search

• Changed: (Case 18642) Smart Search now replaces $STORES with a list of OR statements specifying inventoryid. Not required, but can easily limit searches when using search modules.
• Changed: (Case 13005) Smart Search Module list now uses checkboxes instead of a sticky list, and its right-click menu allows for selecting or deselecting everything.
• Fixed: Search Defaults Page was not restoring Smart Search Module default selection when clicked (it did nothing instead).
• Fixed: (case 20517) an issue where doubleclicking a vehicle attachment icon on the vehicle search could cause an application crash.
• Added: a 'lookup VIN' button next to the VIN field, similar to the vehicles screen.
• Changed: stock # field is now slightly larger, to facilitate longer stock #'s.
• Fixed: several places where dismantled date was incorrectly labeled teardown date.
• Removed: dismantled date from the dropdown searches since its already in the date picker search, which is a bit easier to use.
• Fixed: the dropdown search for 'dismantled' now correctly looks at the dismantled date.
• Fixed: (case 23108) an issue where image data from previous searches were not cleared when the user performed a new search.
• Fixed: (case 23136) an issue where the model lists were based on the id of the currently selected part type instead of the type set id of the currently selected part type.
• Fixed: (case 21654) an issue where the vehicle search page did not remember the user's selected store(s) to search. This system now works identically to the part search stores.

Transaction List

• Added: (case 11402) all date and date/time filters now have a 'date range' dropdown column where the user can choose options like 'Last 90 Days' or 'This Month'. When one of these is chosen, re-running the report again later will automatically move the dates forward.
• Added: (case 11402) support for "Custom: Relative" date ranges. These are like fixed date ranges (the user chooses the start and the end) except that the dates are remembered as offsets from the current date (such as 120 days ago or 3 days in the future). This gives users the ability to save search templates that have date filters that 'move' as the user runs the filter in the future without having to use one of the specific date ranges supplied by the system (such as "This Month" or "Last Year").

Utilities

Print Queue

• Fixed: (Case 21424) Configuration Default settings have been improved
• Fixed: (Case 20820) Support for default parameters has been added.
• Fixed: (Case 20582) Network connection loss should no longer crash PrintQueue
• Fixed: (Case 19307) Support has been added for custom report titles
• Fixed: (Case 20144) Error reporting has been improved.

Vehicles

• Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
• Fixed: (case 19111) vehicle costs could be incorrect if any POs had invalid vendors.
• Performance: saving large teardowns can now be as much as 3 times faster, especially on slow connections. Many queries that were being run to see if inventory on the teardown had been modified since it had been loaded has been combined or eliminated.
• Fixed: (case 20849) an issue where, if the user changed a vehicle's status, user status, or (especially) location, then choosing to cascade that change to all associated inventory records, that change might get rolled back if there were changes to the same items on the bids/teardowns tab.
• Added: if the user cascades location changes from a vehicle to parts on a teardown, that change is now immediately reflected on the teardown screen without having to reload.
• Added: the retail price in the location/status cascade dialog is now right aligned and sorts correctly.
• Fixed: (case 20896) an issue where vehicles wouldn't save reordered attachment ranks if they hit the save button instead of the close button.
• Fixed: (case 20955) an issue where the hidden field vehicle.dismantled was incorrectly being set by the 'purchase date' field instead of the dismantled date.
• Fixed: (Case 16989) make sure any new quantity on teardown items doesn't go into the variance location.
• Added: (case 23034) misc parts on a vehicle teardown will no longer copy the year/make/model/VIN/body style from the vehicle when it is changed. Only Standard parts will automatically copy that information to all associated parts.
• Fixed: (case 21953) a rare issue where a teardown/bid item with a bad inventory type might cause a crash when loading the vehicle.
• Added: (Case 21416) Added a new graphing tab to the vehicles screen. This area shows a vehicle 'break even' graph showing cost and revenue over time.

Vendor

• Fixed: (case 14034) if the user attaches a duplicate file, they will now see a user-friendly error message with a button to quickly remove the duplicate file.
• Fixed: if a price class doesn't have a store-specifc override, the "Default" entry is automatically selected.
• Fixed: (case 10091) an issue where selecting a new store to create store-specific price class overrides might save all the values as 0.
• Fixed: a possible crash when editing a price class and switching whether it is global.
• Fixed: (case 21814) an issue where loading a vendor, then loading another vendor without clearing the screen in between might cause attachments to move between the vendors.
• Fixed: minor issues with button sizing.

Vendor List

• Changed: position of controls on the screen has been standardized with other screens.
• Fixed: (case 15015) phone/fax searches now allow the user to search correctly instead of treating the input as a number.
• Added: date based searches now use a date-time picker to avoid ambiguity of date formatting.
• Performance: date based searches should now be slightly faster.
• Changed: (case 23171) vendor smart searches with multiple words will now automatically require all words to be present in the results.
• Performance: removed some unnecessary searching that happened as part of a vendor smart search that may have added slowness to these searches, especially when no results were found.

Work Orders

• Fixed: (Case 20339) a crash when sending items from search to a WO from the right-click menu.
• Fixed: (case 20023) an issue where inventory on WOs would use retail price instead of customer pricing for jobs set to use customer pricing.
• Fixed: some minor display issues causing some controls to not be placed like on other screens.
• Performance: deleted parts now run a single query to delete locations/order routing/etc. This will make saving a little faster when items are deleted.
• Fixed: (case 18878) estimate WOs no longer prompt the user for serial #'s for master parts or job parts.
• Added: if the user changes the 'estimate' checkbox, all serial # related attention icons are refreshed, so that if a WO leaves estimate state, the user will see that they need to choose a serial #.
• Fixed: an issue where the user could not view the part requests on voided or closed WOs.
• Added: (case 7280) work orders now support attachments. Drag and drop attachments into the new popup to attach things to a WO. Use the attachments button to show/hide the popup.
• Added: (case 21878) if the user attempts to load an inactive work order type, the work order will now load correctly.
• Fixed: several crashes related to work order types that were inactive.
• Fixed: if the user edits the current work order type and renames it, it will be renamed in the dropdown correctly.
• Fixed: (case 21883) an issue where the user could delete or add items to a closed WO.
• Fixed: if the user sends items from search to a closed WO, those items will be ignored.
• Fixed: the 'core returned' checkbox in the edit item dialog no longer can be toggled if the work order is closed or voided.
• Fixed: an issue where blank, empty items would be unnecessarily added to the bottom of a WO if the user added an inherent core or dirty core exchange to an item on a WO.
• Fixed: (case 22090) an issue where all modified job parts would always set the inventory id on save, overwriting any 'in-progress' action a user might be doing on the core management screen.

Placeholder release note:

Version 13 was skipped and not released as a standalone public release. Its changelog content was rolled into Version 14.

Release 12.7

Customer (17569)

• Fixed: (case 22484) an issue where a user without permission to edit customers might get an erroneous change detected message when they open the customer screen.

Global Settings Extension (17563)

• Fixed: an issue where date report parameters with fixed values might not get formatted correctly.

Interchange (17563)

• Fixed: if the user hits enter when they're in the 'search area' of the interchange screen, a search will be performed, but hitting enter when entering interchange records down below will treat the 'enter' as a spreadsheet enter.
• Fixed: a crash that could occur if someone doubleclicked an item with a dropdown where an invalid model was in a dropdown.
• Removed: (case 22494) the sales meta-data no longer looks at non-stocked item sales. This speeds up sales data loading.
• Added: the sales meta-data now also looks at work order usage history.

Report Viewer (17563)

• Fixed: an issue where date pickers for report parameters might show the year 1899 as the default value.
• Fixed: an issue where date report parameters with fixed values might not get formatted correctly.

Sales Orders (17681)

• Fixed: (case 18835) an issue where sales orders for customers who required PO #'s wouldn't pop up the requirement dialog if they weren't buying at least 2 items. Now, the PO # field blinks and the warnings pop up if the invoice subtotal is greater than $0.

Vehicles (17566)

• Added: (case 23034) misc parts on a vehicle teardown will no longer copy the year/make/model/VIN/body style from the vehicle when it is changed. Only Standard parts will automatically copy that information to all associated parts.

Vendor (17562)

• Fixed: (case 21814) an issue where loading a vendor, then loading another vendor without clearing the screen in between might cause attachments to move between the vendors.
• Fixed: minor issues with button sizing.

Work Orders (17568)

• Fixed: Restored department that was removed in a previous change
• Fixed: (case 21883) an issue where users could delete items off of a closed WO.

Release 12.6

Payment Entry

• Fixed: an issue with negative values (case 22433)

Purchase Orders

• Fixed: (case 21865) an issue where POs would automatically be marked as done receiving when a user without permission to receive inventory would save them after all quantity was received.
• Fixed: (case 22419) an issue where transfer orders that were created due to a multi-store purchase from inventory overview would not properly update the 'on order' and 'on hold' quantities.

Reports

Pick List

• Fixed: Excluded cores from the Pick List.

Sales Orders

• Fixed: (case 22423) an issue where the various blinking static fields stopped blinking correctly.

Release 12.5

Customers

• Fixed: (case 21196) an issue where customer default invoice terms were not being selected correctly when a customer was loaded.

Parts

• Fixed: the location field is now larger

Work Orders

• Fixed: (case 21188) an issue where the user could not view the part requests on voided or closed WOs.

Release 12.4

Purchase Orders

• Fixed: (case 21052) an issue where showing the returns dialog could cause a crash.

Sales Orders

• Fixed: (case 21102) a query error that would be thrown when the user sent an item from the warehouse management screen to an inventory adjustment document if that item had been written down more than once previously.

Release 12.3

Purchase Orders

• Fixed: an issue where the return dialog defaulted to just showing purchases from today instead of the last 90 days, as intended.
• Fixed: (case 20893) an issue where some of the right click options in the return dialog were not working.

Vehicles

• Fixed: (case 20955) an issue where the hidden field vehicle.dismantled was incorrectly being set by the 'purchase date' field instead of the dismantled date.

Release 12.2

Customer

• Fixed: (case 20872) an issue where the customer option list wasn't displaying the options it should show.

Parts

• Fixed: an issue where the condition field on the parts screen was not in the proper location in the tab order.
• Fixed: (case 20728) an issue where sending parts from the parts screen to the part modification screen wouldn't load anything up.
• Fixed: (case 20896) an issue where parts/vehicles wouldn't save reordered attachment ranks if they hit the save button instead of the close button.

Vehicles

• Performance: saving large teardowns can now be as much as 3 times faster, especially on slow connections. Many queries that were being run to see if inventory on the teardown had been modified since it had been loaded has been combined or eliminated.
• Fixed: (case 20849) an issue where, if the user changed a vehicle's status, user status, or (especially) location, then choosing to cascade that change to all associated inventory records, that change might get rolled back if there were changes to the same items on the bids/teardowns tab.
• Added: if the user cascades location changes from a vehicle to parts on a teardown, that change is now immediately reflected on the teardown screen without having to reload.
• Added: the retail price in the location/status cascade dialog is now right aligned and sorts correctly.
• Fixed: (case 20896) an issue where parts/vehicles wouldn't save reordered attachment ranks if they hit the save button instead of the close button.

Release 12.1

Purchase Orders

• Fixed: (case 20857) an issue where the 'core exchange' column in the POs return dialog was hidden, making it impossible for the user to specify that a return associated with an inherent core charge was an exchange instead of just a credit. This issue was introduced in version 12.

Sales Orders

• Fixed: (case 20854) an issue where opening the return dialog for a saved SO might show the saved line items on that SO twice.

Release 12.0

Highlights

• Added: all print jobs, successful or failed, now get put into the report print queue (this can be reviewed on the report viewer screen). All print errors can be reviewed here, print jobs can be reprinted/retried, and total execution time can be reviewed. This will help improve print speeds in the future.
• Improved: all print previewing has been improved. Cancelling/reprinting a preview now happens faster. All errors are reported in the standard ITrack error dialog. All print previews now go into the print queue.
• Added: reports in the report viewer can now be marked as 'favorites'. This is a per-user setting so that each user can remember the reports they often print.
• Added: various improvements to the report viewer screen's presentation.
• Added: whenever the user performs an advanced print operation, they can easily choose print quantity as well as whether they'd like to print the job or email/save a pdf (email/save require the advanced print server solution).
• Added: the parts and vehicles screens now show a floating attachment preview dialog. With this, the user can easily view images for the current part or vehicle without having to go to the attachments page. This popup can be located on a second monitor if the user wishes.
• Added: there is now a global hotkey (editable in the configure->hotkeys dialog) that, when held down during a print job, will pop up the advanced print dialog. This makes changing print quantity or emailing any print job easy.
• Changed: the way accounting is saved has been changed to make gl reports clearer.
• Added: each store can now have a remittance address in addition to its street address.
• Added: the returns dialog on the sales order screen has been merged with the one on the purchase order screen so that each area got all the benefits the other had.
• Added: sales orders now allow the user to specify a reason for the return.
• Changed: many screens got adjusted so that whether the user has done a normal search or a location specific search, results are sent to other screens in a consistent way.
• Added: inventory can now be specified as single quantity items. In the future, this will signify items that cannot exist at multiple locations.

Tools/Controls

• Performance: upgrades to our collections that (in some cases) eliminate as much as 85% of the time spent in some loops.
• Added: support for icons on 'push-like' buttons.
• Added: support for typeable columns in lists can now support a 'maximum length' for the data that the user can enter. If the user enters more than this, they hear a beep and are stopped.
• Performance: formatting of list text has been sped up somewhat.
• Added: a shared city/state/zip field group to consistently handle all areas where these linked fields should look one another up.
• Fixed: an issue where attachment interfaces would not lock down correctly in some scenarios. Also fixed an issue where the public checkbox wouldn't work correctly if there was more than one check in the list.
• Fixed: an issue where custom "ok" message boxes wouldn't have their custom button text shown.
• Fixed: an issue where times containing midnight might save incorrectly. Also an issue where date/times might save as 1899-12-30
• Added: doubleclicking an item in a tree control now toggles the expansion of that item.
• Fixed: an issue where the list footer would become invisible in some scenarios.

Accounting

• Changed: (case 18825) the way gl transactions are built has been completely redone. The main upshot from this is as follows:

1. When a SO is saved/finalized/voided, all payments attached to that invoice as well as all external WOs that are on the SO have their accounting put into the same gl transaction. This makes it easier to relate all the 'activity' of the invoice in one place.
2. Now, there are many gl transaction types that represent all the areas of the software the user could trigger accounting from. This will make it easier for accounting reporting to say more exactly what the user did to cause the activity. For example, a single invoice could have multiple gl transactions over its lifetime. The following could be the example transactions for a single SO: "Sales Order Saved", "Sales Order Finalized", "Sales Order Reopened", "Sales Order Finalized", "Sales Order Voided".

• Fixed: an issue where voiding payments was incorrectly attaching the balancing entries to the original transaction, possibly at the original transaction date. Now this gets a new "Payment Voided" transaction at the current date.

Appraisals

• Changed: (case 19419) by user request, the 'current quantity on hand' retrieved as part of sales appraisals will now limit the matched results to just items that match the category of the current item (if it is filled out). Otherwise, all categories are considered.

Approvals

• Fixed: (case 18952) an issue where the stock category was not correctly being displayed when price rules were being loaded. The value of All would save but display as Standard on the next load.
• Fixed: an issue where changing the document type of a price rule was not being saved.
• Fixed: another issue that was causing part types from being saved on price rules.

Crystal Reports Extension

• Added: (case 17915) printing reports now logs successful print information as well as errors to the print queue.
• Added: proper support for 're-printing' items in the report queue. That way, they won't get another entry in the queue.
• Added: print previewing now inserts an 'in progress' entry in the print queue, which is overwritten up by the report viewer screen.
• Added: (Case 18265) the 'choose printer' dialog now has the ability to let the user choose to email a report instead, or archive it on the server. In addition, the user can have a print get 'delayed' in the queue if they wish to schedule it for later.
• Added: the archived reports subdirectory now has a default value per report type. This way, all saved reports will automatically be saved into sorted subdirectories.
• Removed: if the user performs an advanced print, the windows printer dialog no longer shows up. Instead, we show the ITrack choose printer dialog, which allows choosing to email or archive.
• Added: (case 18265) a global hotkey that controls whether to automatically show the advanced print options popup during any print. This defaults to ctrl + left click when printing, but can be rebound in the hotkeys dialog.
• Added: support for auto-complete options in the email dropdown.
• Added: if the user enters a new email address in the dropdown, future email operations will 'remember' that option.
• Fixed: newly created report queue entries are now correctly cleaned up, avoiding memory leaks.
• Changed: reprinting a report queue entry no longer updates the 'created by user'.
• Fixed: crash that would occur when cleaning up report queue entries.
• Changed: if the user chooses to email or archive a report, all reporting code is skipped.
• Added: support for delayed printing and emailing. If a print job is going to be printed in the future, the print operation is skipped and logged in the queue.
• Changed: the error report field in the report queue can now go up to 1000 characters instead of being limited to the previous 250 characters.
• Added: there is a new setting ("Printing"->"Advanced print management server installed"). The advanced printing dialog now deactivates various controls if this setting is off. Essentially, any controls that require report commander to be present are disabled.
• Added: (case 19676) the advanced print dialog now has a quantity edit so that the user can easily change the print quantity without going into the windows printer dialog.
• Added: report auto-updater now creates new reports with a category of "Report".
• Added: Configure->reports page now has handling for setting a report category.
• Fixed: (case 19832) an issue where exporting a report add script with parameter values could cause a query error.

Core Management

• Fixed: (case 19052) an issue where typing into the part lookup on the customer cores (filter at the top) or returned cores (core bank lookup) tabs, if the user was taken to search, any result they chose would not be returned to the screen correctly.
• Changed: the part filter field on customer cores has been modified to work more like the lookups on other screens. This should make the usage of the screen more obvious than before.
• Changed: (case 17587) the document # column in the customer cores tab has been reformatted to match the format of the returned cores tab.
• Removed: (case 17587) the document # columns no longer show document line item #.

Customer

• Fixed: (case 18861) an issue where the user could type in an invalid tax item name and the value would not be cleared before saving, leading users to believe a valid value would be saved.
• Fixed: (case 18861) an issue where no tax item selected was being saved with an invalid value (now it is correctly set to NULL).
• Added: (case 18825) creating finance charges now falls under a gl transaction type of "Finance Charges Finalized".
• Fixed: (case 18961) an issue where the Save & New button did not clear the screen after saving, making it seem as though nothing had happened.
• Fixed: (case 19108) if a new customer was created without the user going to the tax/payment info tab, the default invoice terms would not be saved correctly.
• Fixed: (case 18794) an issue where hitting Save and Clear on a customer with attachments, then creating a new customer could 'move' those attachments to the new customer.

Customer List

• Fixed: an issue where searching by customer website would throw a database error.
• Fixed: (case 18945) a database error that would occur if the user was searching for customers at a specific store ("Customers For All Stores" is unchecked) and they were searching by an address field (due to the recent additions allowing the system to simultaneously search alternate addresses).

Database

• Added: support for new 'time elapsed' column in the reportqueue table.
• Added: (case 18727) support for delayed print operations in the print queue (reportqueue.waituntil). There is also now an index on the fields that the report server scripts uses to find printable jobs.
• Fixed: the triggers and functions that keep locations up to date no longer use a value of -1 to represent 'no location'. This was causing issues on some databases that were in strict mode. Now, the system always uses NULL.
• Added: (case 18825) several previous gl transaction types have been retired and many new ones have been added. This is part of a push to make gl transactions a descriptive and useful way to review accounting.
• Removed: the old comments field in gl transactions. It was generally just used for the same purpose that we now use type for.
• Fixed: (case 18861) customer.taxitemid has been corrected to have a value of NULL instead of -1 for those rows where -1 was being inserted.
• Fixed: (Case 18852) PO adjustments that were created before version 11 wouldn't show up on their posting correctly anymore because of the innodb changes. This fixes it.
• Added: (case 18001) salesorderline.customerprice, which is a transactionalized copy of the price the salesman was presented with by default. All historical sales have had their value set retroactively for future reporting.
• Fixed: (case 19027) the f_invoicepaid function had different versions on different databases. This should standardize and speed up the function slightly.
• Performance: (case 19032) customer balance calculating functions were being too specific about what index to use. Now, they will use whichever one is best. This showed some minor speed improvements on very large customer activity.
• Changed: maximum make length increased from 15 to 50 characters.
• Changed: inventory make length increased to match the 50 character limit of other tables.
• Fixed: (Case 19047) an issue the user would get a database error when deleting locations.
• Added: (case 17859) a new permission to control whether the user can print documents that have outstanding price violations. By default, this is on for all users who could normally edit a SO.
• Added: (case 17070) support for a user-entered 'return reason/code' that can track 'why' an item was returned.
• Removed: a view that was created for a previous report. It is no longer in use and it not well optimized. All reports should use fgetattachment_id instead.
• Removed: (case 3886) the after update trigger on vehicles has been removed. This had been a previous way to keep year, make, model, etc synchronized between vehicle and inventory.
• Added: (case 6507) a search option to inventorysetting to allow the user to search for parts by the tag # of any collections that item is in. This makes printing tags for all collection members easy.
• Fixed: (case 17943) selling/deleting a whole unit should reject all open bids. This solves issues where users would accept bids after the vehicle was sold, marking the vehicle as available again. This should trigger if the user sells the whole unit on a SO, consumes it on a WO, or returns it to the vendor on a return PO.
• Changed: column order rearranged in the inventory table to make more sense.
• Added: (case 6656) there is now a 'singlequantity' flag on inventory. This flag will track items that should never have a quantity greater than 1 and should never have more than one valid location.
• Updated: all previous vehicle whole units set to 'Single Quantity' Parts.
• Fixed: an issue where inventory.isacore allowed NULL.
• Added: (case 18391) vehicle bids now store an 'assigned to' user as well as the date they were closed and what user closed them. All closed bids have had their date closed set retroactively, where possible.
• Added: (case 17070) a new table where users can define a list of 'return codes/reasons'. These can be chosen between when performing returns on an invoice.
• Added: (case 17070) a new permission controlling who can manage return codes.
• Added: 3 initial return reasons to handle the common cases.
• Fixed: the right-clicking graphing template has been modified so that if the user uses a string column as the x axis of a scatter graph (but the strings contain numbers), the graph should look correct.
• Added: (Case 19658) Schema for logging search times to log_search.
• Changed: (case 19042) the previous part search column "Entered By (user id)" is now no longer searchable and has been replaced with "Entered By User" which allows the user to search by user name.
• Added: comments to report table columns.
• Added: new column for tracking a report's category, separate from its type.
• Added: speed index to the report table based on name.
• Fixed: (case 12267) an issue where vpickablejobpart was not defined correctly, causing most items to be unpickable.
• Added: (case 19865) report.name is now enforced unique per report type.
• Fixed: a misspelled column name in a location delete trigger.
• Fixed: (19810) an issue where several sales order job fields wouldn't aggregate correctly on the totals tab of the transaction list.
• Added: (case 19467) notes for why a report subscription exists

Deliveries

• Changed: by customer request, the 'Skip Delivery' button on the picking tab has been renamed to Skip Pick/Delivery to more clearly denote that the items will not be picked.

Ebay Extension

• Added: (Case 17835) There is now a last updated date displayed on the auctions page of the eBay module
• Added: (Case 17835) Invoicing from eBay will now create a basic customer record if no customer with a matching email exists and the Setting "Ebay Create Customer" is set to true and receive at least the email from the ebay transaction.
• Added: (Case 17835) Added a column "Invoiceable" that shows the count of completed transactions with no invoiceids associated. (an invoice id is not added until ebay is closed and re-opened, so this value will not either)
• Fixed: (Case 17835) Fixed an sql error when updating ebay auctions.
• Fixed: (Case 17328) Added 'Freight' as a shipping option.
• Fixed: (Case 17945) Fixed a crash when launching ebay without a user account.
• Added: (Case 19012) Added a transaction tab
• Fixed: (Case 19012) Filtering now works correctly.
• Fixed: (Case 18840) Freight shipping now overrides any cost or free shipping settings
• Fixed: (Case 19012) Now hiding the ItemID column, since users have no use for it.
• Fixed: (Case 19012) Initial load speed dramatically improved.
• Fixed: (Case 19305) Open Screen permission is now correctly followed.
• Fixed: A query error was corrected regarding invoices.

Common Resources

• Added: a generalized version of the picture viewer dialog used on search. This will be usable by other screens that would like to show image attachments for parts and vehicles.
• Moved: the view pictures dialog from search has been moved to common resources so it can be shared between screens.
• Added: the title text of the pictures dialog is now more descriptive, and shows total number of images in the title.
• Changed: the last location of the pictures dialog is no longer stored in the ini file.
• Added: the picture view dialog now uses a type of image cache that holds onto previously loaded file information. This should make load operations faster if the user goes back and forth between items.
• Fixed: the page up/page down buttons seemed to do the opposite of what was expected when scrolling through images.
• Added: support for showing images on unsaved parts and vehicles.

Global Settings Extension

• Fixed: an issue where the print queue page on the report viewer screen would incorrectly ignore the 'show printed' checkbox.
• Added: support for print logging in the report queue.
• Added: support for mouse buttons in key bindings.
• Added: doubleclicking a keybinding now allows the user to immediately rebind that action.
• Added: an auto-complete handler that looks up all historical email addresses of users, customers, customer alternate addresses, and previous emailed reports.
• Changed: to support the new way that search results are sent between screens, the ebay handler had to be updated.
• Added: support for various new report viewer features.
• Performance: when a user closes a screen, column order is now saved with an INSERT ON DUPLICATE KEY UPDATE instead of REPLACE INTO, which will reduce traffic and disk writes.
• Fixed: (case 19255) an issue where user settings would not save any changes if the user logged out and logged back in before closing the application.

Home

• Fixed: an issue where, if WO type of "All" wasn't first in the list alphabetically, it would not correctly look at all types.
• Changed: (case 18791) the work orders tab now uses tagnumber instead of vendorcode and partnumber for all work order master parts. This should resolve issues where some users would get inconsistent labeling for master parts
• Added: tooltips to all columns headers as well as the body of the work orders tab.
• Added: the user can now click into the description and notes fields on the work orders tab, making it easier to read multiline entries and copy text out.
• Added: (case 16389) 2 new columns to the work order tab: % Done and Job Status. % Done shows a value that represents what % of the jobs on the WO are now at status Done. The Job Status field shows the status detail of all jobs on the WO. These fields show VOID if the WO is void and the status shows as FINALIZED if the WO is closed. In all other cases, the columns receive the most appropriate status colorization to match the colors used for statuses on the WO screen.

ITrack Online

• Added: any javascript errors encountered on any pages being navigated to will now be automatically suppressed on client systems, but not in testing.

libITSQLFramework

• Fixed: the timestamps in the query log now use local times instead of UTC times. Also, the values are formatted a bit more logically.

Login

• Fixed: a minor flickering issue when opening up the configure->users dialog causing it to load slower.

Options

• Added: the configure->Stores dialog now has an area for a remittance address and phone #. By default, this is the same as the street address of that store, but the user can make them differ. Soon, this information will show up on billing statements and invoices.
• Added: the configure stores dialog now uses a state auto-complete to populate the state dropdowns, which will speed up loading slightly.
• Added: changes to configure stores dialog to copy address information to the remittance area if the 'use same address' checkbox is checked.

Parts

• Fixed: (case 18858) an issue where the parts screen was setting locationid as part of its insert/update queries, when this field was supposed to be omitted. It is handled elsewhere, and this was causing errors on databases with strict mode on (as virtual locations used a value of -1 which is no longer an allowed value.
• Fixed: (case 6663) the refresh button on the parts transactions tab now refreshes the transaction cache, so any newly created transactions will be found. For speed purposes, the previous/next page buttons will not rebuild the cache.
• Performance: the process of building the cache of transaction history for the transactions tab has been sped up. This will make loading this information faster, especially on slower networks.
• Changed: attachment management has been upgraded to a newer methodology that will be compatible with a new picture viewer pane.
• Changed: several things about the header of the parts screen have been modified to introduce consistency between the parts and vehicles screens.
• Removed: the advanced page no longer checks to see if the enter key should work like tab. This is to establish consistency with other areas.
• Added: (case 1545) this screen now displays a non-modal picture dialog when the user opens the screen. It will allow the user to view part and vehicle images for the currently loaded part at a glance. The dialog is the same one that has been in use on the search screen since version 1. The user may position the dialog on another monitor or in unused space. The dialog is automatically hidden if the user goes to another screen.
• Added: the screen will remember if the user wishes to show the picture dialog, and automatically show/hide it the next time the screen is opened.
• Added: The user can toggle whether the pictures dialog is visible using the new 'toggle' button at the top of the screen.
• Added: user hotkey (can be customized in configure->user hotkeys) for toggling the state of the picture dialog. The default is "Ctrl + P".
• Added: new tool tips for all header controls.
• Added: if the user adds/removes/edits any attachments on the current record, the picture dialog is refreshed.
• Fixed: an issue where image ordering might be overwritten the next time the user opened a part.
• Added: (case 6507) a button to the links page that performs a search for all members in the current collection. This makes printing tags for all collections members easy.
• Fixed: an issue where, if there was an error while saving collection components, the user might not be able to correct the issue and save again.
• Added: (case 17595) as part of saving new collection component items (such as for assemblies), the user is warned if the tag #'s they enter match any existing items in inventory.
• Fixed: an issue where inventory tagnumber was saving only 20 characters, when it was supposed to be 50 characters.
• Added: (case 6656) a new checkbox on the advanced tab called "Single Quantity Part". Parts with this checked attempt to enforce that their quantity never goes above 1 and they never have more than 1 valid location. This represents 'discrete' parts that only exist once in any store (such as vehicles and most parts created from teardown).
• Added: (case 6656) 2 new errors on save if the user has 'Single Quantity Part' checked and the quantity on hand is greater than 1 or there is more than one valid location.
• Added: (case 6656) any 'new' collection components created as part of a collection (usually an assembly) will create all 'child' parts as 'Single Quantity Items' if their quantity is 1 or less. This should make it so that most of these parts won't ever have to end up in a state where they have multiple locations when that doesn't make sense for such 'simple' parts.
• Fixed: (case 19678) an issue where Q&A on new serials was not saving correctly.
• Fixed: (case 19663) an issue where clearing the parts screen after loading a part with a single serial # would not clear the "Serial #" field on the part info tab.

Part Configuration

• Fixed: a possible database error that could happen if the user entered a make longer than the maximum allowed make.
• Fixed: the user could not 'uncheck' the start/end date on part type messages.

Payment Entry

• Added: (case 18825) when payments/discounts/credits are saved, they are now put under a GL transaction type of 'Payment Batch Updated'.

Print Queue

• Fixed: (Case 17810) All errors are now written to file and an exception has been added for writing errors to the database.
• Fixed: (Case 18665) Added timers, written to db. It should also update lastsenton.
• Fixed: (Case 18160) Now has an enterprise handler that should pull in printers using fgetsetting.
• Fixed: (Case 19360) Syntax errors and handling for when no parameters are passed.
• Fixed: (Case 19360) removed an errant else clause possibly causing failure loops
• Fixed: (Case 19360) execution time now correctly quoted.
• Fixed: (Case 19360) PrintQueue now handles missing reports instead of crashing
• Added: (Case 18528) error reporting emails
• Fixed: (Case 18430) Now enabled report commander's native error logging. -v flag effects it. To set a custom logfile, a new config setting 'reportcommanderlogfile' exists.
• Fixed: Printing reports no longer makes a pdf
• Fixed: Saving files to folders no longer deletes them
• Fixed: (Case 18727) Now supports a waituntil date/time which specifies when a report should print.
• Fixed: (Case 19605) Printing to the selected printer now works for reports that have No Printer checkbox checked in the crystal report file.
• Fixed: (Case 19718) Python now corrects the product config setting from ITrack Enterprise to ITrackEnterprise
• Fixed: (Case 19406) We now group_concat on | for parameters to avoid splitting off and ignoring subquery parameters.
• Fixed: (Case 19484) Printqueue now uses fsetsetting to let the other products know that the Advanced Print Management Server is installed.
• Added: a bunch of comments to make PrintQueue.py simpler to understand, as well as a convenience method for query error handling.
• Fixed: (Case 19850) Added some error handling for when queries return no results.
• Added: (Case 19850) Added a setting emailerroron, which when set to False will turn off email error reporting
• Fixed: (Case 19850) Allowed not specifying a printer.
• Fixed: (Case 19878) Fixed another crash

Purchase Orders

• Added: (case 18825) future PO/TO accounting will now be done under GL transaction types of 'Purchase Order Received', 'Transfer Order Received', 'Purchase Order Voided', and 'Transfer Order Voided'.
• Changed: the returns dialog on the SO screen now shares resources with the PO return dialog, this should help them have the same features in the future.
• Added: by user request, the PO returns dialog now has many features that were only in the SO return dialog up until now:
• Previous/next page buttons
• Added: PO return dialog now has a document # filter edit. The user can enter a document # (wildcards supported), or enter something in the "store #-document #" format.
• Changed: (case 6656) the error attention icon/popup related to receiving a vehicle a second time has been generalized to include any parts that are 'Single QUantity Items' (whole units count).
• Added: a new warning attention icon/popup related to whether it looks like a PO will cause a single quantity part to go above 1 QoH. This is a warning because the user is not actually receiving the stock right now.
• Fixed: an issue where a user with permission to edit POs after they have been marked as Done Receiving wouldn't see attention icons/warnings regarding changes they were making. Now, the presence of the warnings is based on whether the user can fix the issue.
• Fixed: an issue where the 'too many locations chosen' pop up dialog on PO save would sometimes show the incorrect number of 'bad lines'.
• Changed: error/warning attention icon hover text has been changed to be more consistent with other screens.
• Added: when the system shows warnings/errors that 'Single Quantity' items (such as vehicles) will get a quantity above 1, it now checks quantity across all stores, as single quantity items can only have a single quantity at any location at any store.

Reports

Billing Statement

• Added: (case 18402) a setting to hide terms. They will show by default.
• Changed:(case 18218) mode setting name and options.
• Fixed: (case 19138) specified sort order in Activity and OIA sections: date, store, salesorder.
• Added: (case 17516) settings for alternate address and logo layouts at the top of the document for lining up with envelope windows and preference. This was also done to the SO report. Billing calls a global setting. SO calls a store setting.
• Changed:(case 18805) replaced store address info in the tearoff with remittance info.
• Fixed:(case 19932) suppressed the Finance Charge line in OIA mode when it is 0.00.

GL Activity

• Changed: (case 18134) renamed GL Sales Activity report to GL Activity. Improved the report to include glentries from all types of documents, sorted by the document and transaction that generated the entries.

GL Entries By GL Account

• Changed: (case 18138) Combined GL Entry Detail By Account and GL Entry Summary By Account functionality into a new report: GL Entires By GL Account. You can summarize by GL Account, GL Entry, or Document of Origin.

GL Entry Detail By Account

• Removed: (case 18138) functionality has been folded into GL Entries By GL Account.

GL Entry Summary By Account

• Removed: (case 18138) functionality has been folded into GL Entries By GL Account.

GL Entry Verification

• Removed: (case 18140) Deprecated report.

Inventory Age

• Added:(case 16912) this is a new FIFO report that figures out average age and oldest per SKU. Requires FIFO.

Labor Summary By Employee

• Changed: (case 18671) renamed some column headers.
• Fixed: (case 19135) non uservisible activity were rows showing up. Now they are not.

Packing Slip

• Fixed: (case 19347) the report was showing date closed instead of date, which was sometimes showing 1899 for open SOs. This now matches Sales Order 11in. I also hid shipping information when appropriate the for Ship Method.

Purchase Order Posting

• Changed: (case 18137) now displays postingnumber instead of purhcaseorderhistoryid.

Received Items

• Changed: (case 18137) now displays postingnumber instead of purhcaseorderhistoryid.

Received Items By Source

• Changed: (case 18137) now displays postingnumber instead of purhcaseorderhistoryid.

Received POs With Unapproved Postings

• Changed: (case 18137) now displays postingnumber instead of purhcaseorderhistoryid.

Sales By GL Category

• Fixed: (case 19370) this was referencing an old view, recently deprecated for being inefficient. Updated the report query to use the UNION salesorder line and salesorder adjustment information like other SO reports. Note that adjustments do not have a glcategory. They are still included in the report under "unassigned"
• Changed: (case 18133) combined Sales By GL Category, Sales By GL Department, and Sales By GL Department And Category into one report with multiple summary levels.

Sales By GL Department

• Removed: (case 18133) functionality has been folded into Sales By GL Category.

Sales By GL Department And Category

• Removed: (case 18133) functionality has been folded into Sales By GL Category.

Sales By Invoice

• Changed: (case 18360) updated with a new mode parameter to view the information at different levels: lineitem, salesorder, or day. Sales By Invoice Extended and Sales By Invoice Extended Detailed can now be removed. Tidied the report.
• Fixed: (case 19361) a bug where the report would ignore the store ID parameter.

Sales By Invoice Extended

• Removed: (case 18360) functionality has been folded into Sales By Invoice.

Sales By Invoice Extended Detailed

• Removed: (case 18360) functionality has been folded into Sales By Invoice.

Sales Order 11in

• Fixed: (case 18857) jobpart quantity rounding.
• Fixed: (case 18941) shipping address fields on Sales Order 11in to hide if there is no ship method.
• Added: (case 17516) settings for alternate address and logo layouts at the top of the document for lining up with envelope windows and preference. This was also done to the Billing report. Billing calls a global setting. SO calls a store setting.
• Fixed:(case 17517) jobpart quantity rounding formulas, made the report react to "print labor detail", and cleaned up the job sections in general. The part and labor subreports are now combined, and I moved things to look cleaner.
• Performance: (case 19738) removed an unnecisary JOIN.
• Replaced customer unit id with customer unit number.

Sales Order Return

• Added: (case 19542) added return reason column.

Teardown

• Added: (case 18638) vehicle stocknumber to the footer of every page.
• Changed: (case 18219) report layout to look cleaner, swapped it to Landscape.

Top Customers Trending

• Added: (case 16724) a new parameter that allows you to specify how "top" is determined, by counts or sums. It was added to all "Top…Trending" reports.

Top Customer Types Trending

• Added: (case 16724) a new parameter that allows you to specify how "top" is determined, by counts or sums. It was added to all "Top…Trending" reports.

Top Part Type Age Trending

• Added: (case 16724) a new parameter that allows you to specify how "top" is determined, by counts or sums. It was added to all "Top…Trending" reports.
• Fixed:(case 18891) Make/Man grouping when 'Make/Man' is selected on on Top Part Type Age Trending.
• Fixed: (case 19708) a rare divide by 0 error that happened when the grand sum (of sales or quantity, depending on what you picked for the based on parameter) = 0.

Top Part Type Sales Trending

• Added: (case 16724) a new parameter that allows you to specify how "top" is determined, by counts or sums. It was added to all "Top…Trending" reports.

Top Salespeople Trending

• Added: (case 16724) a new parameter that allows you to specify how "top" is determined, by counts or sums. It was added to all "Top…Trending" reports.

Transfer Order

• Fixed: (case 18863) barcode format. Previously, if it included commas, which would make the barcode unreadable (transferorderid > 999).

Vehicle Photos 2x3

• Added: (case 17695) Vehicle Photos 2x3 is a new report that prints one photo per vehicle 6 per page, 2 across, 3 down. It also prints year, make, model, and stocknumber. If there is no image, it prints the text "no photo".
• Performance: (case 17695) made photo selection better by using 2 functions instead of a function and a bad view. Updated report type to "Vehicle Search" so it can print from the Search screen Vehicle Search tab Results button.
• Changed: (case 17695) set printer to 'Photos' so people can set a different default printer than the majority of the reports. Since the report is mostly images, they may want higher quality printing.

Vehicle Spec Sheet

• Performance: (case 17695) removed the join to a old view.
• Added: (case 18976) added vehicle notes and description, both suppressible via setting. Tidied the report.

Vehicle Value Analyis

• Added: (case 11433) an age column - resized the fields to make room and tidied.
• Added: (case 8706) closed, non-void jobpart values into the parts sold section.

Work Clock Times

• Changed: (case 18291) renamed Time Clock Work Clock to Work Clock Times and improved the report. It shows Work Clock Time on the left and the division of that time (Time spent on WOs + Time spent on Internal Activities) on the right with percentages + efficiency and lost hours calculations.
• Fixed: (case 18545) default user parameter for showing all users ('All Users'). It was previously entered incorrectly as ''.

Work Order, External

• Fixed: (case 18857) jobpart quantity rounding.

Work Order, Internal

• Fixed: (case 18857) jobpart quantity rounding.

Work Orders

• Added: (case 18690) additional information to the summary section.

Report Viewer

• Added: print queue page now has columns for report type as well as report name.
• Added: column for the new execution time value.
• Added: the print status column is now bolded and color coded.
• Added: notes and error info columns are now multiline edits for easier reading.
• Added: the user can now edit notes on each queue entry.
• Added: support for reprinting items in the queue now updates the execution time as well as parameter values for the existing entry.
• Added: clicking the 'cancel' button (little red x) while a preview job is running now cancels the job completely.
• Added: cancelling a preview either with the little red x or by closing the screen now updates the print queue with a status of Cancelled.
• Added: previewing reports now correctly saves the execution time in the repot queue as well as when it was previewed.
• Added: errors that occur during print preview are now reported with the same error reporting box as all other printing errors. These errors are also saved in the print queue.
• Fixed: any queued report that is sent to the previewer will now correctly save "Preview" as the destination for the report.
• Fixed: an issue where reprinting reports by sending them to preview would cause a new queue entry to be created.
• Changed: the report viewer tab now shows report categories and report names in a tree instead of 2 lists.
• Added: report categories can now contain multiple levels and are no longer attached to the report type (what button it prints from).
• Added: buttons for setting which reports are a user's favorites.
• Changed: deselecting a report now makes various parts of the screen read only.
• Added: the report and parameter lists now save and load their column order and widths.
• Added: when reports are first loaded up (or they are reprinted) various pieces of meta-data are loaded for the report, including average execution time, who ran the report last, a well as how often it is run.
• Added: (case 19808) support for adding reports to the user's favorite reports. All favorite reports show up in a special "* Favorites" area.

Sales Orders

• Changed: default document type has been changed from Quote to Invoice. This won't affect existing users, just new ones.
• Changed: (case 18354) the way 'default' document types work has been reworked. There is still a setting that controls this value, but it is no longer saved when the user closes the screen. Now, the user must choose to set it manually by right-clicking on the document type dropdown.
• Fixed: the 'send items to location map' option in the right click menu will now show the user's current key binding.
• Changed: the email to salesman and email to customer options now print an invoice to PDF and emails it instead of building a text email. This will be much more accurate to the print outs.
• Added: the context menu (right click) now has options for emailing to customer and emailing to salesperson.
• Added: (case 18825) when an invoice is saved, finalized, reopened, or voided, all attached payments and work orders will now have their accounting inserted under the same GL category as the invoice itself instead of separate ones.
• Changed: accounting now happens under the gl transaction types of "Sales Order Updated", "Sales Order Finalized", "Sales Order Reopened", and "Sales Order Voided" to make the transaction log easier to understand.
• Added: (case 18001) the 'customer price' the salesman is presented with is now saved with all lineitems for historical reporting.
• Fixed: saving new lineitems will now be slightly faster, especially on very slow connections.
• Fixed: (case 19013) an issue where loading an item onto a SO without any locations could cause the part to be opened on the parts screen instead if the search sent it over by location. Now the item will be loaded onto the SO with no location.
• Added: (case 17859) support for a new permission to control whether the user can print documents that have outstanding price violations. By default, this is on for all users who could normally edit a SO.
• Changed: the returns dialog on the SO screen now shares resources with the PO return dialog, this should help them have the same features in the future.
• Added: by user request, the SO returns dialog now has many features that were only in the PO return dialog up until now:
• Date range filter
• Remembering what documents were expanded when the user changes pages or filters
• Added: SO return dialog now has a document # filter edit. The user can enter a document # (wildcards supported), or enter something in the "store #-document #" format.
• Added: (case 17070) when the user opens the perform returns dialog, there is now a 'reason for return' dropdown. The user will be shown all previous reasons in an auto-complete, but they can enter new reasons as well. This 'reason' will be applied to all items returned at that time and is remembered for future returns.
• Added: if the user opens the edit item dialog for an item and that item is a return, the return reason will be shown in a special auto-complete dropdown (and can be modified). This is useful for situations where many items need to be returned, but only one or two have a different 'reason'.
• Changed: to eliminate errors caused by the user sending part search results to screens with and without the "group by location" checkbox checked, the two types of messages have been merged into one. This change should be transparent to the user, but it hopefully eliminates cases where screens were handling these 2 cases very differently.
• Added: (case 17070) a new configure->Documents->Return Codes configuration dialog. Users with the appropriate permission can open this dialog to add/edit/remove 'return codes/reasons' which can be chosen between when performing a return on an invoice.
• Changed: (case 17070) the 'return reason' in the perform returns dialog (as well as the edit items dialog) now load entries from the new returncode table. In addition, they now display both the code and name of the return reason. This should give administrators a tighter control over what options can be chosen by users when performing returns.
• Added: return reasons that the user can choose between now show in 'rank' ordering. This allows yards to customize the order that return reasons are displayed in (instead of alphabetical).
• Added: the return dialog now has a Configure button next to the return reasons dropdown. Users with permission to manage this list can click this button to be taken to the configure->return codes dialog.
• Added: configure->return codes now has support for showing which items are in use, and deleting an in-use return code will prompt the user to choose a replacement.
• Fixed: (case 19505) an issue where, if an invoice had payments on it that had a payment method that was not a valid option for the current customer, nothing would show in the payment method column.
• Added: (case 19551) when items are sent to a inventory adjustment document from warehouse management, 'found' items now attempt to find previously written down documents to 'return'. Essentially, if the item in question was ever written down with sufficient quantity, that original write down cost will be used instead. If no appropriate write downs are found, then the item is 'found' with a cost of $0 like before. This helps with yards who would like 'found' inventory to not come back in at $0 average cost.

Search

• Added: (case 8668) if a search returns no results, the popup now has a 'search on HTP' button which will attempt to perform the same search (when possible) on HeavyTruckParts.net.
• Fixed: all options in the right click menu will no correctly show the user's current key binding.
• Fixed: (case 18899) a crash that could occur if the user deselected all vehicles and then clicked on any header to sort the list. This was a long-occuring bug that had been difficult to track down, credit to Ryan@Active for reproduction information.
• Changed: when the user sends search results to other screens, they are now sent in just a single format, instead of 3 or 4. This will make communication between screens easier and more consistent, but breaks compatibility with old versions of other screens.
• Removed: some code that might re-order results being sent from search to other screens. Now items should arrive at other screens in the same order they were viewed on search.
• Moved: the picture viewer dialog that the screen used has been moved to common resources to be shared with other screens.
• Changed: (case 1545) the view pictures dialog is now shared with the parts and vehicles screens. For this reason, some adjustments have been made to the icons and title text to be more useful.
• Added: any images shown in the image viewer dialog are now cached locally, so going quickly between parts will force items to be loaded the first time, but on subsequent visits, the images will already be available. This should make going back forth between search results with images faster, especially on slow connections.
• Added: (Case 19658) Search logging now records execution time, so we set it here.

Transaction List

• Fixed: all options in the right click menu will no correctly show the user's current key binding.

Vehicles

• Changed: the user interface of the main vehicles screen has been significantly reworked. Its layout should now much more correctly match the parts screen.
• Fixed: an issue where the tracking # field at the top of the screen was not emptying when clearing the vehicle.
• Added: (case 1545) this screen now displays a non-modal picture dialog when the user opens the screen. It will allow the user to view part and vehicle images for the currently loaded part at a glance. The dialog is the same one that has been in use on the search screen since version 1. The user may position the dialog on another monitor or in unused space. The dialog is automatically hidden if the user goes to another screen.
• Added: the screen will remember if the user wishes to show the picture dialog, and automatically show/hide it the next time the screen is opened.
• Added: The user can toggle whether the pictures dialog is visible using the new 'toggle' button at the top of the screen.
• Added: user hotkey (can be customized in configure->user hotkeys) for toggling the state of the picture dialog. The default is "Ctrl + P".
• Added: new tool tips for all header controls.
• Added: if the user adds/removes/edits any attachments on the current record, the picture dialog is refreshed.
• Fixed: an issue where image ordering might be overwritten the next time the user opened a part.
• Added: (case 3886) when the user saves a vehicle, whole unit records now correctly save changes to year, make, model, VIN, body style, etc.
• Added: the vehicle's whole unit now correctly copies the user status, similar to the vehicle status, which was already working.
• Fixed: (case 19419) the local sales/usage column in the vehicle bid/teardown area was always 0.
• Added: (case 17595) as part of saving new teardown component items, the user is warned if the tag #'s they enter match any existing items in inventory.
• Added: (case 6656) whole units now are always created as 'single quantity items'. This can be manually overridden on the parts screen, but this should be correct for all cases.
• Added: parts created on a teardown now are created as single quantity items if the quantity of the item on the teardown is 1 or less. THis should cover the default case, where most vehicle parts only exist in one place at all stores. For any parts where this is not true, they will have to be edited on the parts screen.
• Fixed: a possible infinite loop that could occur when the user attempted to add another bid when the current bid's name ended in "(1)", as it was being interpreted as -1 instead of 1.
• Added: (case 18391) columns to the bid document list:
• Created By (set automatically when bid is created)
• Closed by (set automatically during accept/reject)
• Closed date (set automatically during accept/reject)
• Assigned to (set with a new dropdown of user names)
• Fixed: an issue where vehicle bids were no longer saving a 'last modified' time.
• Fixed: sorting by the 'date' column should now work correctly, no matter the user's locale date format.
• Added: (case 18987) a store-specific "Minimum gross margin" value on the bid screen.
• Added: a maximum bid amount based on the minimum gross margin.
• Changed: moved various controls around in order to ensure that all controls are visible at minimum resolution.
• Fixed: (case 19950) part type column in the bids/teardown list is now sortable by part type name.
• Added: made sure that part types in the bid/teardown list order by part type # if they all have the same cost impact (items with high cost impact will still be at the top).

Warehouse Management

• Fixed: all options in the right click menu will no correctly show the user's current key binding.
• Changed: (case 19551) 'found' items now show an approximate cost impact in grey (similar to how vehicle items were shown in grey before). This is to represent the fact that 'found' items now sometimes come back in at the cost that they were last written down at (when possible). Since this is based on the availability of previously written down inventory, it is only an approximation, but is probably more accurate than always showing $0 like before.

Work Orders

• Fixed: all options in the right click menu will no correctly show the user's current key binding.
• Added: (case 18825) when an internal WO is saved, finalized, or voided the gl transaction now uses one of the new types "Work Order In Progress", "Work Order Finalized", and "Work Order Voided". External WOs will use the same "Work Order In Progress" and "Work Order Voided" type, but they are finalized as part of "Sales Order Finalized".
• Changed: to eliminate errors caused by the user sending part search results to screens with and without the "group by location" checkbox checked, the two types of messages have been merged into one. This change should be transparent to the user, but it hopefully eliminates cases where screens were handling these 2 cases very differently.
• Fixed: If the user sent search results from search to the current WO (without clicking the add item button first), if there were items loaded on the job, they would be replaced by the results.
• Fixed: several situations where sending multiple search results to the job on the current WO would load all items onto the same line, causing only the last one to be shown.
• Fixed: (case 19180) an issue where items deleted off of a job could still cause a "Warning: it appears that the item '' is already on the WO, would you like to continue adding it again?" popup to appear.
• Fixed: (case 2401) if the user unchecks the 'override cost' button, the cost value will now go back to the correct calculated average cost instead of $0.
• Fixed: a reversion in one of the recent versions where the context menus in the parts list stopped working.
• Fixed: an issue where clearing a WO wouldn't refresh the job list footer totals.
• Added: when doing an internal WO, the WO master part list now has an attention column similar to many other document lists.
• Added: master part attention icons for empty item and 'insufficient serials selected'.
• Added: (case 6656) master parts now have an attention icon for when a build order would exceed the maximum quantity of a single quantity item.
• Added: pop-up on save regarding single quantity items having their quantity driven above 1.
• Performance: WO save/refresh process now runs a single query to refresh GL info instead of one query per master part. This should make saving WOs with many master parts much faster.
• Performance: various things are only calculated when the user changes values in the work order master part list, instead of just when they tab around.
• Fixed: (Case 19722) potential crash when saving a WO where one or more core charges were ordered to be 'before' the item they are attached to.
• Fixed: (case 19971) an issue where loading a WO template would not correctly load up non-stocked items that were saved on that template.
• Fixed: non-stocked items added to jobs from a template now correctly get a storeid, keeping them from showing the "Empty" icon.
• Fixed: several issues where inherent or dirty cores added from a template would not have the correct lookup column.

Release 11.5

Home (17051)

• Fixed: (case 19233) an issue where the "All" work order types option was not at the top of the WO type dropdown. And if it was not, it would not search all types.

Sales Orders (17053)

• Fixed: (case 19142) an issue where performing lookups in the list control would sometimes only work every other time.

Work Orders (17053)

• Fixed: (case 19180) an issue where items deleted off of a job could still cause a "Warning: it appears that the item '' is already on the WO, would you like to continue adding it again?" popup to appear.
• Fixed: If the user sent search results from search to the current WO (without clicking the add item button first), if there were items loaded on the job, they would be replaced by the results
• Fixed: (case 19181) several situations where sending multiple search results to the job on the current WO would load all items onto the same line, causing only the last one to be shown.

Release 11.4

Database

• Fixed: (case 19032) a bug where indexes in certain functions were not being used appropriately

Reports

Sales By Invoice

• Fixed: (case 19361) a bug where the report would ignore the store ID parameter

Vehicle

Fixed: a crash that occurred when opening a vehicle with an attached bid

Release 11.3

Customer

• Fixed: a crash that occurred when printing from the customer screen

Release 11.2

eBay Extension

• Fixed: a problem where eBay would crash on export

Release 11.1

Customer

• Fixed: (case 18861) an issue where the user could type in an invalid tax item name and the value would not be cleared before saving, leading users to believe a valid value would be saved.
• Fixed: (case 18861) an issue where no tax item selected was being saved with an invalid value (now it is correctly set to NULL).

Customer List

• Fixed: an issue where searching by customer website would throw a database error.
• Fixed: (case 18945) a database error that would occur if the user was searching for customers at a specific store ("Customers For All Stores" is unchecked) and they were searching by an address field (due to the recent additions allowing the system to simultaneously search alternate addresses).

Database

• Fixed: (case 18852) PO adjustments that were created before version 11 wouldn't show up on their posting correctly anymore because of the innodb changes.

Sales Orders

• Added: (case 18001) the 'customer price' the salesman is presented with is now saved with all lineitems for historical reporting.
• Fixed: saving new lineitems will now be slightly faster, especially on very slow connections.

Search

• Fixed: (case 18899) a crash that could occur if the user deselected all vehicles and then clicked on any header to sort the list. This was a long-occuring bug that had been difficult to track down, credit to Ryan@Active for reproduction information.

Release 11.0

Approvals

• Fixed: (case 17951) an issue where hitting the delete button would always ask the user to delete all price restrictions.
• Fixed: (case 17952) an issue where part types on price restrictions were saving but not displaying correctly.

Customer

• Changed: (case 17610) the 'next/previous page' buttons on the invoice list are now under the main invoice tree. This should make it easier for users to find.
• Added: the drag bar on the invoices page no longer lets the user drag so far that it goes over other parts of the screen. Other minor UI tweaks.
• Fixed: an issue where the invoice item detail list was still showing if the user had the 'show line items' checkbox unchecked when they closed and reopened the screen.
• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clilpboard.
• Changed: customer # and balance are now right aligned.
• Added: (case 12527) payment dialog now resizes and remembers previous location.
• Changed: invoice dropdown no longer automatically pops up, making things work a little smoother.
• Changed: save and new as well as previous and next result buttons have been re-activated.
• Fixed: (case 18378) a crash that could occur if a customer was loaded that had an invalid price class markup. This would only happen if it wasn't the 'last' price class markup on the customer.

Customer List

• Added: (case 16332) searching by company name/contact/street/mailing/city/state/zip/country now searches alternate addresses as well.
• Added: (case 16332) smart search now searches alternate addresses.
• Fixed: next and previous customer functionality works again (buttons to scroll through search results on customer screen).

Common Resources

• Changed: (case 17685) if the user hits print tags from the parts screen, the choose locations/serials to print dialog will be shown if there are no locations on the part or quantity is 0. Serialized parts with serial #'s will still not show this dialog, but now an error message is shown that says why tags could not be printed.
• Added: (case 17685) if the user prints tags for one or more non-serialized parts with no locations, a blank location is now shown so that the user can pre-print tags for parts that don't have locations yet.
• Added: (case 17685) a blank tag is no longer printed if all visible locations have a print quantity of 0. Now, the user is shown an error telling them to enter some quantities.
• Added: hitting enter in the thread dialog will no longer hit cancel. This is because sometimes people would do a search and another hit of enter would cause the search to be cancelled.

Core Management

• Fixed: an issue where the store chosen in the store dropdown would not actually filter the results unless the user chose a store then switched back.

Database

• Fixed: the query that converted customerfile to InnoDB was throwing an error due to some misplaces parenthesis and commas
• Added: a column to inventorytype to control permission to make public on HTP
• Fixed: an issue where fcalculateaverage_cost was incorrectly using average item cost instead of average core cost when calculating cost for inherent core charges on vehicle items.
• Changed: (case 17057) when an invoice that contains a vehicle item is either reopened or returned, the cost of the sale will now correctly be put onto the item for the next time it is sold. Previously, this only worked if a yard didn't allow inventory cost to override percent of price costing. Now, in such a case, the returned cost will be put into the cost field on the part. This will keep a secondary sale from recalculating a new percent of price cost and adding it to the previous cost. That issue was causing the cost to increase on returned parts in some scenarios. These changes will not have an effect on yards that do not allow the inventory cost field to override % of price costing.
• Added: inventorysetting now has a unique key on the fieldname column to prevent possible duplicates.
• Fixed: an issue where documentlinelocation.location was longer than the location field in other tables.
• Fixed: (case 17477) an issue where the salesperson value saved on the invoice could sometimes be saved as an invalid number when it was supposed to be NULL (None selected). This issue was not really visible to the user.
• Added: (case 17655) several user-suggested indices to speed up loading items onto the customer cores and returned cores tab of the core management screen.
• Changed: (case 17806) fmoveinventorywithallocations now accepts negative quantities. In such circumstances items are moved from the destination to the source and any document allocations will be 'unpicked' correctly.
• Changed: (case 17806) fmovedocument_allocations now marks serials received on POs and TOs as not picked if the user picks a negative quantity of an item.
• Removed: deprecated view v_salesorderitem. This view was added for some reports, but it is very slow, and we don't use it anymore.
• Changed: (case 17591) all tables that had a multi-field primary key with an auto-increment column have been modified to no longer work that way. This is because that type of key is not supported by InnoDB, and all these tables have been moved to innodb. Some tables had their key replaced, some got a new key, and some that got a new key had other tables updated to point to the correct 'new id'.
• Changed: (case 16468) almost all tables in the database have been moved to the InnoDB storage engine. This should reduce the locking experienced by users under full load and lower the likelihood of data corruption if the server crashes.
• Fixed: issues where the old primary key columns were set to NOT NULL, preventing new items being inserted.
• Added: (Case 1759) workordertypeid to activitytype. This will be used to determine which activity types represent which work orders.
• Added: (Case 1759) a column to tell Enterprise Mobile that certain activities should not be shown to users.
• Added: (Case 1759) a unique index that will insure only one activity type is created per work order type
• Fixed: (case 16886) when the user performs right-click graphing and numeric values being graphed are empty, they are no longer graphed as 0. Now, such values are not present in the graph.
• Added: (case 16928) a new permission that controls whether the user can edit dates on SOs.
• Added: Purchase Order - Stock Category filter and field to the Transaction List.
• Added: (case 15780) in version 10, the dismantled checkbox and the dismantled date were combined in the interface. At the time, we didn't update the 2 fields to match. Now if one field is filled out, the other will get set.
• Changed: (case 18062) default user status in the part and vehicle tables is now blank instead of A. This shouldn't affect any current systems, but could change the default status of new parts on any future imports or uploads.
• Added: (case 18558) The FIFO subsystem has now been added to the standard Enterprise release. This subsystem has been an optional add-on until now.

Deliveries

• Fixed: an issue where all results would be displayed, even if the user told the screen to only load the first 500 items when the size of the results exceeded the warning level.

Ebay Extension

• Fixed: (Case 16237) Sending multiple listings to auction no longer fails due to shipping options.
• Fixed: (Case 16144) Enabled support for sandbox testing.
• Fixed: (Case 16144) Multiselect listing now correctly lists the items selected.
• Fixed: (Case 17525) New listings cancelled through itrack will now show as closed instead of active.
• Fixed: (Case 17525) Cancelling auctions now updates the display immediately so that it is more apparent that the auction has actually been cancelled.
• Fixed: (Case 17631) Weights and measures are now initialized correctly, so that items may be listed with shipping options safely. This is a stopgap fix pending additional UI changes.
• Fixed: (Case 16410) The user should now see much cleaner information when errors occur. There is now also an eBay error type.
• Added: (Case 17725) Items submitted with an SKU in the customlabel field to ebay externally from itrack can now be invoiced out of itrack matching on the tagnum field.
• Added: (Case 17792) The auctions page now has a transactions column for sorting to find invoiceable listings.
• Fixed: (Case 17791) Items which have already been invoiced out can no longer be invoiced out a second time.
• Fixed: (Case 17849) Global and Part Specific defaults should now all correctly apply once more.
• Fixed: Query fixes for recent schema changes have also been added.
• Fixed: Defaults now load even if the config page has not been visited.
• Fixed: (Case 17849) Two new pullfields added to handle part model and manufacturer. The old pullfields now correctly pull assembly model and manufacturer.
• Fixed: I have also centralized the ebaycategorymap table as it is in pro.
• Fixed: Corrected an issue with listing items on ebay
• Fixed: Issues with weights and measures have been corrected.

Home

• Fixed: (case 17783) home screen footers were not resizing correctly when a pagination control was at the bottom of the page.

Interchange

• Changed: the way cross references work has been updated to match the newer database version (moved to InnoDB).

ITrack Online

• Added: better error checking to the code that opens a URL. Now, if the URL is too long, an error message will be displayed to that effect.

ITSQL Framework

• Added: Error reports now have a "Force advanced information" option. If this is set to true, when the error message is displayed, the 'advanced info' checkbox is automatically checked (and hidden). This is useful when code wishes to use the error reporting box as a normal error popup but we can't gaurantee that everyone views advanced info.
• Fixed: an issue where very long words (like a URL) were not properly resizing the height of the message body in the error message popup.

ITMySQL Connection

• Updated: local connection library version updated to version 6.1.5

Master

• Added: (case 13008) when the application cannot reach the local database during an update attempt, the original MySQL error is now sent out as part of the error report, instead of the current, generic Database error 0 that we currently get.
• Changed: (case 17194) we disabled some of the COM timeouts in the application, as this seems to make exporting reports from the crystal reports previewer not show erroneous 'server busy' messages.

Part Configuration

• Fixed: (case 17465) manufacturer/model page: an issue where choosing a part type was loading an empty manufacturer dropdown.
• Fixed: a potential situation where all manufacturers would be loaded into the manufacturer dropdown if no part type was chosen.
• Fixed: an issue where adding a new manufacturer with a duplicate name wouldn't show the user-friendly error message.
• Fixed: (case 17465) an issue where the user was unable to add a new model to a manufacturer that had no models for the current part type.
• Added: the manufacturer dropdown now shows the number of models under that manufacturer/part type combination.
• Added: auto-complete support to the part type and manufacturer dropdowns on the inventory models tab.
• Fixed: an issue where the user could not change the case of a make on the vehicle makes/models page (they would receive a 'duplicate make detected' popup).
• Changed: (case 17591) cross references entry tab has been updated to properly handle changes for the new database version (moved to InnoDB).
• Fixed: minor layout issues on the cross references tab.
• Fixed: (case 18443) a crash that could occur if the user renamed a manufacturer that had at least one model for the current part type.

Parts

• Added: (case 17627) the "Enforce Location Hierarchy" setting now correctly uses the inventory store instead of the store the user is logged into.
• Fixed: an issue where updating a location name and saving would not save the updated location name.
• Fixed: (case 15515) an issue where deleting a location on a part no longer correctly removed corresponding allocations on open documents. Now, only documents that are reducing quantity will have their allocations removed (meaning POs, SO returns, and TO destinations will still remember what location they are planning on adding quantity to).
• Added: (case 15515) if a location on a part is changed/moved, any open allocations on documents are updated to point to the new location (both allocations that reduce and increase quantity).
• Fixed: (case 17690) an issue where checking the 'link manufacturer and model' would set the correct model, but if the model was not on the first page of models, the selection would not be saved.
• Fixed: (case 17696) an issue where the parts screen detected a change collision on imported parts if their last modified date was '0000-00-00'.
• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clilpboard.
• Fixed: an issue where changing collection type and saving was not actually updating the collection type.
• Changed: (case 17544) when the user loads pricing from the vendor catalog or from the vendor's price class multipliers, if the user has already filled out pricing on the part, those values will not be overwritten by any $0 values.
• Added: if the user loads pricing information based on price class markups, distributor price levels will now correctly get set like the others.
• Fixed: (case 18353) when the user clones a part with attachments, saving the attachments no longer throws an error.

Purchase Orders

• Fixed: (case 17401) an issue where transfering core items could transfer items at average core cost instead of average item cost.
• Added: (case 17627) the "Enforce Location Hierarchy" setting now correctly uses the inventory store instead of the store the user is logged into.
• Fixed: an issue where a received serial on a return PO couldn't be removed.
• Added: if a received serial cannot be removed, an error message will be shown to say why.
• Fixed: if serials on a return PO get removed, they now correctly get set to Status Available instead of Status In Transit.
• Changed: (case 17591) postings now have an id (which count up globally) and a posting number, which count up per PO #. All the posting lookups and displays have been changed to show the posting # (1, 2, 3) so as to most closely match how things worked before this Update.
• Added: for backwards compatibility, postings can be looked up by id or by posting number.
• Fixed: the current posting is now selected when the user opens the choose posting dialog.
• Added: minor performance improvement to deleting adjustments.
• Changed: (case 17777) there was a warning that the user was going to receive a quantity greater than 1 into a whole unit, but was only triggered if accounting was turned on. There is a new blocking error if the user is going to increase vehicle quantity above 1. There is also a new attention icon in the PO list for these situations.

Reports

Aging

• Added: An updated, more efficient version with more filter options.

Billing

• Fixed: the OIA mode of the Billing report + additional improvements. Adds a third mode which is a hybrid of the two existing. "Both"
• Fixed: a bug in the OIA and Both modes of the report that would sometimes show extra open items. (When payment storeid did not match paymentline storeid - which can happen)
• Added: a setting to hide terms (bottom left of Billing report). By default, they will show.

Inventory Adjustment Log

• Fixed: joining for global inventory adjustments (that can affect inventory at multiple stores), and updated grouping to reflect inventory store, not adjustment store.
• Added: count summaries.

Labor Summary By Employee

• Change: column headers

Purchase Order Posting Report

• Updating PO reports that reference purchaseorderhistoryid to use posting number instead (for version 11).

Received Items

• Updating PO reports that reference purchaseorderhistoryid to use posting number instead (for version 11).

Received Items By Source

• Updating PO reports that reference purchaseorderhistoryid to use posting number instead (for version 11).

Sales By Invoice

• Combined the SalesByInvoice report with the extended versions. New "mode" parameter lets you select detail level.

Sales Order 11in

• Added: Customer Tax Exemption ID, if present. This can be suppressed with a store level setting.
• Changed: the default for creating a new "hide company name" setting to show by default. Will not change the default for people who already have the setting.

Tag

• Added: the TagLogo functionality to the standard Tag report.

Teardown

• Added: Pageheader updates and some minor improvements from previous cases, query comment headers, etc…
• Added: vehicle Stock # to the footer of every page on Teardown.rpt.

Top Part Type Age Trending

• Added: more grouping options, made the black "all" group in the bottom 2 graphs more universal.
• Improved report description.

Unmoved Inventory

• Added: a part type parameter.

Vehicle Value Analysis

• Added: summary totals.
• Added: an age column.

Work Order Internal

• Added: store-level settings to suppress master part and customer unit options and values, both default to show.

Work Orders

• Added: a summary section and color-coded 'date promised'. Sections can be optionally shown or hidden using the new parameter.

Sales Orders

• Fixed: (case 17575) an issue where returning a core from the core management screen might throw a database error.
• Fixed: (case 17589) a possible query issue that could appear when distributing a vehicle's remaining cost across remaining inventory.
• Added: a setting to fadjustinventory that allows a yard to disable the code that statically allocates CoGS onto returned vehicle parts. This is useful at yards that want to use pure percent of price costing all the time. It is suggested that yards not change this setting as it keeps vehicles that have been written down from having their cost become unbalanced.
• Added: (case 17627) the "Enforce Location Hierarchy" setting now correctly uses the inventory store instead of the store the user is logged into.
• Added: (case 17800) now, if the user attempts to save an adjustment without an adjustment type, an error will appear. This prevents issues where the user would enter an amount on an empty adjustment line, which would show in the subtotal, but not be saved.
• Added: (case 17766) loading a template onto a SO now loads all component items with the quantities filled out on the collection.
• Changed: a small performance improvement made to looking up payment information made possible by recent database changes (globally unique primary key).
• Added: smart search now searches customers by alternate address info as well.
• Fixed: (case 17593) the sales orders screen will no longer show the 'item is part of a collection doubleclick to break down assembly' attention icon if the parent assembly has a quantity of 0.
• Added: (case 17778) the part info tab on the left side of the SO screen now shows 'core status' of the selected line. For inherent cores, it shows the status of whether the core has been credited back or not (or discarded). For dirty core returns, it shows whether the core was discarded, inventoried (as well as to what SKU), or if its still in process.

Search

• Fixed: (case 17646) a crash that would occur if the user doubleclicked the camera icon to view images on some parts.
• Fixed: an issue where the picture preview dialog that would appear after clicking camera icons would always show part SKU instead of tag # where appropriate.
• Fixed: an issue where cancelling a very quick search (often done accidentally by hitting enter a second time) would cause an error to be thrown when the search was being logged. This is due to a MySQL error that has been reported (https://bugs.mysql.com/bug.php?id=79838). However, a second error was happening due to the outcome of the first query, and that has been fixed.
• Added: 'wait' cursor while appraisals are being generated. Other minor UI changes to appraisal configuration.

Vehicles

• Changed: after reviewing vehicles with cost discrepancies, it was noticed that parts with a status of S or C still allocate vehicle costs, but don't show on the available inventory area of the performance tab. Now, everything other that status D shows up, making it easier for users to review manual cost allocations.
• Fixed: (case 17385) an issue where making updates to attachments and saving could lead to database errors or possibly vehicle images not saving.
• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clilpboard.
• Removed: (case 17986) parts on teardowns were inheriting the vehicle's category. Since vehicle category lists don't necessarily match part category lists, this was causing issues where parts were saved with invalid vehicle categories.

Vendor

• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clilpboard.
• Changed: save and new as well as preview and next result buttons have been re-activated.
• Changed: buttons at the top of the screen have been standardized to be more like the customer screen.
• Changed: standardized all the "do you want to save" prompts to match the customer screen as well as other screens.
• Added: gridlines to the vendor catalog page.
• Added: price class and purchase class dropdowns now have auto-complete.
• Added: the price class area has been made easier to understand (labels reworded, etc). Also, since one of 2 sets of multipliers are active at a time, the currently active multipliers are now bolded.
• Added: (case 12538) there are now 2 'recalculate inventory prices' buttons. One that recalculates prices for all inventory associated with that purchase vendor, and another that affects everything associated with the current price class. These allow the user to refresh the inventory prices based on the current price class (useful for when the price class gets modified or a different price class is chosen).

Vendor List

• Fixed: next and previous customer functionality works again (buttons to scroll through search results on vendor screen).

Warehouse Management

• Fixed: (case 17741) an issue where the count sheet would be blank when printed from the warehouse management screen. This was due to a bad part type argument.

Work Clock

• Fixed:(case 18537) a bug where complaint, cause, correction or internal notes with new lines could break the entire page.
• Changed:(case 18481) Changed the job list page so you can clock in or out of jobs without going to the job detail page.
• Changed:(case 18415) Previously, only users flagged as workers could log into work clock. Now, everyone can. Only users flagged as workers can see the job list page. Workers now automatically go to the job list page after logging in.
• Added:(case 1759) Clocking out of a job now also clocks you out of the associated activity.
• Added:(case 1759) support for clocking out of activities and having it automatically clock out of sub jobs
• Changed: The job name and description are now headers directly below the main title. Previously they were below the complaint, cause and correction fields which are quite large.
• Added: (case 18116) Work Clock should now redirect the user back to the main store selection page if the php session expires.

Work Orders

• Added: (case 17627) the "Enforce Location Hierarchy" setting now correctly uses the inventory store instead of the store the user is logged into.
• Fixed: a possible bug that could be caused by building a job from a template that had parts on it. Each job part's behind the scenes ID was being assigned from the template, which could cause collisions once a template was used more than once.
• Fixed: an issue where doing a serialized assembly breakdown where the assembly was not destroyed would cause the serial # to be marked as 'Consumed' even though it was not consumed.
• Fixed: an issue where the locations of an item would not be handled correctly if the user did an assembly breakdown where the assembly was not consumed.
• Fixed: an issue where serialized assembly breakdowns that did not consume the assembly were not correctly adding the assembly to the job, causing no cost to be distributed and the locations to get messed up.
• Added: a temporary popup to warn the user when they do an assembly breakdown and the part is not consumed that the location of the part may change to the default Work order production location.
• Added: non-stocked items now show N/A in the availability.
• Added: the taxable checkbox now defaults to checked for empty lines.
• Added: price/quantity now defaults to $0.00/1 for empty lines.
• Fixed: (case 17544) if the user enters a pure misc item (description only), the quantity/price/etc will not be lost when the user enters a description.
• Fixed: (case 18184) deleting an item with an inherent core charge would ask the user to delete more than once.
• Fixed: (case 18184) an issue where replacing an item on a WO would ask the user if they wanted to delete the previous item.
• Fixed: an issue where replacing an item with a new item that had an inherent core charge wouldn't load the core charge correctly if it wasn't the last line on the job.

General/Controls

• Fixed: (case 17707) a crash that would be caused when hitting the up arrow in an advanced combo box when nothing was selected.
• Fixed: an issue where paging combo boxes weren't correctly 'going to a page' during setting initial text.
• Fixed: (case 17672) an issue where deleting all items from a list could leave dead whitespace in the list when new items are loaded back in.
• Fixed: an issue where a variable was not initialized, leading to somewhat random behavior on ITDateTimeCtrl's where their style was set to date and time.
• Fixed: an issue where ITDateTimeSetting::Reset was working inconsistently and could create an COleDateTime that was invalid. This lead to inconsistent behavior in some date/time pickers.

Release 10.5

Appraisals (17051)

• Changed: (case 19419) by user request, the 'current quantity on hand' retrieved as part of sales appraisals will now limit the matched results to just items that match the category of the current item (if it is filled out). Otherwise, all categories are considered.

Home (17052)

• Fixed: (case 19233) an issue where the "All" work order types option was not at the top of the WO type dropdown. And if it was not, it would not search all types.

Sales Orders (17054)

• Fixed: (case 19142) an issue where performing lookups in the list control would sometimes only work every other time.

Vehicles (17051)

• Fixed: (case 19419) the local sales/usage column in the vehicle bid/teardown area was always 0.
• Fixed: (case 19346) a crash happening when the user used the up arrow in the dropdowns on teardown.

Work Orders (17054)

• Added: non-stocked items now show N/A in the availability.
• Added: the taxable checkbox now defaults to checked for empty lines.
• Added: price/quantity now defaults to $0.00/1 for empty lines.
• Fixed: (case 17544) if the user enters a pure misc item (description only), the quantity/price/etc will not be lost when the user enters a description.
• Fixed: (case 18184) deleting an item with an inherent core charge would ask the user to delete more than once.
• Fixed: (case 18184) an issue where replacing an item on a WO would ask the user if they wanted to delete the previous item.
• Fixed: an issue where replacing an item with a new item that had an inherent core charge wouldn't load the core charge correctly if it wasn't the last line on the job.
• Fixed: If the user sent search results from search to the current WO (without clicking the add item button first), if there were items loaded on the job, they would be replaced by the results.
• Fixed: (case 19181) several situations where sending multiple search results to the job on the current WO would load all items onto the same line, causing only the last one to be shown.
• Fixed: (case 19180) an issue where items deleted off of a job could still cause a "Warning: it appears that the item '' is already on the WO, would you like to continue adding it again?" popup to appear.

Release 10.4

Approvals

• Fixed: (case 18952) an issue where the stock category was not correctly being displayed when price rules were being loaded. The value of All would save but display as Standard on the next load.
• Fixed: an issue where changing the document type of a price rule was not being saved.
• Fixed: another issue that was causing part types from being saved on price rules.
• Performance: improved the speed of the auto-complete fields on the screen.

Customer

• Fixed: (case 18861) an issue where the user could type in an invalid tax item name and the value would not be cleared before saving, leading users to believe a valid value would be saved.
• Fixed: (case 18861) an issue where no tax item selected was being saved with an invalid value (now it is correctly set to NULL).

Sales Orders

• Added: (case 18001) the 'customer price' the salesman is presented with is now saved with all lineitems for historical reporting.
• Fixed: saving new lineitems will now be slightly faster, especially on very slow connections.

Search

• Fixed: (case 18899) a crash that could occur if the user deselected all vehicles and then clicked on any header to sort the list. This was a long-occuring bug that had been difficult to track down.

Release 10.3

Common Resources

• Changed: (case 17685) if the user hits print tags from the parts screen, the choose locations/serials to print dialog will be shown if there are no locations on the part or quantity is 0. Serialized parts with serial #'s will still not show this dialog, but now an error message is shown that says why tags could not be printed.
• Added: (case 17685) if the user prints tags for one or more non-serialized parts with no locations, a blank location is now shown so that the user can pre-print tags for parts that don't have locations yet.
• Added: (case 17685) a blank tag is no longer printed if all visible locations have a print quantity of 0. Now, the user is shown an error telling them to enter some quantities.

Work Orders

• Fixed: (case 18141) an issue where doing a serialized assembly breakdown where the assembly was not destroyed would cause the serial # to be marked as 'Consumed' even though it was not consumed.
• Fixed: (case 18149) an issue where the locations of an item would not be handled correctly if the user did an assembly breakdown where the assembly was not consumed.
• Fixed: (case 18141) an issue where serialized assembly breakdowns that did not consume the assembly were not correctly adding the assembly to the job, causing no cost to be distributed and the locations to get messed up.
• Added: a temporary popup to warn the user when they do an assembly breakdown and the part is not consumed that the location of the part may change to the default Work order production location.

Release 10.2

Approvals

• Fixed: (case 17951) an issue where hitting the delete button would always ask the user to delete all price restrictions.
• Fixed: (case 17952) an issue where part types on price restrictions were saving but not displaying correctly.

eBay

• Fixed: eBay Shipping options have been corrected so that listings with shipping options work correctly.

Manage Warehouse

• Fixed: (case 17741) an issue where the count sheet would be blank when printed from the warehouse management screen. This was due to a bad part type argument.

Parts

• Changed: (case 17091) choosing an interchange record will now only set a side on the part if the existing part location is blank or "N/A"
• Fixed: a rare crash that would occur if the user hit the up arrow in the manufacturer/model dropdown if nothing was selected.

Release 10.1

Customer

• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clipboard.

Parts

• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clipboard.

Reports

Billing

• Fixed: Billing Statements sending datetimes instead of dates from the customer screen. The billing statements should no longer care about time of day.

Payment Receipt

• Added: conditional suppression, tidied the report, and added a new optional payment memo via a store level setting.

Sales By State

• Added: handling for non-US countries/states to Sales by State report.
• Fixed: grouping.

Weekly Sales Insights

• Fixed: customer and parts subreports - they were not filtering by store even when a store was specified.

Work Orders

• Fixed: a bad join in the workorders report.

Vehicles

• Fixed: (case 17385) an issue where making updates to attachments and saving could lead to database errors or possibly vehicle images not saving.
• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clipboard.

Vendor

• Fixed: (case 17816) if the user doesn't have permission to edit attachments, they'll now correctly still be able to copy the image to the clipboard.

Release 10.0

Highlights

• Vehicle bids/teardowns improved, and many bugs and crashes eliminated.
• SO screen load, save, and refresh significantly sped up. Opening and saving a large SO (hundreds of items) can now take as much as 70% less time.
• Entirely new price control system on sales orders. See the new tabs on the Approvals screen to define new rules to control how salesmen can price items.
• Interchange screen completely rewritten. Significantly faster and easier to use. Interchange records can now be added and edited on this screen easily and quickly. Also, you can now view notes, attachments, and inventory summary information. The user can easily 'drill down' to see what applications are present on an interchange # as well as seeing all models a particular # applies to.
• The interchange pop-up on parts and search has been replaced. The new one allows the user to see interchange applications, notes, and attachments. All this information should make identifying interchange application much easier.
• Database performance improvements in several slow areas.
• Support for ZIP+4 on all address interfaces.
• More attachment types supported.
• Ebay screen significantly faster to update and is even more user friendly. More improvements coming soon.
• Several behind-the-scenes changes to the report viewer to make crashes much less common when previewing reports as well as adding several features to make reports easier to run.
• Support for scheduled reports is now here. Print, email, or save reports on any schedule you want. Contact ISoft for more information on enabling this feature at your yard.
• Tag printing from all areas has been reworked. The user can now customize how many tags print for each item and the pop-up is significantly easier to use.
• Better windows 10 support.
• Support for finding serials during a count that have been sold or written down.
• Standardization between part type, customer, vendor, and part messages. They can now all be marked as important, support multiline, and other minor changes.
• Hundreds of minor fixes and improvements across the entire application.

Tools

• List controls are now faster to load items. This can have a significant effect on large lists.
• Fixed: an issue where combo boxes were not scrolling correctly in windows 10 with the 'scroll inactive windows' windows setting on (which is on by default).
• Fixed: an issue where clicking on the scrollbar of a combo box could affect how the mouse worked, such that the user could move the application without moving the dropdown window.
• Added: support for mouse scrolling in combo boxes for any mouse wheel with customized sensitivity.

Appraisals

• Fixed: (case 15937) an issue where the sales appraisals and the HTP appraisals might cause a database error if they both attempted to connect to the database at the same time. This may have resulted in crashes if the timing was just right.

Approvals

• Changed: (case 17109) the credit approvals screen has been renamed to Approvals since it will soon allow other types of approvals.
• Changed: (case 17109) the credit approval system has been moved to a tab on the approvals screen.
• Fixed: lots of little issues with the resizable area of the credit approvals area.
• Added: new pages to the approvals screen for adding/editing price restrictions, as well as one for approving documents in which price restrictions were violated.
• Added: permissions that control the visibility of each of the 3 pages on the approvals screen.
• Changed: the refresh button on the credit approvals tab has been moved to match the new price approvals tab.
• Added: the price approvals page now has a list that shows all sales order lines that need to be approved. The user can review information about why the items in question need approval, including information about the part and what salesman created the document.
• Added: the user can now mass-approve price violations. This will automatically allow the salesperson to finalize the document.
• Added: the user can now mass-reject price violations. This will keep the salesperson from finalizing the document, and they will be made aware that the request has been denied.
• Added: support for searching through historical price approval requests that were approved or denied.
• Added: a shared 'price violation/approval information' dialog that will be shared between any documents that have price violations. This dialog shows the current approval status of the item, as well as detailed information on why the approval is required. In addition, the user can choose the reason why the price has deviated (from a fixed list), as well as filling out a more detailed explanation (optional).
• Fixed: the user can no longer approve/reject price violations on closed/voided documents.
• Added: there is now a checkbox that allows the user to control whether they see price approvals/rejections for closed/voided documents. These finalized items are shown with a different background color.
• Added: document type column to pricing approval screen, so the user can tell the difference between quotes and invoices at a glance.
• Added: the price control page can now be used to add/edit/view price rules that apply to documents at the current store. The user can view rules that apply to their store directly as well as global rules.
• Added: on the price control page, the user can now define a comma separated list of allowed price violation 'reasons' that can be chosen from on the document screens.
• Added: the price control page now locks down global rules if the user only has store-level permission for editing rules.
• Added: a Configure Document Exemptions button, which opens the configure sales order document types dialog and is permissioned by the corresponding Configuration permission.
• Added: the price approval screen now filters approvable documents down to the items with the same inventory store that the user is logged into.
• Added: the user can now see the reason and explanation of the price approval request in the approvals list.
• Fixed: minor issue with the order of document lines in the list.
• Added: when the user goes to reject one or more approval requests, they are now presented with a popup that asks for an (optional) reason and explanation, which is visible to the salesman. The popup allows the user to apply one reason to all item(s) being rejected, for fast mass-rejections.

Common Resources

• Changed: the attachment dialog has been modified to facilitate more types of attachments.
• The following changes have been made to the shared print tags dialog:
• Fixed: if the dialog or lists are resized, that will be remembered.
• Added: tag # column to the lists of items to print tags for.
• Added: quantity to print column to the location list (the serial # list still always prints 1 per serial)
• Changed: Sold, Returned, Transferred, and Consumed serial #'s no longer show up to be printed.
• Changed: the "print one per quantity" checkbox has been removed and there are now buttons that will automatically set all item's quantity to print either to 1 or to the current quantity on hand at that location.
• Changed: the location list no longer shows locations for serialized parts, and if there are no entries in the location list, it is hidden. This simplifies the process for printing serialized tags.
• Added: (case 7429) the argument passed to the tag report has changed so that each item can have an individual quantity to print.
• Fixed: a possible crash when launching a tree report dialog.

Core Management

• Added: integration to new tag printing format.

Credit Approval

• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.

Crystal Reports Extension

• Fixed: an issue where date parameters with no default value might cause an error when previewing or printing.

Customer

• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.
• Added: both addresses and alternate addresses should correctly support ZIP+4 format. This means that the +4 section will no longer keep city/state/country from being auto-filled and if they zip is ever auto-filled, the +4 section will not be overwritten.
• Fixed: 0-padded zip codes will no longer be overwritten with non-padded zip codes.
• Fixed: an issue with overactive change detection in an unreleased change.

Database

• Added: (case 15807) an index to the scansession table that should make looking up sessions when logging into the scanner faster.
• Added: (case 15807) an index to the inventoryserial table that should make looking up serials on the salesorders screen a bit faster.
• Removed: vehiclemodel.teardownid, which is no longer used.
• Added: a primary key to the vehicle model table.
• Removed: some databases still had the teardown and teardowninventorytype tables, which are unused.
• Removed: several unnecessary indices on the interchange table.
• Added: a new index on the interchange table that should make loading/sorting search results faster on the interchange screen.
• Changed: recurring invoices must now be open and can be cloned on the day they expire
• Fixed: (case 16107) a problem where generated recurring invoices were not being updated with the correct date.
• Fixed: (case 15819) an issue where transferring vehicles between stores was not updating the store or location on the vehicle record.
• Fixed: (case 15908) an issue where, if max % of price was filled out, an item's cost could drop below inventory.averagecost (only matters if statically allocated average costs is turned on).
• Removed: an old setting that is no longer used.
• Performance: (case 16372) the sales appraisal process is now much faster and has been rewritten to no longer use a temporary table.
• Added: sales appraisals now weight the fitness of a result based on how old it is, in addition to the other fitness metrics.
• Changed: sales appraisals now weight the fitness of sales with mismatched model/category with a value that is retrieved from settings, allowing more customization of sales appraisals.
• Added: sales appraisals now use a setting to control how many days into the past we will consider old sales. The default is 2 years.
• Performance: added an index to the model table which makes active model lookups by name faster in situations where a manufacturer is not specified (common on the interchange screen).
• Changed: as part of the interchange rewrite, all interchange notes have been combined into single, multiline entries.
• Fixed: a possible issue where inserting the first inventory record in the system could cause an error.
• Added: a "Vehicle Part" field to the transactionlist, which displays whether or not the part is attached to a vehicle record.
• Changed: the interchange table is now innodb so that we can roll back an entire transaction if there is any failure.
• Added: new interchange attachment table (interchangefile). This table is incompatible with the old interchange attachment system (interchangeattachment). If the user has any valuable data in there, they should contact ISoft for manual conversion.
• Changed: all 4 of the existing attachment tables (interchangefile, vehiclefile, customerfile, vendorfile) now have a single auto_increment primary key and have been switched to InnoDB.
• Added: 2 new permissions for the interchange screen. One allows opening the screen, the other controls adding/editing/deleting interchange records, notes, and attachments.
• Added: various filters and display fields to the Transaction List
• Fixed: add a query to make sure no one has inventory items where vehicle ID is 0
• Added: a column to the adjustmenttype table to determine if certain adjustment types should be included in "Gross Sales" on reports
• Added: zipcode.displaycode, which is a string, so it allows padding short zip codes with 0's, where appropriate.
• Removed: an unused function related to SAV transport.
• Fixed: (case 16739) a foreign key constraint on the report queue parameter table wasn't created correctly.
• Fixed: (case 16804) a rare issue where an inventory record could be replaced (instead of duplicated) when freplicateinventory was called. Now, any unexpected contingencies like this will instead return either 'Duplicate' or 'Error' instead of replacing the inventory record.
• Fixed: (case 16689) an issue where the vendor catalog inventory prices import would not work on any database using InnoDB version of inventory.
• Removed: (case 16956) a setting with a blank location
• Fixed: a bunch of misspelled setting names.
• Changed: (case 17055) serials at location variance should now correctly come out of the adjustment log when they get written down.
• Removed: serials of status Work In Progress no longer count as on hand.
• Added: (case 17081) all previous count operations now have their 'location' set correctly retroactively.
• Fixed: (case 16138) if a serial that is not on hand is moved, inventorylocations will no longer be updated.
• Added: some new permissions for the Approvals screen.
• Added: (case 17109) new tables for tracking price restrictions.
• Added: (case 17110) new tables and fields for SOs to track price approval status.
• Added: (case 11565) there are now tables for scheduling reports to be run and either saved into a directory, emailed to a recipient, or printed out of a network printer.
• Changed: the price level field on the pricerestriction table no longer has core price levels. Instead, there is a 'core' column which dictates whether the price level applies to a core charge or not.
• Added: unique index to price approvals so that there can only be one approval/denial per document line and price combination.
• Added: since the salesorderline table now has more transactionalized price levels than it did before, these values have been retroactively set for all historical document lines. This may not be 100% accurate, but it should be better than having 0 for all those prices.
• Added: function fcalculateprice_acceptability. This function takes necessary information about a salesorder/workorder line and returns whether it is in violation or not. In addition, it will return information regarding whether there are any approvals or rejections that match.
• Added: function fcalculatepriceacceptabilityreason. This function returns human readable reasoning for why a particular price is in violation of the price control rules. It can optionally include 'warnings' in addition to violations.
• Added: function fadjustprice_approval. This function is called when the the price approvals system is going to update a line to be approved or denied.
• Fixed: (case 17477) an issue where the salesperson value saved on the invoice could sometimes be saved as an invalid number when it was supposed to be NULL (None selected). This issue was not really visible to the user.
• Added: (case 17655) several user-suggested indices to speed up loading items onto the customer cores and returned cores tab of the core management screen.
• Fixed: an issue where documentlinelocation.location was longer than the location field in other tables.
• Added: inventorysetting now has a unique key on the fieldname column to prevent possible duplicates.
• Added: a setting to fadjustinventory that allows a yard to disable the code that statically allocates CoGS onto returned vehicle parts. This is useful at yards that want to use pure percent of price costing all the time. It is suggested that yards not change this setting as it keeps vehicles that have been written down from having their cost become unbalanced.
• Fixed: an issue where fcalculateaverage_cost was incorrectly using average item cost instead of average core cost when calculating cost for inherent core charges on vehicle items.
• Changed: (case 17057) when an invoice that contains a vehicle item is either reopened or returned, the cost of the sale will now correctly be put onto the item for the next time it is sold. Previously, this only worked if a yard didn't allow inventory cost to override percent of price costing. Now, in such a case, the returned cost will be put into the cost field on the part. This will keep a secondary sale from recalculating a new percent of price cost and adding it to the previous cost. That issue was causing the cost to increase on returned parts in some scenarios. These changes will not have an effect on yards that do not allow the inventory cost field to override % of price costing.

Ebay Extension

• Fixed: (Case 15770) ITrack no longer attempts to insert duplicate ebaytemplate lines.
• Fixed: Default Template edit window now has fewer options, since they were moved to global config tab
• Added: (Case 14747) Shipping Service Options now work in global config!
• Fixed: (Case 15902)Company name is now listed if the customer name is blank
• Added: (Case 15639) Combo boxes now automcomplete and are searchable in the listing edit dialog, as well as global defaults
• Fixed: Default Listing Duration now correctly populates with default value if no user default value yet saved to the database.
• Fixed: (Case 15882) Shipping dimensions now correctly populate in the Edit Dialog when pulled from global config. This was only a display issue.
• Added: (Case 16007) Disabled editing of shipping dimensions in the edit dialog, since we don't want people having to change things every time.
• Added: (Case 16004) Disabled the shipping cost field when free shipping checkboxes are enabled.
• Fixed: (Case 16005) Shipping Service Options were not actually being deleted. They are now.
• Fixed: (Case 16006) Listing Duration has been expanded to be the same size as other dropdowns in the Global Config screen. Good Til' Cancelled was being cut off.
• Added: (Case 16009) Added Listing Duration methods, more to come.
• Fixed: a bug where the chosen date would be omitted from the results rather than included.
• Fixed: (Case 16037) Expanded the edit dialog to show the entirety of all dropdown values by default.
• Fixed: a bug where certain auctions may would not appear when limiting the auction list by date.
• Fixed: (Case 16102) Returns accepted and Listing Duration now pulled correctly from global config. This was only a display issue.
• Fixed: (Case 16116) Spacing improved, duplicate call removed
• Fixed: (16132) Weights and measures now pull to their correct fields.
• Added: (Case 14758) eBay listings can now be cancelled through itrack with a dialog to select cancellation reason.
• Fixed: eBay now updates based on date filters! (ebay requires we check at most 120 days total).
• Fixed: eBay updates are dramatically faster per listing.
• Fixed: (Case 16237) Enabled Motorcycle category mapping
• Fixed: (Case 16237) Enabled CategoryMappingAllowed from ebay to update the old category id to the current category id.

Home

• Added: (case 16871) estimate work orders can now be shown or hidden on the work order list.
• Added: the show closed and show estimate checkboxes now remember their last setting.

Interchange

• Added: the screen now gives more space to certain areas of the UI.
• Moved: the exact and inexact notes now have their own top-level edit fields that the user can view the notes more easily in.
• Added: the part type dropdown is now a typeable combo, allowing the user to quickly lookup part types by name with auto-complete support.
• Added: the manufacturer dropdown now properly loads all manufacturers that match the current part type as well as all vehicle models.
• Added: the model dropdown now has both part and vehicle models in it.
• Added: if the user chooses a model directly, the corresponding make/manufacturer will be selected.
• Fixed: issue where makes/vehicle models weren't displaying correctly. Also fixed an issue where part models wouldn't populate correctly based on just part type (all manufacturers).
• Added: the interchange search now works.
• Added: wildcard support for make/model/interchange #/sub interchange #.
• Added: fixed sorting to the results
• Added: pagination to the interchange search results. The number of items to show per page defaults to 200, but can be set per user.
• Added: distinct rows now load into the interchange group list for every inventory type #/interchange #/sub interchange # combination that matches the application rows.
• Added: selecting an item now highlights the corresponding items in the opposite list.
• Added: some more columns of information to the lists below.
• Added: support for popping up an interchange choice dialog.
• Added: interchange group search support.
• Changed: the interchange group and interchange application lists have been merged. I think this will make the screen more user friendly. Most of the screen has been rearranged based on this.
• Added: the application list now groups all similar entries into a single interchange group on the screen. The group is sorted together and shares a background color. Selecting one item in a group highlights all other items in that group.
• Added: "New group" and "new application" buttons below the interchange list.
• Fixed: several issues where the manufacturer/make and model dropdowns didn't have the right items in them.
• Added: if the user doubleclicks an interchange record when they are in application mode, the screen will 'drill down' and search for all applications that share that interchange number. If the user doubleclicks a record when they are in interchange # mode, the screen will 'drill down' and search for all applications with the same part type/make or manufacturer/model.
• Added: the screen now has a save button, change detection, and proper saving.
• Added: if the user changes anything that affects an entire group of interchange records, that change is automatically applied to all other records in the group whether they are currently visible or not.
• Added: attention icons for unsaved records as well as ones who are missing required fields.
• Added: the add group/add item buttons should now correctly add new items that will get their initial default values from the last search that has been performed.
• Added: the interchange detail page now properly handles shared exact and inexact interchange notes for each interchange group.
• Added: interchange notes now properly have change detection and save and load correctly.
• Added: all part type dropdowns now show the part type # at the end of their name. The user can use the auto-complete feature to lookup part types by number this way without disrupting the sorting of the items.
• Removed: the dedicated inventory type # field, since it is now part of the name field.
• Added: adding new interchange groups now works as expected.
• Added: changing pages of applications now properly sorts 'new' groups in.
• Added: if anything changes about an interchange group, the notes pane will now be refreshed to show correct notes.
• Added: if an interchange group is modified to overlap with an existing group that has notes, applications, or attachments, the user will be prompted to merge them or cancel. Merging these groups will make them one large group and the notes will be appended.
• Added: the user can now delete interchange records. When the last application is deleted from a group, group notes are also deleted, unless that group is 'inexact' (no sub interchange #). In the future, we will probably ask the user if they want to delete notes in this case.
• Added: putting a 2 digit year into either of the year fields will now expand out to a 4 digit year, based on windows locale settings.
• Added: attachments can now be saved and loaded for entire interchange groups.
• Fixed: an issue where the screen state wasn't set correctly when the screen was first loaded.
• Added: interchange groups now support 'inexact' attachments. If the "Exact" checkbox for an attachment is unchecked, that attachment will be associated with all inexact interchange groups as well.
• Added: merging interchange groups now merges attachments.
• Added: the application list now shows a side and allows editing of it.
• Added: support for permissions. The 'Can open screen' permission controls whether the user can open the screen and the 'Can Edit' permission controls whether the user can add/edit/delete interchange information.
• Added: support for being shown on the parts/search screens.
• Added: support for year range searches, which can be done from the part search screen.
• Added: the apply button is no longer usable when the user doesn't have permission to edit interchange.
• Added: (case 16604) the interchange detail page/pop-up now has a sales/inventory totals area. This area shows QoH, QA, quantity sold (last year and last 5 years), total revenue (last year and last 5 years) for each store. If the user expands a store, the information is further grouped by category at that store.
• Fixed: an issue where unsaved attachment changes would persist between searches.
• Added: if the user performs a new search with unsaved changes, they are now prompted to save those changes before continuing.

Inventory Overview

• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.

IT SQL Framework

• Fixed: A bug where closing an active transaction on an ITMySQLConnection when host.ini's connection logging was turned off (logfile='') would result in a crash.
• Fixed: an issue where an error would occur during connection (though it would not be shown to the user). This was causing a small delay on every launch of ITrack. Also, connecting via named pipe should work correctly now.
• Changed: query logging code is a bit cleaner. Also, when queries are logged, the user can now tell which queries were sent together as a single query group.
• Fixed: an issue where queries ending in a semicolon and linebreak could cause 'empty' queries to be added to the queries the pipe sent.

IT MySQL Connection

• Fixed: A bug where SSL could be set as required and the connection would not fail when the encryption step failed. Now setting SSL active will generate an error when it fails to gain a cypher.
• Fixed: an issue where errors that happened during StoreMultiple were not being reported in any way (so long as the syntax of the entire query string was correct). Now, if any part of the query set fails, the entire thing fails and it stops grabbing results. This may cause false-positives in some situations where 1/10 queries is allowed to fail, but since each ITSQLResult cannot report the error of an individual query, I think this is the best we can do for now.

Master

• Fixed: an issue where pages weren't resizing properly in the options dialog.
• Fixed: an issue where the initial size of the options dialog wasn't being restored correctly, causing pages to be resized strangely.
• Added: any options page can now send a message to the options dialog to initiate a close operation as though the user had hit OK.
• Changed: (case 17194) we disabled some of the COM timeouts in the application, as this seems to make exporting reports from the crystal reports previewer not show erroneous 'server busy' messages.

Parts

• Fixed: an issue where the vehicle make and model might not display correctly when a the user loaded a stock # onto a new part.
• Changed: all the dropdowns now become readonly instead of invalid when the user doesn't have permission or other situations where the fields cannot be edited. Readonly dropdowns are easier to read and interact with.
• Removed: parts were only partially inheriting the status of the vehicle whose stock # was loaded onto the part. Because it wasn't working right, it has been disabled for now until we figure out if its something that should be added back in.
• Performance: loading vehicles should now be slightly faster and run fewer queries.
• Performance: (case 15807) if the user was loading many inventory records from a specific location (common when doing inventory adjustments or from searches that were grouped by location) this process will be as much as 99% faster on large databases.
• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.
• Changed: the transaction list page now limits the description, notes, extra, and locations fields to 250 characters for faster retrieval of results.
• Changed: (case 16534) the choose interchange popup has been changed to be more like the new interchange screen.
• Added: hitting enter or doubleclicking an interchange option in the interchange popup now sends that item back to the screen. Also, the previously selected option will be automatically selected when the user shows the dialog again.
• Added: (case 10449) the transaction list on the history tab can now be sorted by newest transactions first or oldest transactions first. The default is newest first, to match the home screen.
• Added: integration to new tag printing format.
• Added: inventory.oemnumber is now an available option for building default aftermarket part tag #'s.
• Fixed: (case 17055) serials with status Lost and Found no longer count as serials that are on hand.
• Added: (case 17091) mis-matched side will no longer cause the interchange popup to not select the correct interchange application.
• Changed: (case 17091) as per user request, if a part already has a side filled out, choosing an interchange application will no longer set the side of the part.
• Fixed: an issue where the message text field didn't allow the user to enter newlines.

Part Configuration

• Changed: when the user types in a year when editing a model, the year will automatically be changed from 2 digit to 4 digit years, using the windows defaults.
• Added: when model names get symbols stripped out, the \ character was being skipped. This didn't match the model import process which stripped this character out.
• Added: part type messages can now be marked as important.
• Fixed: an issue where new messages were not getting a date created.
• Fixed: the messages dialog now remembers its last location.

Print Queue

• Added: this new server module allows scheduling database reports to be printed, emailed, or saved to a folder on any schedule the user wants. Contact ISoft for setting this feature up.

Purchase Orders

• Fixed: an issue where switching source store of a saved TO was not correctly deleting existing items, causing their allocations to not get properly released.
• Removed: (case 16987) the store dropdowns on saved TOs are no longer editable. If a user wants to change the source or destination of a saved TO, they should start a new document.
• Changed: all the pop-up messages when saving a TO have been updated to be clearer and have more obvious choices and cleaner wording.
• Fixed: an issue where the Print Transfer Order checkbox was not correctly saving its last value between closing and reopening the screen.
• Added: the print pick list checkbox now remembers its value between closing and reopening the screen.
• Added: (case 17182) part category is now loaded with the inventory items on the PO and TO tabs so that part type messages can be category specific.

Report Viewer

• Fixed: (case 15785) an issue where key choice parameters were displaying the incorrect value as soon as the user chose a value.
• Fixed: (case 15785) an issue where date, time, and date/time fields would display default values in a different format than the user's windows setting for date/time format. This was leading to those fields losing their default value.
• Fixed: (case 16029) entering a date before 1970 will no longer cause date-time pickers in the list to throw an error message that the user cannot clear. The user should now be able to enter any date back to 1601 (limited by the windows date time controls).
• Added: (case 16246) if the EDocuments extension is not loaded, the report viewer will attempt to continue using dynamic report parameters anyway. This could lead to database errors for some more complex reports, but it should be very rare. If the EDocuments extension could not be found during dynamic report processing, the status bar will now show a warning.
• Fixed: reports now show in alphabetical order.
• Fixed: (case 17162) if the report viewer screen was closed while a report preview was being built, or the user previewed a different report altogether, a crystal error would sometimes appear and it would occasionally keep the report viewer from previewing new reports. Now, we attempt to cancel the current preview and the user must wait for this cancellation process before closing the screen.
• Fixed: an issue where date parameters might sometimes not display correctly.
• Added: the report queue tab now works with the new report queue fields. Also, we now display notes and error message on the screen.

Reports

Billing

• Fixed: an issue with the middle subreport (Activity or Billing, whichever option is in use) listing documents from all stores even when not using centralized billing. This would rarely come up because 1) most companies use centralized billing & 2) even when doing per store billing, a customer would have to have documents from multiple stores in the date range for the issue to occur. The balance at the bottom would still be the store balance, but the documents in the middle would be different.

GL Sales Activity

• Added: optimization, tidy, reorder, and addition of a reference to what line on the so the entry comes from.

Inventory Count Sheet

• Changed: cleaned up the report, gave more room for quantities
• Changed: set '*' as the default for the compare parameter.

Inventory Summary

• Fixed: manufacturer grouping
• Added: core cost
• Added: a vendor group by option
• Fixed: The calculate average cost function now looks at inventory.inventorytypeid instead of inventorytype.inventorytypeid just in case the join to inventorytype doesn't happen. Updated the #non-vehicle unit and #unknown sections of the union to run average cost through the calculate average cost function.

Label

• Change: the report now has only one parameter, updated query.

Label Location

• Added: more dynamic resizing of text based on string length

Logo Tag

• Change: gave the report the last several updates to Tag, so they now match again except for the Logo
• Change: the report now has only one parameter, updated query.

Pick List

• Fixed: cleaned up the report and query, made it look presentable.
• Fixed: picked and needed columns, which were wrong.
• Fixed: tidied the report. It was ugly.

Picking Label

• Fixed: cleared out margins, adding resizing rules for location text below the barcode.
• Fixed: copied the existing LabelPicking report fields onto a copy of Label.rpt and renamed it so it will print correctly. Crystal is weird about odd-sized reports.

Purchase Order

• Changed: "phone" in shipping area to "shipphone".
• Fixed: set PO to order lineitems by rank. Any adjustments will print after standard lineitems.

Purchase Order Posting Report

• Fixed: report now sorts in the same order as the screen.

Purchase Order Receiving List

• Added: serials.
• Fixed: grouping, it now groups by PO Line.

Purchase Totals By Destination

• Removed

Sales By Category

• Fixed: restructured the report, cleaned it up.

Sales By Counterperson

• Added: updated adder to be dynamic/neater.

Sales By Inventory Type

• Removed: excel mode
• Added: quantity totals
• Added: distinct inventory type totals
• Added: options for seeing only adjustments or only non-inventory/misc. Previously, you could see adjustments and non-inventory/misc when you entered 0 for all types, but I thought it would be good for users to be able to isolate them if they choose.

Sales By State

• Added: a country parameter and country grouping, minor report cleanup.

Sales By Tax Item

• Added: a setting to suppress the accounting sections, default False
• Changed: renamed the Non-Sales column header (etc…) when there is only one non-sale adjustment type
• Changed: The report is now landscape
• Added: a column for nonsales
• Added: a column for nontaxable sales
• Added: an accounting footer to each section
• Added: a setting to treat taxable 0.00% as non-taxable (will show 0.00 in the taxable column)
• Fixed: regular taxable lineitems weren't caring about quantity
• Fixed: Replaced a bad taxable formula

Sales By Tax Item And City

• Fixed: just a quick fix, removing references to the {?excelmode} parameter.

Sales Order 11in

• Added: a new setting to show ta item name instead of the word "Tax" at the bottom of the report.
• Fixed: memo fields now actually hide if the setting is turned on
• Fixed: saving space on the invoice to prevent it from breaking onto a second page as frequently as it does (suppressing empty sections, etc…), adding 2 new functions to customize where invoicememos show up to potentially save even more real estate.

Sales Order Return

• Added: updated the report to include negative adjustments if desired
• Added: gave the ability to exclude core returns.
• Changed: Replaced partnumber column with tagnumber.

Sales By Inventory Type

• Removed: adjustments when the report is filtered by parttype. So now they only show when typeid is 0.

Tag

• Added: the 'Tag: flag cores' setting to optionally display 'CORE' in the top right when the part is a core.
• Change: the report now has only one parameter, updated query.

Teardown

• Changed: Moved Page Header A content to Page Header B and Page Footer. Suppress Page Header B on pages after the 1st page.

Top Customer Types Trending

• Added: A new insights trending report and adder, very similar to the one that looks at customers.
• Added: 'Week' as a group option, making sure the pie graph doesn't get cut off, CASTing the list of ids as CHAR because it decided at some point to behave like a memo field instead of a string, changed date formats in the top right corner.

Top Customers

• Added: Solution for getting the same (summary) information you'd find in some of the Trending reports, but in list form with no upper limit on seeing the top X.

Top Customers Trending

• Fixed: a parameter issue in the key and pie subreports. It was not narrowing down by store. All Stores (0) still worked as expected.
• Changed: the report orientation, made the bottom graphs more prominent since that is what the reports are about.

Top Part Type Age Trending

• Added: black average line and bar as long as topx > 1. This took some additional coloring rules in the line graph.

Top Part Type Sales Trending

• Changed: the report orientation, made the bottom graphs more prominent since that is what the reports are about.
• Fixed: a mislabled parameter in the comment header. Wouldn't affect anything, but… tidy.
• Added: New insight report.

Top Part Types

• Added: Solution for getting the same (summary) information you'd find in some of the Trending reports, but in list form with no upper limit on seeing the top X.

Top Salespeople Trending

• Added: New insight report.

Unmoved Inventory

• Added: a new parameter that allows you to pick whether you want to view the report by vendor or by inventory.dateentered.

Vehicle Type Profitability

• Removed: This report has been replaced by Vehicle Value Analysis.

Vehicle Value Analysis

• Performance: indexes, removing superfluous join for performance.

Work Order Internal

• Removed: Job ID field.
• Fixed: The year in the customerunit subreport was printing out in "2,015" format instead of "2015" format.

Work Orders

• Complete redesign of this report.

Sales Orders

• Fixed: (case 16316) an issue where an error would be thrown during SAV shipping quoting if the description of an item on a document was so long that the total URL length exceeded 2048 characters. Now, only the first 100 characters of the description are sent to solve this.
• Added: both billing and shipping addresses should correctly support ZIP+4 format. This means that the +4 section will no longer keep city/state/country from being auto-filled and if they zip is ever auto-filled, the +4 section will not be overwritten.
• Fixed: 0-padded zip codes will no longer be overwritten with non-padded zip codes.
• Fixed: (case 16947) an issue where loading a SO with an inactive tax item might not display the tax item correctly. This only happened if it was the second SO with this tax item loaded since the screen was opened.
• Performance: opening the SO screen should now be slightly faster, as a query for the store list has been eliminated.
• Fixed: (case 16964) an issue where the 'assign sequential id' checkbox for salesorder documents was always showing as unchecked and would not save changes.
• Fixed: the trucknumber field no longer accepts more than 20 characters. Entering long truck numbers before had the ability to cause database errors or for the end of the number to be chopped off.
• Added: (case 17055) when an inventory adjustment writes a serial # down, its status is now set to Lost instead of Sold.
• Fixed: (case 17055) serials of status Found can no longer be sold until they have been brought on hand by an inventory adjustment.
• Added: (case 17182) part category is now loaded with the inventory items on the screen so that part type messages can be category specific.
• Performance: many optimizations have been made to the loading process of SOs. In tests of a large SO (500 items), load time was decreased by as much as 35%.
• Performance: many optimizations have been made to the refresh process of SOs. In tests of a large SO (500 items), refresh time was decreased by as much as 50%.
• Added: (case 17110) the configure->SO documents popup now has a column for setting which document types allow 'price restrictions' (and therefore price approvals). To maintain backwards compatibility, all document types default to having this unchecked.
• Fixed: an unreleased bug where the default date when opening the screen was the lowest date the windows date/time picker supported.
• Changed: return lines and job lines no longer check the database for the price the customer should be charged, as these items calculate price differently.
• Added: (case 17110) the "!$" icon in the price field that previously would show up when a lineitem had a price of $0 has been split into a "?$" (warning) icon and a "!$" (error) icon. These are now used when the price on the document violates price restrictions. This applies only to document types where price verification is enabled.
• Fixed: an issue where, if the document type was switched to Inventory Adjustment (or any other write-down document), prices would remain at non-zero values. Now, prices are correctly set to $0 when switching to inventory adjustment document type.
• Added: when items are loaded (new or saved items) or the document is refreshed, the 'Price Verification' status is refreshed for all items.
• Changed: price is now bold, as it is an important field and should stand out.
• Added: every salesorder line now remembers the value of various price levels from inventory when the item is saved. This won't be updated after the SO is closed, as those fields are for historical reference.
• Added: when parts are loaded onto a SO, when item prices are changed, or when the document is refreshed, every item has its price acceptability refreshed. This is a new quality that uses the price control rules defined on the approvals screen to decide if a price on a SO is in need of approval or not, as well as retrieving the status of that approval.
• Added: the price column is now colorized based on whether that item's price is in need of approval, has price warnings, has been approved, or has been rejected. There are also icons that correspond to these states and tooltips if the user hovers over them.
• Added: if the user doubleclicks on a price icon (or in the price field when it has an error or warnings), a pop-up will appear that tells the user how the item has violated the price rules (allowing them to more easily come into compliance).
• Added: right-clicking in the item list now gives the user the option to view the detailed explanation of why price rules were violated as well.
• Added: a SO cannot be finalized if any items have outstanding price violations.
• Added: the user is warned on each save if any items have outstanding price violations or warnings.
• Added: a SO that affects inventory cannot be saved if any items have outstanding price violations and the following setting is set to True: "Sales Orders"->"Prohibit price violations on open invoices". This defaults to False to more closely follow the credit approval system.
• Performance: saving a SO previously was running a query for each item if accounting was turned on (to verify that each item had a valid GL category and context that had accounting set up for it). Now, all items are checked in one query, making this much faster for large SOs.
• Fixed: an issue with get price control status on an item that wasn't yet saved.
• Added: support for the 'price violation/approval information' dialog that is shared from the approvals screen. This dialog allows the user to view approval status, detail information on why the approval is required. In addition, t he user can choose the reason why the price has deviated (from a fixed list), as well as filling out a more detailed explanation (optional).
• Added: when the user goes to save an invoice, if any items have a price violation, a dialog pops up that allows them to choose a reason (and an optional explanation) for the approval request. The user can click next to go through all items with no reason, or apply a single reason to all items with an approval request.
• Added: the price violation pop-up now shows the reason and explanation for the approval being rejected.

Search

• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.
• Changed: (case 16534) the choose interchange popup has been changed to be more like the new interchange screen.
• Added: hitting enter or doubleclicking an interchange option in the interchange popup now sends that item back to the screen. Also, the previously selected option will be automatically selected when the user shows the dialog again.
• Removed: the buttons for interchange notes as well as the button for interchange attachments, since these are all now available in the main interchange information popup dialog.
• Added: interchange attachments are now working correctly in the attachments info pane on part search.
• Added: integration to new tag printing format.

Vendor

• Fixed: (Case 15681) Type field for vendors is now supported up to 50 characters in the database and has support for autocomplete.
• Added: both addresses and alternate addresses should correctly support ZIP+4 format. This means that the +4 section will no longer keep city/state/country from being auto-filled and if they zip is ever auto-filled, the +4 section will not be overwritten.
• Fixed: 0-padded zip codes will no longer be overwritten with non-padded zip codes.
• Changed: (case 16869) when adding/editing a vendor price or purchase class that is store-specific, the user can edit the class name even when a store is selected.
• Fixed: an issue where editing price classes was not correctly renaming the price class in the dropdown on the vendor screen.
• Added: if a price class has all its multipliers set to 0 it will now be deleted automatically on save. This should give the user the ability to remove store-specific overrides to the default template on store specific price classes.
• Fixed: a database error that could occur when creating new store-specific price classes.

Vehicles

• Fixed: a crash that would occur if the user double clicked in the list but not on an item. case 15886
• Fixed: an issue where the bid/teardown totals wouldn't refresh correctly if prices were filled out with autopricing.
• Fixed: an issue where assembly manufacturer and assembly model would cascade into the 'actual' manufacturer/model (or vice versa) but the value would be removed when the user tabbed into the field.
• Fixed: an issue where manufacturer/model wouldn't be cleared if the user switched part types but assembly info would.
• Fixed: changing part types after manufacturer/model are already filled out will attempt to reselect that information under the new part type.
• Added: part type, manufacturer, model, assembly manufacturer, assembly model, and category now all have auto-suggest support (typeable dropdowns).
• Changed: part type now lists type # last so that the user can still search by #, but part types are sorted alphabetically.
• Fixed: a possible crash that could be caused by switching part types on an existing item.
• Added: integration to new tag printing format.
• Changed: unreceived quantity on POs marked as "Done Receiving" will no longer show up as a projected purchase cost.
• Fixed: an issue where component parts might not correctly copy the vehicle's year/make/model/vin/body style. Now, on save, this information will be updated on all parts on the teardown.
• Fixed: (case 16930) an issue where changing the inventory GL category of a vehicle might not correctly cascade down to all component teardown inventory items when the user confirmed that they wanted that to happen.
• Removed: (case 16749) Create copy Teardown and Create New Teardown are now both disabled when a teardown is selected (since a vehicle can only have a single teardown).

Warehouse Management

• Added: (case 16546) manually adding an item to a manual count should no longer be restricted to just items with a status of A or H and no longer be restricted to items with a quantity at a countable location.
• Added: (case 17081) manual count jobs now correctly set the new 'location' and 'date created' fields.
• Changed: (case 17081) when a count is done on a location and no parts are scanned, the count job will now still show the location the count was performed at.

Work Orders

• Fixed: a bug where a part selected on the search screen would not properly load onto the work order. (case 16081)
• Fixed: a bug where lookups by manufacturer code based lookups/hot items wouldn't work. (case 16082)
• Added: Red close button to the parts list. case 15872
• Added: Confirmation dialog when removing a part.
• Performance: (case 15754) temporary tables switched to in-memory table engine for faster database interaction.
• Changed: spacing and sizing of controls on the WO screen tabs to fit the look and feel of other screens.

Release 9.3

Database

• Fixed: (case 11845) a problem where location data would be incorrect after transferring a vehicle to a new store
• Fixed: (case 15908) an issue where, if max % of price was filled out, an item's cost could drop below inventory.averagecost (only matters if statically allocated average costs is turned on)
• Performance: (case 16372) makes the sales appraisal faster. This no longer uses a temporary table, and it eliminated multiple update passes. The loss is that we no longer ignore items with a price or days in inventory 2 standard deviations from the mean, as that requires running the query twice. Also, we now check settings for various values that control the fitness of a sales row.

Parts

• Fixed: (case 16002) an issue where using the mouse to click (confirm selection of) the first suggested item now properly selects the item. This was only causing trouble when the user would look items up by something other than the start of the item text.
• Fixed: (case 16370) an issue where the application might crash if the user typed something into a dropdown that didn't match an item then clicked outside of the combo.
• Added: the ability to use {inventory.oemnumber} as a tag when auto-generating tag numbers.

Reports

Pick List

• Fixed: 'picked' and 'needed' columns and made the report look nicer.

Top Customers Trending

• Fixed: an issue with the storeid parameter in the key and pie subreports.

Top Part Type Age Trending

• Added: this is a new report

Top Salespeople Trending

• Fixed: an issue with the storeid parameter in the key and pie subreports.

Vehicles

• Fixed: (case 16056) an issue where the store combo wasn't getting a default value correctly.
• Fixed: (case 15886) a crash when the user would double click in an empty space in a list on the performance tab.

Release 9.2

Reports

Sales By Tax Item

• Fixed: made the report look nicer, fixed a bad formula.
• Fixed: quantity problem on regular taxable lineitems.
• Added: a setting to the Sales By Tax Item report to treat taxable 0.00% tax item lines as non-taxable.

Sales By Tax Item and City

• Fixed: a parameter issue causing a "this field name is not known" error.
• Fixed: (case 16077) Removed non-sale column. Fixed aggregation error that occurred on invoices where there were multiple salesorderlines and at least one adjustment or multiple adjustments and at least one salesorderline.

Work Orders

• Fixed: (case 16082) a problem where the WO screen would not recognize adding hot items.
• Fixed: (case 16081) a problem where, when input in the lookup field kicked the user over to the search screen, double clicking on a part would open the parts screen instead of adding that part to the WO.

Release 9.1

MySql Connection

• Fixed: (case 16049) a problem where leaving the logfile parameter in host.ini blank could crash Enterprise

Release 9.0

Highlights

• The Work Order screen has been redesigned. The goal of this new format was to allow more room for technicians to take detailed notes. As well as the layout, we've added a new 'status' feature for jobs and fixed many bugs.
• The EBay extension has been improved and many features added.
• New reports in the 'Insights' category have been added to help examine trends in your business.
• Payment document type has been added to the Transaction List screen

Accounting

• Added: (case 9248) Footers for the account (total unique accounts) and amount (credit, debit and total) in the entries tab.

Customer

• Fixed: (case 14421) an issue where the remittance boxes (0-30 days, 30-60 days, etc) weren't refreshing correctly on saved customers when they were loaded.
• Fixed: (case 15265) an issue where the customer's default terms would appear to be set, but would stay NULL.
• Fixed: (Case 15430) Changing the default on a customer's payment methods now correctly saves and prompts for saving even if it's the only change.

Common Resources

• Fixed: the print tags popup no longer has memory leaks.
• Fixed: the print tags popup now has a layout and text prompts similar to other screens.
• Added: icons to the buttons in the print tags popup.

Crystal Reports Extension

• Added: (case 10703) a new edit->options->reports tab. The previous page wasn't very useful and essentially had no purpose any longer. The new version actually allows a user with permission to manage the reports visible in their system (deleting, renaming, managing parameters, etc) as well as add and replace existing reports.
• Removed: Edit->Options->Reports. This page has been moved to its own configuration screen because it affects all users, not just the local machine. Some users were accidentally changing reports when they meant to just configure their printers.
• Added: Configure->Printers. This is a permission-controlled dialog for managing all reports, system-wide.
• Added: Edit->Printers. Since this is a semi-common user operation, the printers page has been given its own edit dialog. For now, it still appears in edit->options as well.
• Added: support for retrieving information about a crystal report file loaded from the system. We can read parameter names and types as well as page orientation and desired paper type.
• Added: the rank column is now present in the Configure->reports dialog.
• Added: if the user adds new Report(s) from a file (through drag and drop or the add button), the report file is scanned for parameters and paper orientation. This information is auto-populated into the new report.
• Added: support for managing fixed report parameter values in the configure->reports dialog.
• Added: the advanced button now has a 'export selected reports' option. This will create a .SQL file with queries that will create the selected reports, parameters, and parameter values on any database. This will only be useful for someone who wishes to manage their own report files (rare) as well as the application support team.

Database

• Fixed: (case 14153) v_salesorderitem no longer contains duplicate column names.
• Fixed: A scansession key wasn't unique enough, and would cause errors on update.
• Fixed: (Case 14165) Corrected an issue where historical data was lost on table update.
• Fixed: back in 6.0 we deprecated the setting that would check whether to use statically calculated hold quantities, but for some reason fquantityavailable didn't get updated. This function now always uses the statically calculated hold quantities all the time, similar to the changes to fquantityonorder. This should make search much faster for any company who wasn't already using statically calculated holds.
• Added: (case 14738) altered vehicle.sellerinfo and vehicle.pickupinfo to text
• Added: an index to speed up adding pictures to parts
• Fixed: (Case 14312) updated the "Inventory" data import to be compatible with InnoDB tables
• Fixed: (Case 14342) A bug where creditsalesorderlineid values were not being updated correctly, resulting in lost data for salesorderline and purchaseorderline.
• Fixed: a duplicate key error from occurring during an "Inventory" import when there are duplicate tagnumbers in inventory
• Fixed: (case 14387) an issue where there would be an error when the first PO, SO, or WO was created on a new database that was using InnoDB.
• Performance: added an index to the collection table that makes searches faster after recent changes.
• Fixed: (case 14561) an issue where loading an existing WO with master parts would display the quantity as the default master part quantity instead of the saved value.
• Fixed: an issue where, if a store had a location with an empty location name, auto-pick shipping methods might do pick and move even when it was disabled.
• Fixed: (case 14637) if the user finalized a new SO with multiple items from the same vehicle, it was possible that they might over-allocate vehicle costs.
• Fixed: (Case 14647) a problem where, if the innodb_inventoryid and inventoryid were not the same, the core management screen would return cores incorrectly.
• Added: (Case 14633) shipping methods now have a field called showonpicking, which controls whether documents with this shippingmethod can be shown on the picking screen.
• Fixed: an issue where transferred vehicles (and parts that are non-replenishable) would be status S after being transferred instead of status T.
• Added: (case 14912) for speed purposes, an index has been added to salesorderline involving vehicleid, salesorderid, storeid, salesorderlineid. This speeds up sales order loads significantly on very large data sets due to what appears to be a bug in MySQL.
• Performance: (case 14920) sales appraisals now only consider sales history with a matching manufacturer within the last 2 years. This makes the appraisal process take 90% less time.
• Added: flocationrefresh should now correctly 'merge' locations on a part if the user renames a location in the location library to match another location. Before, an error would be thrown because the part had a duplicate location.
• Performance: frefreshdocument_delivered is now much quicker. It was taking about 20-30s to run for all 150 items on large documents, but now it takes about 1.5s.
• Fixed: an issue where inserting new report parameters was causing issues.
• Fixed: an issue keeping ITrack from inserting new report parameters.
• Added: a new permission controlling whether the user can go into the configure->reports dialog.
• Fixed: an issue where flocationrefresh could throw duplicate key errors if a part was at one location and had the locationid of a different location. This should also make the refresh operation faster.
• Removed: (case 14928) the change item price permission wasn't always working because there was a setting that had to be set before it would control things. This setting has been removed. Now, the permission alone controls whether a user can edit prices on a sales order. This permission has been defaulted to on for all users who could edit sales orders to make sure no one loses functionality.
• Removed: an unused query from pgetsales_appraisl
• Fixed: (case 15275) a possible database error that could occur while finalizing a SO or WO. It was a rare recursive function error that could occur when adjusting inventory locations.
• Removed: an unused setting that was redundant with the setting for the default number of days the customer has to return a core charge.
• Added: there is now a unique key in the importtypecommand table, this should avoid any issues where duplicate commands get created.
• Added: (case 15204) support for a new command timing for import scripts "Before Mapping".
• Fixed: (case 15311) an issue where vehicles might consume an incorrect cost if the corresponding GL category had a 'maximum % of price' filled out.
• Added: (case 15341) an "Ext. Price" search filter and field to the Transaction List.
• Added: an index for speeding up sales appraisals for WO activity.
• Added: unique indexes to tables used by the Transaction List to help add future fields and filters.
• Added: (case 15313) receiving a vehicle on a PO can now set the vehicle's received date again. Now, there is a setting that can disable this for those who want to set received date manually.
• Added: (case 15313) collections now have a date created. This will be useful for storing when a teardown was created.
• Fixed: (case 15249) an issue where work orders were not updating hold quantities correctly (mostly when consuming inventory from another store).
• Fixed: (case 14879) an issue where transfer orders were not updating their hold quantities correctly in all cases.
• Added: (case 15365) Payment document fields and filters to the Transaction List
• Added: (case 15231) functionality for scheduling SOs that automatically get cloned every month.
• Added: (case 15231) salesorderdocument.clonedsalesorderdocumentid, which (if filled out) will be the salesorderdocumentid of all salesorders that get automatically cloned as part of a recurring invoice scheme.
• Performance: added various indices to scanning related tables.
• Added: completed column to the jobtask table.
• Added: Update query to set completed to 'True' if the completeduserid is not NULL.
• Fixed: (case 15662) various small changes have been made to make several slow queries faster. This should be very noticeable on large databases.
• Added: (case 15702) Sales Order adjustment fields and filters to the Transaction List.
• Added: the index on salesorder.date now includes storeid to speed up some reports.
• Fixed: an issue where moving inventory could result in an infinite loop if a fractional quantity was used.
• Fixed: a possible bug where the Work Order External report had an incorrect value for it's type, and therefore never showed up as an option.

Data Management

• Fixed: an issue where unchanged row count could be negative.
• Fixed: an issue where "Before Conversion Validation" commands were not being run.
• Fixed: an issue where the record terminator wasn't displaying a linebreak correctly. Essentially, tab will now be shown as \t, and newline will be shown as \r\n or \n. Also, an escape character of \ will now be displayed as \ for consistency.
• Added: (case 15204) support for a new command timing for import scripts "Before Mapping".

Deliveries

• Added: (case 14633) documents that have a shipping method that is not set to show on picking will no longer show up to be picked.
• Fixed: (case 14633) an issue where putting the cursor into one of the staging location dropdowns, and then clicking out would erroneously cause a 'are you sure you want to change the staging area' popup to appear.
• Added: an extra check to suppress the confirmation dialog for changing the picking staging locations if the user doesn't have permission to change them. In some cases, users were still seeing this popup.

Ebay Extension

• Syncing an ebay account in an external browser is now "functional"
• Added: a refresh button for ebay accounts
• Added: now notify the user when an account sync is in progress
• Changed: the "Default" status filter option to say "Active or Closed" because Default is a not obvious.
• Changed: how the list controller footer formats listing counts(proper plural usage).
• Added: when "Active or Closed" is selected, the list control footer will now also show the count of active listing in addition to closed and total listings.
• Added: (Case 14748) "30 Days" and "Good Til' Cancelled" options for Fixed Price type ebay listings, not shown for Auction type ebay listings.
• Fixed: (Case 15255) Good Til' Cancelled now saves and loads correctly.
• Added: (Case 15298) 30 day (Days_30) and Good Til Cancelled (GTC) have been added as default choices.
• Added: (Case 14750) ShippingPackageDetails(Length, Width, Depth and Weight) are now added to our ebay request.
• Added: (Case 15639) Defaults added to the EBay config screen. Payment Methods still need to be fixed, as does the dispatch time dropdown pulling into new listings.Otherwise, defaults are all present and pulling into new listings.
• Fixed: (Case 15639) sandbox mode hidden from release builds
• Fixed: Additional functionality for defaults
• Fixed: (Case 15678) Moved tab order and renamed to Global Config and Advanced Config
• Added: Date range filtering on the auctions tab.(case 14749)
• Added: Global Shipping line to Ebay.xml Export
• Fixed: (Case 14747) Corrected some issues with ebay defaults loading
• Fixed: (Case 15729) Shipping Option Defaults hidden for now while we get change detection, saving and deleting working correctly.

Auctions tab

• Changed: Counts of each status group are no longer in statics. Now, the value is show in a list control footer for the selected status.
• Changed: There is no longer a splitter resizer thing in between the lists. The auctions list gets most of the available vertical space and the size of the transaction list is smaller and static. This was done in part due the splitter resizer and list control footers no being friendly with each other.
• Changed: "Create Hold" and "Create Invoice" buttons have been moved to the bottom as they're actions with require selection from the lists above.
• Added: "Create Hold" button now requires an auction to be selected to become active. Tooltips are aware of this.
• Added: "Create Invoice" button now requires an auction & transaction to be selected to become active. Tooltips are aware of this.

Parts Listing tab

• Added: More descriptive button text.
• Added: When the user goes to the tab with no items, focus it put on the "Add Part from Inventory" button. After adding an item, it is selected in the list and focus is put on the "Edit Item Listing" button so they can jump right into the dialog(I assume this is what most users will want to do at this stage)
• Changed: "Export" button has been renamed to "Export to CSV". This button is now only shown if the user has Turbo Lister installed.
• Added: Confirmation dialog when deleting Item(s).
• Added: "List on eBay" button. This functionality has been removed the from the Export split button to emphasize it.
• Added: Slightly improved feedback after pressing the "List on eBay" button via a statusbar message.
• Changed: The "Remove Item" button will now say "Remove Items" if they have more than 1 item selected in the list.

Edit Listing Dialog

• Changed: Edit Listing dialog has been reorganized to flow better and better spacing has been given between controls.
• Added: When the "Returns Accepted" checkbox is unchecked the various corresponding controls will become inactive.
• Added: Starting Price, Buy it Now Price & Reserve Price edits now do proper currency formatting.
• Changed: Some of the combos that were displaying API strings are now displaying friendlier strings(listing duration & dispatch time. (I would like to eventually fix the rest)
• Added: Category dropdown is now an advanced combo box that suggest things based on what the user types. This is useful for the tree style strings that eBay uses for their categories.
• Fixed: a crash that would occur if the user pressed the Delete button for Shipping Options when no shipping option was selected in the list.
• Added: Clicking the Add button for Shipping Options now automatically puts the users focus in the "Shipping Service" column dropdown in the shipping options list.
• Added: Icons to the Add and Delete buttons for Shipping Options

Templates tab

Edit Template dialog

• Added: When the "Returns Accepted" checkbox is unchecked the various corresponding controls will become inactive.

Global Settings Extension

• Fixed: (case 14207) an issue where printing reports would sometimes not pass the parameters in correctly.
• Removed: the old edit->Options->reports tab since there is a newer, better version.

Interchange

• Added: (case 15471) a new interchange search page.
• Changed: the existing interchange search page has been renamed to Interchange (Old) so that it can still be used side by side with the new interchange interface.
• Added: The work area now resizes with the total available screen space. The pricing area has been removed and a aggregate sales information area has been put in its place. The search panes have been reworked to be more intuitive.

Login

• Added: support for now configure->reports permission.

Master

• Changed: messages sent between screens through master are now done in a way that should be faster and allow the calling screen to know whether the message was handled or not.
• Fixed: an issue with global hotkeys that was causing them to not be called in some corner cases, like before the user had clicked into any screens.
• Fixed: an unnecessary error popup that would occur if the user was sending a message to a screen that was not open.
• Fixed: (case 14506) the database updater now correctly parses events and triggers, and should no longer have trouble with versions that end with an EVENT declaration.
• Added: if ITrack.exe fails to write a setting out to the ini file, it now displays an error in the status bar so that we can debug situations where users cannot seem to write printer choices to their settings file.
• Fixed: some minor issues with error reports that are reported to the error reporting server.

MySQL Connection

• Added: support for a new database mode where disconnects are not automatically reconnected, but instead must be manually reconnected.
• Added: (case 14552) support for a new database mode where the application catches all database disconnections and automatically attempts a fixed number of reconnection attempts before throwing an error (the default reconnection attempt count is 1). This is the new default mode.
• Added: for legacy support, there is a legacy database mode where reconnects are handled automatically by MySQL. This mode is not transaction safe, and so is being deprecated.
• Changed: Several low-level database operations have been sped up, including checking to see if a connection is live, as well as disconnecting.
• Added: all ISoft database error codes have been given formal #'s in the 100 to 200 range to keep them separate from the MySQL database error codes (1000 to 2999)
• Added: (case 14552) any disconnections (manual, timeout, explicit connection termination on the server side) will cause a new error ("Connection lost during transaction" error # 103) to be thrown on the next query to be run. This feature requires the database connection to be in the new AUTO_RECONNECT mode, which is the default. Also, this only applies to code that explicitly begins transactions. This solves a central issue where bad connections could lead to partial saves being lost due to the implicit ROLLBACK performed by MySQL when a connection is lost. Now, the application will detect this state and return an error so that it can be handled gracefully.
• Added: the MySQL connection now puts more information in the (optional) log file. This includes notes whenever disconnects were noticed, as well as a note for every auto-reconnect attempt. This makes the log file more readable when debugging operations that spanned multiple reconnects and identifying errors that occurred because of a disconnect in the middle of a transaction.
• Fixed: code that calls Disconnect directly will no longer cause the application to get into a state where it would not reconnect anymore.
• Changed: The Reconnect operation now simply calls Disconnect and Connect, to avoid previous issues where it was handled differently.
• Added: support for hiding the 'retry' button on the query error dialog if the error being reported is that the tranaction was interrupted. This is because, in this case, the entire transaction must be re-run to ensure validity.
• Added: Support for socket-based connections.

Parts

• Added: the global hotkey for 'search for part' (default: F4) now sends the part that gets found to the currently screen. If the current screen can't handle parts messages (such as Home), the part will instead be opened on the parts screen.
• Changed: Renamed the "Part Transaction" tab to "History".
• Fixed: (case 14203) if the user had replenishable parts default to not public, doing a save & clear operation after updating a replenishable part would cause an unnecessary 'do you want to save' prompt to appear during the screen close process.
• Fixed: an issue where typing into the location dropdown on the aftermarket tab would act normal unless the user tried to type in a new location name.
• Fixed: an issue where deleting a location from a part wouldn't work right if the user changed the location name before deleting it. This could happen if the user changed the location to "", implicitly causing a location to be deleted.
• Fixed: an issue where the location dropdown on the replenishable tab would always initially have a very short dropdown, making it hard to use.
• Changed: the 4 flex fields now only load the first 1000 distinct choices found in inventory for cases where there are more options than that. This makes loading parts and choosing part types much faster on databases where every component gets a unique value in one of these flex fields (such as a casting # or VIN). In cases like that, auto-complete is not helpful anyway.
• Added: the days to return core is now set on new parts based on the setting "Default: days to exchange cores for new items"
• Fixed: (Case 15187) New parts added to assemblies will now correctly show the retail core price in the retail core price column.
• Fixed: (case 15662) deleting a location should now more quickly delete all document allocations against that location. This query was taking longer than necessary on large databases.
• Fixed: an issue where the vehicle make and model might not display correctly when a the user loaded a stock # onto a new part.
• Changed: all the dropdowns now become readonly instead of invalid when the user doesn't have permission or other situations where the fields cannot be edited. Readonly dropdowns are easier to read and interact with.
• Removed: parts were only partially inheriting the status of the vehicle whose stock # was loaded onto the part. Because it wasn't working right, it has been disabled for now until we figure out if its something that should be added back in.
• Performance: loading vehicles should now be slightly faster and run fewer queries.

Part Configuration

• Fixed: (Case 15152) A database error that occurred when activating a new part category.
• Fixed: a bug where it was possible to create an inventory type of 0. case 15562

Purchase Orders:

• Fixed: (case 15132) a rare crash that could be caused by adding new order fulfillments to an existing PO.
• Fixed: all fulfillable items now show by default when the user opens the fulfillment dialog on existing POs.
• Added: doubleclicking an item in the "choose source" dialog inside the order fulfillment dialog now selects the item in question and closes.
• Fixed: sometimes adding a new fulfillment to an existing PO would show the wrong sources in the choose source dialog.

Report Viewer

• Added: if the user enters an invalid parameter value, when they leave the field, the value will be updated to reflect a valid value. This means entering "ABCDEF" into a number filed will be replaced with the value 0. This fixes an issue where such values were being treated as 0 but the user was not aware.

Reports

Billing

• Fixed: an issue with the activity section (or OIA list if that setting is turned on) of the report listing customer documents for all stores when a single store is selected.

Inventory Adjustment Log

• Added: (case 14614) a new sort by parameter

Inventory Count Sheet

• Fixed: (case 15085) an error that could occur when certain parameters are passed in

Inventory Detail By Part Type

• Fixed: (case 15428) average cost calculations on this report were updated to use the database costing function, which takes cost settings into consideration

Inventory Summary

• Fixed: (case 15120) average cost calculations on this report were updated to use the database costing function, which takes cost settings into consideration
• Added: (case 14884) a new option to group the report by category

Label

• Fixed: (case 14657) a problem where fields were getting cut off

Payment Receipt

• Added: (case 15092) store logo in header of the report

Sales By Tax Item

• Fixed: (case 15321) a problem where the report didn't sum groups correctly

Sales Order 11in

• Added: a setting to the SO giving the option to display tax item.
• Fixed: report now listens to the "print part detail" checkbox on work orders.

Tag

• Changed: (case 14249) barcodes have been made taller

Top Customers Trending

• New Report (case 12989)

Top Part Type Sales Trending

• New Report (case 12987)

Top Salespeople Trending

• New Report (case 12990)

Unbalanced Items

• Fixed: (case 14859) where the cashonly parameter would not get passed to the report correctly

Unmoved Inventory

• Fixed: (case 15733) a problem where the report could be blank if certain date parameters were entered
• Added: Added a parameter to Unmoved Inventory report, added dynamic parameters, and updated average cost calculation.

Vehicle Value Analysis

• Fixed: column "Sold ($)" is now wider
• Improved performance
• Added: GM% column

Sales Orders

• Added: (case 14599) new adjustment types will now default to printable. Also, the user can now change this field on all adjustment types.
• Fixed: (case 14637) when loading a SO with multiple parts off of the same vehicle where the entire vehicle cost was allocated should now correctly display the total vehicle cost on the items without requiring a refresh.
• Removed: (case 14637) when saving an open SO with multiple parts off of the same vehicle, the correct cost allocations should be saved now. When the SO is being finalized, this recalculation will still be run to ensure that vehicle cost allocations don't over-allocate the vehicle's current cost.
• Added: (case 14633) support for a new 'show on picking' flag for shipping methods. It controls whether to show documents with this shipping method on the picking screen and defaults to true.
• Performance: (case 14912) sales order loads are now much faster in some certain circumstances, mainly revolving around millions of historical sales records on certain versions of MySQL.
• Removed: (case 14928) the change item price permission wasn't always working because there was a setting that had to be set before it would control things. This setting has been removed. Now, the permission alone controls whether a user can edit prices on a sales order. This permission has been defaulted to on for all users who could edit sales orders to make sure no one loses functionality.

Search

• Added: if the user selects a part and hits enter or doubleclicks it to send it to another screen, if the recipient screen can't handle the part, it will be opened on the parts screen instead.
• Fixed: The old IN style for the WHERE clause was causing an unoptimized lookup during updates. Changed it to be AND/OR style and keys are hit now.
• Fixed: (case 13696) an issue where the search/clear buttons might not be visible on the part or vehicle search pages at minimum resolution.
• Fixed: an issue where printing serialized tags could take a long time and remove the 'needs printing' check from other serials in the system.

Shared/Controls

• Fixed: (case 14389) an issue where advanced combo boxes were not reporting value changes correctly.
• Fixed: (case 14319) an issue where double-left clicking in an edit did not select the entire word that was clicked on.
• Fixed: (case 14353) if a pop-up happened (or something caused the mouse to move) when the user was left clicking somewhere in the list, it was possible that when the modal dialog box was closed, the current mouse position would be used for click handling or drag & drop handling, causing items to get rearranged strangely.
• Fixed: an issue that could cause an advanced combo to ignore the first selection change the user made by clicking.
• Fixed: (case 14966) an issue where combos might send a 'changed' message when they had not actually changed, which could lead to an infinite loop on some screens.
• Fixed: (case 14966) an issue where combos might not register a change message when they were changed by the user clicking on an item in the dropdown.
• Fixed: an issue where the user could ctrl + page down to go past the last page in a paging combo
• Added: (case 14918) the page up/ page down keys now scroll a whole page in all combo boxes.
• Fixed: a long-standing issue where date-time fields in a list control would not draw the up/down arrows correctly until the user put their mouse over them.
• Added: support for turning 'drag & drop' support off in a list control. This is useful for pages and dialogs where drag & drop is handled for a different reason. This disables the ability to move and copy items in said lists.
• Fixed: an issue where killing focus from a combo while it was reporting a value change could cause it to throw a second value change, which was confusing the vehicles screen (2 bids being created when status dropdown changed to B because the bids tab would be activated).
• Added: when an ITEdit is invalid or readonly, the background is now explicitly painted as the 3dface color (same as buttons and dialog backgrounds). This should make no difference in pre-Vista installations, but after that, property pages have a white background instead of a grey background, and invalid edits were inheriting that background color. This made readonly edits not very obvious.

SQLFramework:

• Added: when a query error popup happens, the retry button will not be available if the error being reported is that the transaction was interrupted. This is because, in this case, the entire transaction must be re-run to ensure validity.

Vehicles

• Added: (case 14738) On the additional info tab, you can now enter more into the sellerinfo and pick-up location fields.
• Added: (case 14365) Bid Accepted Dialog check boxes now save to user settings and load from user settings.
• Added: (case 14361) the duplicate VIN # dialog now shows the store that the vehicle is at. (The store the active whole unit is at)
• Changed: (case 14362) a vehicle in bid mode no longer hides the whole units tab by default. This has been moved to a store setting in case anyone would prefer hiding this page until after a vehicle has been received.
• Added: (case 14364) the manufacturer and model dropdowns in the bidding/teardown lists is now sorted alphabetically.
• Changed: (case 14678) the teardown date has been renamed to Dismantled Date, and it is now set when the user checks the dismantled checkbox instead of when they add a teardown to the vehicle.
• Fixed: an issue where changing status From/To status B might cause popups to be shown twice or for 2 bids to be created.
• Added: (case 15095) if the user switches a vehicle from status B to status A, they will be asked if they'd like to send the vehicle to a PO, just like a newly available vehicle.
• Added: (case 15313) teardowns now display the date that they were originally created.
• Changed: (case 15313) the 'teardown date' field has been renamed to 'dismantled date', as that is what it has been used for and to differentiate it from the newly added date on the teardown page.
• Removed: there is no longer a dismantled checkbox since the dismantled date can be unchecked. The 'is dismantled' value now defaults from whether the dismantled date is checked.
• Fixed: (case 15302) adding items with an inventorytypeid of 0 will no longer cause appraisals to crash.
• Fixed: (case 15937) an issue where the sales appraisals and the HTP appraisals might cause a database error if they both attempted to connect to the database at the same time. This may have resulted in crashes if the timing was just right.

Warehouse Management

• Changed: (Case 14165) Screen reflects recent changes to scan sessions.
• Fixed: (case 15081) an issue where typing in the location dropdown was causing users a lot of difficulty because the user's focus was automatically moved to the print button as they typed.
• Performance: Results are only loaded when the user finishes selecting an item, instead of as they type. Also, loading lots of items in the manual count page should now be faster.

Work Orders

• Changed: The Work Order screen has been redesigned. The goal of this new format was to allow more room for technicians to take detailed notes. As well as the layout, we've added a new 'status' feature for jobs and fixed many bugs.
• Added: (case 828) Work Orders can now be saved without clearing the screen. This option exists in the Save button dropdown.
• Fixed: A few buttons were missing tooltip text.
• Added: Property Sheet with Property Pages for "Complaint, Cause, and Correction", "Notes", "Parts", and "Tasks and Labor".
• Changed: Most of the buttons at the bottom of the screen such as "Add Item", "Edit Item", "Delete Item", "Requests", "Add Task", and "Add Labor" have been moved to their corresponding property page to clean up the bottom of the screen and add context to their function.
• Added: Many new columns of information to the Jobs list.
• Added: (case 2509) Footer to the bottom of the Job list to sum up the corresponding column.
• Removed: Many of the totals from the bottom of the screen. The past totals edits had multiple totals in a single edit and often didn't fit the whole number.
• Added: A new "Subtotal" read-only edit at the bottom. Adding this number to "Estimated Tax" will get you the "Total". So, only these 3 "total" fields are now shown at the bottom.
• Changed: Reduced the size of the bottom area, which was done by removing many buttons and totals and better organizing the "On Save" checkboxes in a groupbox.
• Fixed: the edit item dialog was using the wrong setting value for the days to return cores.
• Added: Drag static between the job list and the property sheet.
• Removed: the group box around the "on save" checkboxes in the bottom right so I could make the bottom section shorter and use those few pixels for the job list and property sheet.
• Fixed: Controls on the pages now respect various state, such as permissions, job is selected, template is enabled, etc.
• Added: Tabs now have an asterisks next to their title if they have information on them. This way the user can see, without having to switch tabs, if they have info.
• Added: (case 14374) Status for jobs. These are "Not Ready", "Ready", "In Progress" & "Done". They are colored on screen as dark red, dark yellow, dark green & dark blue respectively.
• This can be changed from the job list or in the job dialog. We wanted to use a slider control but it doesn't work on XP so I'm using radios with ITColorStatics and it looks pretty good(yes, clicking the static works).
• Changed: The layout of the controls on job dialog. Also made the various multi-line able to get a new line by pressing enter.
• Changed: Tab order on the main screen now goes to the property sheet when you would expect.
• Fixed: A bug where the options in the job dialog's priority dropdown didn't match what was in the database or database object, and thus, if the user chose "Critical" or "None" from the dropdown, they wouldn't save to the document.
• Fixed: A bug where job priority wouldn't ever save if the user changed only priority on a job and nothing else.
• Added: Priority to the job list.
• Fixed: A bug where "Low" priority would never show as selected in the dialog because "Lowest" came first in the combo and contains "Low".
• Changed: (case 14864) The "Cost Factor" and "%" columns in the master part list are hidden when there is only 1 part. Serial column is hidden when no part in the list has a serial number.
• Added: Some new task and labor icons.
• Added: (case 2298) "Completed" checkbox
• When the "Completed" checkbox is checked, the "Completed By" field is available for the user to optionally select the user that completed the task.
• Changed: The UI of the Task dialog
• Added: All task fields can be edited directly in the list
• Fixed: (case 2298) A bug where the "assigned to" worker group wouldn't ever save.

Release 8.7

Parts

• Fixed: an issue where the vehicle make and model might not display correctly when a the user loaded a stock # onto a new part.
• Changed: all the dropdowns now become readonly instead of invalid when the user doesn't have permission or other situations where the fields cannot be edited. Readonly dropdowns are easier to read and interact with.
• Removed: parts were only partially inheriting the status of the vehicle whose stock # was loaded onto the part. Because it wasn't working right, it has been disabled for now until we figure out if its something that should be added back in.
• Performance: loading vehicles should now be slightly faster and run fewer queries.

Release 8.6

Data Management

• Added: (case 15204) support for a new command timing for import scripts "Before Mapping".

Database

• Fixed: (case 15311) vehicles no longer pay attention to max percent of price.
• Added: (case 15204) added a new timing to data management in order to facilitate importing into InnoDB tables.
• Added: (case 15204) added a unique key to importtypecommand table.
• Fixed: (case 15257) a database function that was causing a recursive function error to be thrown when finalizing a sales order.
• Performance: (case 15038) changed the function used to save POs to be faster.
• Fixed: (case 15036) a duplicate key error cause when saving a part with multiple locations of the same now. Now, the locations merge into one.
• Performance: (case 14912) reduced the amount of data looked at when doing appraisals. Appraisals now require at least a part type and manufacturer.
• Performance: (case 14912) added an index to salesorderline table to help appraisals.
• Fixed: (case 14698) vehicles now properly get set to status 'T' after being transferred to a new location.

Location Management

• Fixed: (case 15081) an issue where typing in the location dropdown was causing users a lot of difficulty because the user's focus was automatically moved to the print button as they typed.
• Performance: Results are only loaded when the user finishes selecting an item, instead of as they type. Also, loading lots of items in the manual count page should now be faster.

Parts

• Fixed: (case 14865) lots of UI issues with the dropdowns on the screen.
• Fixed: (case 14916) an issue where models were not cascading from the assembly model correctly.
• Fixed: (case 14966) an issue where changing a part type might crash the screen.
• Fixed: an issue where choosing a part type with the mouse might not change the part type #.
• Fixed: (case 14966) an issue where changing part type on an existing part might cause a crash.
• Fixed: (case 14977) an issue where changing models on the parts screen wasn't working properly, this impacted automatic pricing and other features.
• Fixed: an issue that could cause an advanced combo to ignore the first selection change the user made by clicking.
• Fixed: an issue where typing into the location dropdown on the aftermarket tab would act normal unless the user tried to type in a new location name.
• Fixed: an issue where deleting a location from a part wouldn't work right if the user changed the location name before deleting it. This could happen if the user changed the location to "", implicitly causing a location to be deleted.
• Fixed: an issue where the location dropdown on the replenishable tab would always initially have a very short dropdown, making it hard to use.
• Fixed: an issue where sometimes a location of random characters would be shown on the screen after loading a part (generally only occurred when a user had many screens opened).
• Fixed: various issues where the parts screen was not working as intended.

Reports

Label

• Fixed: Split Manufacturer and Model onto different lines so they have more room.
• Fixed: (case 15178) Child parts now display part manufacturer and model of parent instead of displaying nothing on Label report.

Sales By GL Category

• Fixed: a divide by zero error.

Tag By Location

• Fixed: Made the barcode taller, made the report look like the standard tag.
• Fixed: (case 15178) Child parts now display part manufacturer and model of parent instead of displaying nothing on TagByLocation report.

Tag Picking

• Fixed: Made the barcode taller, added the setting-based tag below the tearoff field.

Tag Receiving

• Fixed: Made the barcode taller, added the setting-based tag below the tearoff.

Vehicle Bid Internal

• Fixed: Corrected the COGS formula, labeled GM% for clarification.

Release 8.5

Database

• Added: (case 14633) in order to facilitate shipping methods that are for staging things that aren't ready for picking yet.

Deliveries

• Added: (case 14633) documents that have a shipping method that is not set to show on picking will no longer show up to be picked.
• Fixed: (case 14633) an issue where putting the cursor into one of the staging location dropdowns, and then clicking out would erroneously cause a 'are you sure you want to change the staging area' popup to appear.
• Added: an extra check to suppress the confirmation dialog for changing the picking staging locations if the user doesn't have permission to change them. In some cases, users were still seeing this popup.

Parts

• Fixed: (case 14601) an issue where, if a manufacturer or model was modified by another control (such as through the link models checkbox), the next time the user would tab through the field, some fields would be cleared.
• Fixed: (case 14702) an issue where the sub interchange number might be cleared the next time the user tabbed through it in some circumstances.

Sales Orders

• Added: (case 14633) support for a new 'show on picking' flag for shipping methods. It controls whether to show documents with this shipping method on the picking screen and defaults to true.

Vehicles

• Changed: (case 14678) the teardown date has been renamed to Dismantled Date, and it is now set when the user checks the dismantled checkbox instead of when they add a teardown to the vehicle.
• Added: when the user checks the Dismantled checkbox, Dismantled By will now default to the current logged in user.

Release 8.4

Database

• Fixed: (Case 14647) a problem where, if the innodb_inventoryid and inventoryid were not the same, the core management screen would return cores incorrectly.
• Fixed: (Case 14387) a problem with new innodb databases where it would throw an error when trying to insert the very first document in the document tables (SO# 1, WO# 1, etc.)
• Added: an index to the collection table to make it faster
• Fixed: a bug during pick and move if you have a valid location of ""
• Fixed: (Case 14637) a problem where if the document id was NULL (a new document), queries would return incorrectly.

Reports

Purchase Order

• Fixed: (Case 14658) a problem causing vendor state to sometimes display incorrectly.

Sales Orders

• Added: (case 14599) new adjustment types will now default to printable. Also, the user can now change this field on all adjustment types.
• Fixed: (case 14637) when loading a SO with multiple parts off of the same vehicle where the entire vehicle cost was allocated should now correctly display the total vehicle cost on the items without requiring a refresh.
• Fixed: (case 14637) when saving an open SO with multiple parts off of the same vehicle, the correct cost allocations should be saved now. When the SO is being finalized, this recalculation will still be run to ensure that vehicle cost allocations don't over-allocate the vehicle's current cost.

Work Orders

• Fixed: (case 14561) an issue where loading an existing WO with master parts would display the quantity as the default master part quantity instead of the saved value.

Release 8.3

Customer

• Fixed: (case 14421) an issue where the remittance boxes (0-30 days, 30-60 days, etc) weren't refreshing correctly on saved customers when they were loaded.

Vehicles

• Fixed: (case 14362) the whole units tab is now visible even on bid units.
• Added: (case 14361) the duplicate VIN # dialog now shows the store that the vehicle is at. (The store the active whole unit is at)
• Added: (case 14364) the manufacturer and model dropdowns in the bidding/teardown lists is now sorted alphabetically.
• Added: (case 14365) The "Bid Accepted" dialog now saves the state of the checkboxed and the user status.

Release 8.2

Common Resources

• Fixed: (case 14389) an issue where advanced combo boxes were not reporting value changes correctly.

Database

• Fixed: an issue where the Inventory import would run into a duplicate key error if there were duplicate tag numbers in inventory already.

Parts

• Fixed: (case 14345) an issue where certain values were not updated appropriately. This was report as causing problems with the autopricing system.

Release 8.1

Data Management

• Fixed: an issue where unchanged row count could be negative.
• Fixed: an issue where "Before Conversion Validation" commands were not being run.

Database

• Fixed: changed the Inventory import to be compatible with inventory as an InnoDB table.
• Added: an index to file.hash. This will speed up adding pictures.

Vehicle

• Added: (case 14738) On the additional info tab, you can now enter more into the sellerinfo and pick-up location fields.

Release 8.0

Accounting

• Fixed: various tab order issues
• Added: button icons

CoreManagement

• Fixed: various tab order issues
• Added: button icons

Customer

• Fixed: a database error that could occur if the user didn't choose a store for the billing address. This kept users from creating global customer records.
• Added: (case 13676) there is now a store level setting "Customer"->"Payments page: default new customers to 'cash only'" which controls whether new customers are cash-only or not by default.

Customer List

• Added: the list now has gridlines for consistency with other big lists.
• Fixed: performing a customer search for customers only at the current store was not correctly grabbing customer Q&A values.
• Performance: (Case 12685) customer search has been rewritten to be 99% faster in some cases. Namely, searches were found to be very slow if the user was searching for customer for only their store and some of the customers in question had many alternate addresses or Q&A options filled out.
• Disabled: currently, searching customers by balance has been disabled because it has been shown to be extremely slow on large databases, and that is not made obvious to the user. Any users who use this feature should contact ISoft, as we can discuss work-arounds.
• Fixed: several issues regarding getting an accurate count of matching customers when the user is searching by customer balance. This may be useful in the future, but as mentioned above, balance searches have been disabled due to speed concerns.
• Reconfigured the UI a bit as follows:
• Search related options(checkboxes) are now at the top next to the search button.
• The search type combo is hidden when doing a smart search
• Post-search related buttons are now at the bottom.
• Button change their state depending on if results are in the list or if an item(s) are selected.
• Buttons have state-specifc tooltips.

Database

• Added: (case 12722) the view vdeliverabletransferorderline now puts both source and destination comments into the internal comments of the view, making both comments viewable on the picking screen.
• Added: A line to update LXW's table entries to use correct names. Without this, Inventory Detail will not load on LXW.
• Removed: several settings in the parts location that are unused and are easily confused with in-use settings in other areas.
• Fixed: the trigger on inventory update no longer moves the primary location of the part unless the location changed, and even then, one of the locations must be valid. This helps prevent situations where touching a part would create an 'empty' primary location on a record with no locations.
• Fixed: (case 13044) an issue where fmoveinventoryprimarylocation was creating inventorylocation records that were not permanent and had a quantity of 0. This was contributing to situations where inventory with no location were getting an 'empty' location record added to them.
• Renamed: a setting that is being deprecated to its new name, and all values are being converted over so that software behavior remains the same.
• Fixed: an issue where, if the inventory table was InnoDB, replicating a part between stores to perform a transfer order would not work correctly (the part at the source store would be lost). This shouldn't have been affecting any databases in the wild.
• Fixed: (case 13110) if a part was replicated while any quantity was on hold, the holds would get copied over, so the new part would appear to be on hold when it was transferred. Now, items do not automatically get holds during replication.
• Fixed: an issue where replicating inventory items wouldn't reset the hold quantity on the newly created inventory record.
• Added: (case 13105) a new permission "Search"->"Can perform potentially slow searches", which controls whether the user is allowed to perform smart searches that the system has detected might take awhile to execute.
• Fixed: an issue where right-click list graphing would display fractional numbers as 'rounded' numbers.
• Fixed: an issue where right-click list graphing would open the graph website twice if the default browser was google chrome.
• Added: (Case 13226) Queries for removing the old FULLTEXT inventory.notes+inventory.description index and migrating the search module that used it to something more standard.
• Fixed: the template used for "right click list graphing" has been upgraded to fix the following issues:
• Fixed: (case 13273) an issue where grouping the x axis by value was incompatible with some graph types, like stacked column chart.
• Added: the graphing template now properly rounds all aggregated values to a similar precision as the input data (this solves issues where $1.50 would display as 1.49999999).
• Fixed: several issues where aggregation wasn't working correctly, this was breaking stacked bar charts.
• Added: support for grouping values into date/time ranges like "By Day/Week/Month/Quarter/Year".
• Tweaked: the layout of the graph to reserve more space for the graph itself.
• Fixed: an issue where pie charts wouldn't render because the label column (x axis) has to be a string
• Added: support for the google ChartWrapper class, which enables more real-time chart modifications
• Added: the user can now click a series in the legend to show/hide it.
• Fixed: grouping results by date range wasn't working for pie charts.
• Fixed: an issue where pie charts would fail to render because they had negative values.
• Fixed: an issue with the graph template where numbers might sometimes display 100.instead of 100.01
• Fixed: an issue where calling some move location functions could throw an error because a DECIMAL was being saved into a TINYINT. This would only have been a problem for servers with strictmode on.
• Fixed: (case 13437) if the user moved the primary location of a part (commonly done on the vehicles screen when parts are moved with a vehicle), they could get an error from recursive database references.
• Fixed: (case 13794) several issues that could be cause if the user needed to do auto-pick and move fractional inventory quantities (like .5). This could be caused by selling fractional quantities or by manually picking 50% before making the invoice auto-pick.
• Added: LXW changes that move storeid from scanner (which is now store-agnostic) to scansession.
• Added: numbers table now goes up to 16k, which makes many reports easier.
• Removed: a search setting for disabling picture counting which is not used anymore.
• Added: (case 9416) new permission that controls what stores a user can pick inventory at.
• Added: (case 9416) a permission that controls what stores the user can create run sheets for.
• Removed: an inventorysetting for "Location" which was redundant with "Locations"
• Changed: the location code is now allowed to be up to 50 characters long. Care should be used with long locations, since the total location name "parent code-location code-child code" needs to be less than 50 characters as well. Therefore, only 'top level' locations that will never have sub-locations should ever have codes this long.
• Added: (case 13003) support for report parameters that allow a choice between items that are loaded from the database. Also, parameters can now be hidden, and their editability can be customized.
• Changed: reportparameter.reportparameterid is now an independent auto_increment column, instead of being depdent on reportid. This should make it so that the table can be moved to InnoDB database engine.
• changing the length of the title field in the database to match the limit set in code and by ebay
• Added: ebay permission
• Added: (case 1464) a log table to record vendors that have been merged.

Deliveries

• Fixed: (case 14013) issues where the dropdowns were editable when source store All was chosen, and where the entire edit would not be 'greyed out' when it was not editable.
• Added: (case 9416) a new permission that controls which store(s) the user has access to picking inventory at. This controls the options the user can choose from the source store dropdown.
• Added: (case 9416) a permission that controls what stores the user can create run sheets for. This controls the options for the source store dropdown (which controls what stores' inventory the user can create runsheets for).

EBay Extension

• The Ebay Sync button will now always take you to account authorization page and reset the ebay contexts
• Added: screen permission
• Changed: ExternalURL won't work for our current image solution so I added PictureData which doesn't work with our current api set up because it doesn't add the xml attachments but its there for future development
• Fixed: a bug where shipping options weren't saving without killing focus before closing dialogs
• Fixed: a bug where users could add shipping options to the default template
• Fixed: Bringing items to the ebay screen from the search screen now ALWAYS maintains order instead of only sometimes case 13535
• Added: core prices are now added into pricing when an item is sent to ebay case 11525
• Added: a counter for the number of listings that are currently on the listings tab case 13887
• Various UI improvements

InventoryOverview

• Added: (as per user suggestion) the inventory filter dropdown now has a "QA < Min" in addition to "QA <= Min". This allows users to build orders composed of only more strict depletions.

ITMySQLFramework

• Changed: Recent error reports seem to suggest that in some cases, the error reporting dialog is not appearing for customers. Some changes have been made that may make it less likely that things won't work right.
• Fixed: a freeze issue that could happen if a very large query failed. The error was too large to be shown in the pop-up and therefore the message would also not be shown to the user.

Locations

• Fixed: the input field for code, delimiter, and description are now limited to a maximum number of characters that matches what the database can hold.
• Fixed: (case 13169) an issue where the location screen would crash if the user had a particular combination of permissions.
• Fixed: the locations screen is now properly locked down if the user has no permissions to edit locations.
• Added: (case 14092) paste sibling option to the paste dropdown. This is now the default if you hit the paste button. This is to make paste work consistently with the insert new button.
• Removed: (case 14092) hitting paste no longer selects the newly created location. This makes pasting work the same as the insert new button. This should make inserting many copies of the same location faster.
• Fixed: (case 14092) an issue where pasting the same location multiple times would increment the number in the description only once.
• Changed: the location editing screen now allows the location code to be up to 50 characters long. Care should be used with long locations, since the total location name "parent code-location code-child code" needs to be less than 50 characters as well. Therefore, only 'top level' locations that will never have sub-locations should ever have codes this long.

Login

• Removed: two extra, unnecessary error messages related to loading up stores that would appear if the user could not connect to the database.

Master

• Added: More error handling in certain cases of loading extensions. Only useful for debugging and extreme (non-occurring) corner cases.

Parts

• Fixed: (case 12905) an issue where changing the text of the primary location might not update the location on the part info tab.
• Fixed: (case 12905) an issue where typing in 'virtual' locations wasn't working.
• Fixed: (case 10340) an issue where saving a part with a location might either cause there to be two locations, or a duplicate location error to appear.
• Fixed: (case 13054) an issue where the 4 flex fields were not loading up saved data correctly.
• Fixed: the tab order was incorrect on several pages. Also, tabbing between pages was not working consistently.
• Fixed: if the user opens the screen or does a search, their focus will automatically be put into the part type # field.
• Changed: the setting Parts->"Model dropdown search pattern" has been switched to Parts->"Use only the start of the model name when searching for matching models". The new setting is just a True/False setting which controls whether typing in the model dropdowns on parts will find matches just by the start of the model name or anywhere in the string.
• Fixed: an issue where typing a full model name into the "Part #" field on the part info tab wasn't always finding the model correctly. This also fixes an issue where the user would be taken back to the first page in this situation.
• Fixed: an issue where the model dropdown's auto-suggest method would sometimes suggest an item by the middle of the model name even though that option was turned off.
• Fixed: a possible crash caused by typing in the model dropdown because the model and assembly model kept changing each other in a loop.
• Fixed: if no model is selected, the Manufacturer Part # edit will no longer contain a single space " ".
• Changed: when the user first opens the screen, their focus is automatically put into the tag # field for quick lookup of items.
• Changed: the replicate parts button now uses the same database replication method that the Transfer Order screen uses when replicating parts between stores. This fixes an issue where manually replicating a part between stores would replicate the held quantity as well.
• Fixed: (case 13322) an issue where creating a new location (or renaming an existing one) and rearranging the locations could cause locations to combine or even a database error.
• Added: (case 13923) there is now a location column in the part screen transaction list. This is a comma separated list of all location(s) a particular document line referenced at the current time, along with a summary of the quantity allocated at each location. Since work order master parts don't save a location that they referenced, "Primary loc." is displayed instead.
• Fixed: (case 14131) if the user switched an aftermarket/replenishable inventory item to Miscellaneous, the 'replenish' checkbox on the advanced tab would be unchecked, but upon save, the part would not become replenishable. The same is true for Misc/Standard items going to Replenishable items. Now, this change will be saved correctly.
• Fixed: (case 14203) if the user had replenishable parts default to not public, doing a save & clear operation after updating a replenishable part would cause an unnecessary 'do you want to save' prompt to appear during the screen close process.

Purchase Orders

• Added: (case 13105) similar to smart search on the search screen, things typed into the lookup field will popup a "Potentially slow search detected" if the input starts with a wildcard or is very short. If they have a new search permission, they can perform the search anyway.
• Added: (case 13492) the PO screen can now accept a bid to purchase. In this mode, the item will be purchased from the bid vendor for the bid amount, and all bid fees will be added as add on costs.
• Fixed: a crash that could occur when deleting a document level adjustment from a posting. Sometimes the crash would occur on the next load or save operation.
• Fixed: The following changes have been made to the interface for consistency with other document screens:
• Tab order issues
• Save is always the bottom-right most button and "S" is it's alt key shortcut.
• Clear is always to the immediate left of the save button
• A "On Save" section of checkboxes and/or combos is to the immediate right of the save button
• The "Add Item", "Edit Item" & "Delete Item" buttons are above the clear/save buttons in the same order.

Report Viewer

• Added: (case 13003) support for dropdowns whose values are loaded form the database. In addition, the current user, the store they're logged into, as well as other various pieces of information can be used as part of the query, making it so that running reports can use better user defaults in the future. This system supports some of the results being a default choice, as well as behind-the scenes key #'s for faster report support.
• Added: (case 13003) report parameters can now be hidden, as well as visible by readonly.
• Added: (case 13003) dropdown report parameters now support passing behind the scenes ids to a report for speed purposes, as well as allowing dropdowns that the user can type into (for wildcard support).
• Added: (case 13003) report parameters can now be marked as required, meaning the user cannot print until they are not empty. The user will be prompted to fill it out or to use the default value (if one exists).

Reports

Back Orders

• Replaced some columns with more relevant columns, cleaned up the report.
• Now only includes sales order document types that can affect inventory.

Billing

• Added: an alternative OIA layout, which will show instead of the standard layout based on a setting. Also, the logo and address were swapped in the header so the address is on the left and can be lined up with envelope windows with deliberate folding.

Receiving Label

• Added: conditional sizing to the barcode field based on length.

Part Search Results

• Updated query to look at the same view as the screen for make, vehiclemodel, and year fields.

Purchase Orders

• Fixed: a problem where line descriptions weren't showing up.

Sales By Customer

• Detail Level parameter now allows selection from line item, salesorder, and summary levels.

Sales Order 11in

• Fixed: Displayed tax amount no longer rounds.

Tag

• Added: a setting to display tagnumber below the barcode in addition at the top of the report, False by default. This is good for tearoff tags.
• Increased the height of the barcode.

Weekly Sales Insights

• Added: average invoice amounts.

Sales Orders

• Added: (case 13105) similar to smart search on the search screen, things typed into the lookup field will popup a "Potentially slow search detected" if the input starts with a wildcard or is very short. If they have a new search permission, they can perform the search anyway.
• Fixed: The following changes have been made to the interface for consistency with other document screens:
• Tab order issues
• Save is always the bottom-right most button and "S" is it's alt key shortcut.
• Clear is always to the immediate left of the save button
• A "On Save" section of checkboxes and/or combos is to the immediate right of the save button
• The "Add Item", "Edit Item" & "Delete Item" buttons are above the clear/save buttons in the same order.

Search

• Added: (case 13105) if the user performs a search with nothing filled out, they will get an error that says "Search too general, please narrow down your search". This should prevent the user from accidentally locking things up for awhile.
• Added: (case 13105) if the user performs a Smart Search, if the smart search filter starts with a wildcard, or the input string is very short (customized in a setting, but defaults to less than 2 characters), the user will be told that this is potentially a slow search. If the have a new permission "Search"->"Can perform potentially slow searches", they can continue anyway. Otherwise the user will be prevented from performing the search. This should prevent very simple searches that take too long to perform on large databases.
• Performance: (case 13105) if the user is doing a "Group by locations" search, the query will not contain a GROUP BY (unless the user is searching by serial #). This makes large searches faster if the user is finding lots of results but attempting to grab only the first 1000 with a LIMIT.
• Performance: (case 13105) if the user is doing a normal search, the query will attempt to not use a GROUP BY clause (unless the user is searching by serial # or location). This makes large searches faster if the user is finding lots of results but attempting to grab only the first 1000 with a LIMIT.
• Fixed: an issue where the side dropdown had all side options repeated twice.
• Removed: (case 12528) the user can no longer disable the ability to count part and vehicle attachments on search. This feature did not add significant time to search.

Vehicles

• Removed: several unnecessary queries that were being run on save and load.
• Added: when a whole unit is saved, the post-save database functions are now correctly run.
• Fixed: (case 13216) an issue where, if the user created a new vehicle and sent it to a PO, the item would not correctly appear on the PO screen if a new database configuration was in use.
• Fixed: a crash that could happen if the user added a second bid to a vehicle with exactly one bid.
• Added: a 'Create PO' button that is available whenever a bid is selected. This allows the user to send the selected bid to a PO (including fees, amount, and bid vendor). This is useful for situations where a bid is accepted but the receiving PO is not created at that time. This allows the user to create a bid PO for a vehicle after the bid has been accepted, or a second time if the original PO has been voided.
• Fixed: an issue where copying a saved bid/teardown to a new bid would not save the bid items correctly.
• Added: (case 13492) when the user sends the vehicle to a PO to be received, if there is an accepted bid, that bid information will be used on the PO. This includes bid vendor, amount, and fees.
• Fixed: an issue where new bid vehicles would ask the user to send the vehicle to a PO on the first save.
• Changed: whole unit type is now always a required field, even for bid units. This avoids a possible database error. Plus bid templates were based off of whole unit type, so filling it out should always be required.
• Fixed: (case 13821) an issue where an existing vehicle would not correctly move when its location was changed. The parts would move but the whole unit would not.
• Fixed: the location dropdown was really small, making it hard to see all the available locations.
• Fixed: a crash that was occuring after a save operation where the screen was not cleared and the user inventoried part of a teardown list. The crash would occur after save if the user changed anything on the unused template components.
• Changed: (case 13857) the way sales appraisals are calculated has been completely rewritten. Large teardown lists were taking a long time to process sales appraisals, especially at remote yards. Now they are processed in batches of 50, which greatly reduces communication time. Also, sales appraisals are processed on a secondary database connection. This can make them slower to start, but it should fix an issue where sales appraisals that were still processing during save were causing random behavior, crashes, and broken vehicle saves. This was more common at locations with longer teardown lists and slower connections.
• Fixed: Various tab order issues
• Added: Pressing "New Vehicle" or doing ALT+N will now put the user on the first property page so they can begin entering in a vehicle. The vehicle screen defaults to the user getting focus in the stock # lookup field when the screen loads. So now users can use ALT+N to quickly start entering a vehicle.
• Added: Icon to Copy Bid button
• Changed: The right alignment of the checkboxes made it look like they were for the more field edits, so I rearranged the screen a bit to make it more clear.

Vendorlist

• Added: the list now has gridlines for consistency with other big lists.
• Added: (case 1464) ability to merge vendors. This includes addresses, attachments, options, catalogs & purchase orders.
• Changed: The Vendor List screen UI is now consistent with the Customer List screen:
• Button state handling
• Button state-specific tooltips
• Various tab order fixes
• Clear button has been removed from the tab order
• If search type smart search or part id, the 2nd dropdown is hidden.

Warehouse Management

• Added: support for showing fast inventory move detail information.
• Fixed: an issue where doubleclicking item detail for moves wasn't opening the corresponding part.
• Added: (case 12251) the inventory count detail list is now limited to loading 1000 items at a time. This should keep very large count jobs from freezing the screen. Even though only part of a job is loaded, the user is notified that there is more information, and the entire job can be approved at once.
• Fixed: (case 13610) an issue where the arrow icons didn't move with the items if the user sorted the list or moved items by dragging and dropping them.

Work Orders

• Added: (case 13105) similar to smart search on the search screen, things typed into the lookup field will popup a "Potentially slow search detected" if the input starts with a wildcard or is very short. If they have a new search permission, they can perform the search anyway.
• Fixed: an issue where the parts list might be hard to read if the user hid and unhid some of the other lists of data.
• Fixed: an issue where the "& Print Work Order External" checkbox might be hidden on a WO sometimes when it shouldn't be.
• Changed: Some tooltip text
• Changed: Placement of buttons in the bottom right to be more consistent with the Sales Order screen as per case 13565.
• Added: Button icon to the Requests button
• Added: Clear button(checks if there are unsaved changes before clearing)
• Fixed: The following changes have been made to the interface for consistency with other document screens:
• Tab order issues
• Save is always the bottom-right most button and "S" is it's alt key shortcut.
• Clear is always to the immediate left of the save button
• A "On Save" section of checkboxes and/or combos is to the immediate right of the save button
• The "Add Item", "Edit Item" & "Delete Item" buttons are above the clear/save buttons in the same order.
• Fixed: An issue where the word "Correction" was getting trimmed on the "Complaint, Cause, Correction" static text.
• Changed: The read-only price edits at the bottom are no longer in the tab order.

Release 7.10

Customer List

• Performance: (Case 12685) customer search has been rewritten to be 99% faster in some cases. Namely, searches were found to be very slow if the user was searching for customer for only their store and some of the customers in question had many alternate addresses or Q&A options filled out.
• Disabled: currently, searching customers by balance has been disabled because it has been shown to be extremely slow on large databases, and that is not made obvious to the user.

Parts:

• Fixed: an issue where typing into the location dropdown on the aftermarket tab would act normal unless the user tried to type in a new location name.
• Fixed: an issue where deleting a location from a part wouldn't work right if the user changed the location name before deleting it. This could happen if the user changed the location to "", implicitly causing a location to be deleted.
• Fixed: an issue where the location dropdown on the replenishable tab would always initially have a very short dropdown, making it hard to use.
• Fixed: an issue where the vehicle make and model might not display correctly when a the user loaded a stock # onto a new part.
• Changed: all the dropdowns now become readonly instead of invalid when the user doesn't have permission or other situations where the fields cannot be edited. Readonly dropdowns are easier to read and interact with.
• Removed: parts were only partially inheriting the status of the vehicle whose stock # was loaded onto the part. Because it wasn't working right, it has been disabled for now until we figure out if its something that should be added back in.
• Performance: loading vehicles should now be slightly faster and run fewer queries.

Vehicle

• Fixed: (case 15530) a bug where changing the vehicle's status to 'B' causes two bids to be created.

Release 7.9

Manage Warehouse

• Fixed: (case 15081) an issue where typing in the location dropdown was causing users a lot of difficulty because the user's focus was automatically moved to the print button as they typed.
• Performance: Results are only loaded when the user finishes selecting an item, instead of as they type. Also, loading lots of items in the manual count page should now be faster.

Release 7.8

• Fixed: (case 14979) an issue where changing category wouldn't update the whole units tab.
• Fixed: (case 14977) an issue where changing models on the parts screen wasn't working properly, this impacted automatic pricing and other features.

Release 7.7

Parts

• Fixed: (case 14966) an issue where changing a part type might crash the screen.
• Fixed: (case 14966) an issue where choosing a part type with the mouse might not change the part type #.
• Fixed: (case 14965) printing from the parts screen could crash Enterprise. This requires a full rebuild.

Release 7.6

Customer

• Fixed: (case 14932) an issue where the customer screen would show changes when no changes had been made.

Parts

• Fixed: (case 14865) lots of UI issues with the dropdowns on the screen.
• Fixed: (case 14916) an issue where models were not cascading from the assembly model correctly.

Search

• Fixed: (case 13696) an issue where the search/clear buttons might not be visible on the part or vehicle search pages at minimum resolution.

Release 7.5

Customer

• Fixed: (case 14421) an issue where the remittance boxes (0-30 days, 30-60 days, etc) weren't refreshing correctly on saved customers when they were loaded.

Parts

Fixed: (case 14865) lots of UI issues with the dropdowns on the screen.

• Fixed: (case 14345) an issue where SelectString was not suppressing change reporting. This was causing a 'value changed' message to be sent prematurely, which caused some screens to think the previous value was still selected. This prevented auto-pricing from working sometimes.

Vehicles

• Fixed: (case 14362) the whole units tab is now visible even on bid units.
• Added: (case 14361) the duplicate VIN # dialog now shows the store that the vehicle is at. (The store the active whole unit is at)
• Added: (case 14364) the manufacturer and model dropdowns in the bidding/teardown lists is now sorted alphabetically.
• Fixed: (Case 14447) A crash that could occur when adding a second bid to a vehicle.
• Fixed: (case 14363) the user is no longer prompted to create a PO to receive a vehicle on new bids.
• Added: (case 14365) The "Bid Accepted" dialog now saves the state of the checkboxes and the user status.

Release 7.4

Manage Warehouse

• Updated: screen was updated to be compatible with the latest version of LXW.

Release 7.3

Parts

• Fixed: (case 13761) an issue where a miscellaneous part with a make and a model would save vehicle model correctly, but not display it correctly on the next load.
• Fixed: (case 14131) if the user switched an aftermarket/replenishable inventory item to Miscellaneous, the 'replenish' checkbox on the advanced tab would be unchecked, but upon save, the part would not become replenishable. The same is true for Misc/Standard items going to Replenishable items. Now, this change will be saved correctly.

Vehicles

• Fixed: the location dropdown was really small, making it hard to see all the available locations.
• Fixed: (case 13821) an issue where an existing vehicle would not correctly move when its location was changed. The parts would move but the whole unit would not.
• Fixed: a possible crash when sending a newly saved vehicle to a PO to receive it.
• Changed: (case 13857) the way sales appraisals are calculated has been completely rewritten. Large teardown lists were taking a long time to process sales appraisals, especially at remote yards. Now they are processed in batches of 50, which greatly reduces communication time. Also, sales appraisals are processed on a secondary database connection. This can make them slower to start, but it should fix an issue where sales appraisals that were still processing during save were causing random behavior, crashes, and broken vehicle saves. This was more common at locations with longer teardown lists and slower connections.

Release 7.2

Parts

• Fixed: (case 13322) an issue where creating a new location (or renaming an existing one) and rearranging the locations could cause locations to combine or even a database error.

Reports

Label

• Different label format for vehicle units.

Location Label

• Location name font size now dynamically changes depending on length of the string to allow for longer location names.
• Added conditional size formatting to the barcode. Locationids over 99999 will print smaller so they fit.

Purchase Order Receiving List

• Report now shows quantity ordered, quantity received and still expected, instead of just quantity expected. No longer excludes line items that have all quanatity received.

Receiving Label

• Fixed an error in the query with locations.
• Different layout for vehicle units.

Vehicle Bid External

• Minor formatting changes to External Vehicle Bid.

Search

• Fixed: (case 13287) another (hopefully the last) fix for dead whitespace in a list control. This could occur if the user locked search results, scrolled down, then performed another search or hit clear.

Vehicles

• Removed: several unnecessary queries that were being run on save and load.
• Added: when a whole unit is saved, the post-save database functions are now correctly run.
• Fixed: (case 13216) an issue where, if the user created a new vehicle and sent it to a PO, the item would not correctly appear on the PO screen if a new database configuration was in use.

Release 7.1

Database

• Removed: unused setting Parts - Default location for received inventory
• Fixed: (case 13044) an issue where receiving quantity on an item with 0 qoh was not using the default part location automatically.

Parts

• Fixed: (case 10340) an issue where saving a part with a location might either cause there to be two locations, or a duplicate location error to appear.
• Fixed: (case 13054) an issue where the 4 flex fields were not loading up saved data correctly.

Reports

Purchase Order

• Added: side when to the line descriptions when the information is available.
• Fixed: row duplication error on the PO report.

Release 7.0

• Customer screen rewritten to be 90% faster
• Customers can now have state-specific tax exemptions, with expirations
• All customer/vendor/part messages can now be marked as important, and documents now bold, underline, italicize, and blink at appropriate moments to make important messages more obvious.
• Statically calculated holds are now live for everyone (they can't be turned off anymore). This means people who didn't manually turn this on in 6.0 now have it on, generally making big searches as much as 90% faster.
• Transaction list has changed the way it groups results to be the way users will probably expect (one row per document if no lineitem columns are returned, even if filtering by lineitem columns; one row per lineitem if lineitem columns are part of the result set, no matter what is being filtered).
• Vehicles screen now loads as much as 75% faster, and sales appraisal values are more accurate and more quickly retrieved.
• Bid system on the vehicles screen has been completely retooled. The process, UI, permissions, creation, rejection, and approval process have all been retooled. Also, the bid screen now has more business intelligence and gives a 'suggested bid' based on projected COGS and shows a gross margin % for both the suggested bid and actual bid.
• Lots of little bugfixes, and ease of use updates suggested by users both at the users' conference and after.

Common Resources

• Added: (case 11363) when standard parts are consumed due to a vehicle being sold, fadjustinventory is now properly called with a document type.
• Fixed: an issue where standard parts that are consumed due to a vehicle being sold were not depleting their locations or marking their serial #'s as sold.
• Added: the double black right/left arrow icon has been added. It is used for showing/hiding side panes.

Core Management

• Added: (Case 11881) there is now a part type column in the customer cores and returned cores pages. In the returned core page, it is the part type of the originally sold item, not the dirty core return.
• Added: (case 11552) changing the value in the location field when inventorying returned cores will now control what location the new cores will be sent to. For 'new' core records, the default return location is now used, but the user can overwrite this value on a core by core basis. This fixes an issue where new cores are showing up in VARIANCE and require a manual move.
• Added: the returned cores tab has been updated to make its usage more obvious. A prompt has been added to the top of the screen, the tag # column is now bold, and all 3 of the editable columns are now a different color than the other columns to make them more obvious. Many of the column tooltips have been updated to give more specific information on the usage of the screen.

Crystal Reports Extension

• Fixed: an issue where, if the user had an invalid attachment cache directory, printing might fail. This shouldn't affect most users, but it fixes a rare issue where the user may not be able to print through ITrack if their ini file was copied from another machine. Now, if saving a report file fails due to the directory not existing, code is run to reset the attachment cache ini setting.

Customer

• Fixed: overactive change detection on creating new customers.
• Removed: some unnecessary queries run when opening the screen. This is in an attempt to speed up loading.
• Changed: several changes to facilitate upcoming tax expiration changes.
• Performance: during the process of loading a customer, the Sales Order tab (sales history) was loading results several times. This was causing many unnecessary queries. Now, this page is only refreshed once per load.
• Performance: several unnecessary queries have been eliminated from loading a customer and opening up the screen to create a new customer.
• Performance: all pages on the customer screen are now loaded when the user goes to that page instead of immediately. This can greatly increase the speed of loading customers, especially on customers with a lot of sales history, as that data will not be loaded until the user goes to that page. In some tests, this decreased customer load time by as much as 90%, especially on slow connections or customers with lots of data.
• Changed: the customer screen now tells the user which tabs have been modified if they close the screen when changes have been made.
• Changed: all state dropdowns on the screen now use a state auto-complete feature. This makes it so that typing in the dropdowns works better, and also less queries to the database are required, speeding up the screen.
• Added: (case 3257) there is now an area on the payment/tax information tab where the user can enter multiple tax exemption records for a single customer. These tax exemptions can be for different states, can have expriation dates, and also allow extra notes to be saved about them. All existing tax exemption information has been moved over for all customers who had that info filled out. These new records will (by default) have no expiration date and will be valid for the state of the billing address of the customer. In some cases, this may be innaccurate, so contact ISoft Data to help you duplicate customer tax exemptions for other states, if required.
• Changed: the balance/remittance info on the payments tab is now in the same order it shows on billing statements, making a more consistent view.
• Changed: all controls on the payments tab have been re-arranged, re-labeled, and have had tooltips added. We believe the organization of this tab is now much more intuitive.
• Changed: the default payment method box has been dropped and now the default payment method can be specified in the payment method list.
• Changed: the payment methods allowed to a customer are now specified with a checkbox instead of item selection. This is because the user can more easily toggle checkboxes with the keyboard (such as by selecting multiple items and then hitting space to toggle the check).
• Added: (case 9726) the user can now specify messages as important. This will start to come into play on various screens.
• Changed: the resizable pane now has a minimum size, that way users will know that they can use the sidebar to view/edit long messages in an easier way.
• Added: tooltips to columns in the messages page.
• Added: the column order/width now saves on the messages page.

Customer List

• Fixed: (case 11561) an issue where hitting the "Show all" button might not remember the last search performed, leading to an error when attempting to print the customer list.
• Fixed: a possible error thrown when trying to print all customers that could result if inactive customers were being shown.
• Changed: the error message that pops up when the user attempts to print results when no results have been loaded is now more descriptive.

Database

• Fixed: (case 11363) an issue where running fadjustinventory wouldn't update inventory.status if the 'document type' passed in was NULL.
• Added: (case 11481) the schema for the report queue tables.
• Removed: several unused fields from the user table.
• Changed: several keys in the user table have been changed from signed to unsigned to match other tables.
• Added: some rank values (ordering) for all current transaction list filters and fields.
• Changed: fields now say "Sales Order" instead of "Document" when a single source is selected.
• Added: support for a new transaction list filtering method (documentsearchjoin.keyfields).
• Added: (case 11479) document search sources, filters, and fields all now have an 'active' field that allow the user to control whether certain search options are displayed.
• Added: (case 11479) there is a new permission that controls who can deactivate/activate/view inactive search options on the transaction list screen. It defaults to anyone with advanced reporting permissions.
• Added: new, more complete, data for the transaction list screen, now with rank ordering, the ability to hide, and fewer errors.
• Added: (Case 11694) log_inventorytransaction now tracks average cost changes
• Added: (case 3257) a table to store store-specific expiring customer tax exemption information.
• Moved: all customer tax exemption information has been moved into this new table, with a state matching the customer's billing address.
• Added: the customerpaymentmethod table now has a primary key. This will help this table migrate to InnoDB eventually.
• Added: (case 9726) the message table now has an important field, which defaults to off. Important messages will be displayed more aggressively.
• Fixed: (case 10967) fmoveinventorywithallocations now accepts a document lineitem # as an argument. All functions that call this have been updated.
• Fixed: (case 10967) fmovedocument_allocations now accepts a document lineitem # as an argument. All functions that call this have been updated. This should fix a bug where picking a document with a duplicate item might cause an error.
• Removed: (case 11925) some unreachable code in fadjustinventory
• Fixed: an issue where (on some database versions) the deliverable item views (used by the deliveries screens) might show blank for their document type.
• Added: prunforalltables now skips filechunk, log, BACKUP, and TEMP_* when performing an OPTIMIZE against all tables. These tables generally do not need to be optimized and they can consume a lot of time.
• Removed: some transitional code has been removed that allowed a company to decide whether hold quantities and on order quantities should be calculated by documents (fast) or every time a search is performed (slow). The 'calculate once' method has been working for awhile at several yards, so the option has been removed and now all available and on order quantities are calculated just once when documents are saved. This has shown drastic improvement on search times.
• Removed: an auto-complete user setting affecting location dropdowns. This setting is no longer in use, so it's being cleaned up.
• Changed: the nightly event that recalculates hold and on order quantities has been scaled back somewhat. Previously, all available inventory had these values recalculated every night. These values are staying pretty up to date, so this has been scaled back to only recalculating every saturday at midnight. Also, instead of recalculating every inventory record, only those that have been modified in the last 3 months will be affected. This reduces total calculated rows by as much as 90% in live tests.
• Added: Part type 3555 (Diesel Particulate Filter) is now added to all customer databases.
• Added: (case 11421) a new permission that controls whether a user can add/edit vehicles at statuses other than B (non-bid units). By default, anyone who could edit information on the basic page has this permission.
• Added: An event that periodically cleans camerachunk. This table can grow unbounded, and it most certainly does not need to.
• Added: (case 11977) deliverylinehistory.autogenerated, which keeps track of whether pick history was generated automatically by auto-picking or manually. This will quickly become important because it controls whether the system can automatically 'unpick' what was previously picked or not.
• Added: frefreshdocumentautopickhistory, which performs the 'auto-pick' and 'auto-move' that each of the fsalesordersaved, ftransferordersaved, and fpurchaseordersaved did before, making it easier to change all 3 at once.
• Changed: fsalesordersaved, ftransferordersaved, and fpurchaseordersaved are now simpler and just call frefreshdocumentautopickhistory to manage their auto-pick status.
• Added: (case 11977) if the user reduces the quantity on an item that is auto-picked, an appropriate quantity of items will be un-picked, and it will be moved back to where it was in the system before it was autopicked (if it was moved at the time of pick).
• Added: (case 11977) if the user switches the shipping method on a document from one that auto-picks to one that does not, the item will automatically be unpicked and it will be moved back to where it was in the system before it was autopicked (if it was moved at the time of pick).
• Fixed: an issue where fmoveinventory wasn't calling fmoveinventorywithallocations correctly, causing various database errors.
• Fixed: an issue where, when quantity is reduced on a document with an auto-pick shipping method, the item that was moved back was still allocated to the document (instead of the item at the staging area location).
• Fixed: a rare database error that might pop up when changing quantities on autopick documents.
• Added: (case 9315) tinventorypost_update trigger once again updates the primary location when inventory.location is modified. Whatever the primary location is at the time, it is moved to the new primary location.
• Added: (case 9315) fmoveinventorywithallocations, fmoveinventoryprimarylocation no longer overwrite the value of session variable SUPPRESSINVENTORYINTEGRITY_CHECK in case it was set by a previous function.
• Changed: (case 9315) fadjustinventory_location has been rewritten slightly to no longer involve inventory in the UPDATE for the vehicle table. This should avoid circular write lock issues when updating primary location on inventory.
• Fixed: an issue where, in some cases fmoveinventoryprimarylocation would not reset the SUPPRESSINVENTORYINTEGRITY_CHECK if the primary location didn't need to be updated, which could cause later calls to fail.
• Fixed: (case 9315) fverifyinventorylocationintegrity no longer updates inventory.location if it doesn't need to be updated, which should avoid circular write lock issues.
• Removed: a user setting "Default Whole Units" which was confusing and was not being used.
• Added: (case 11419) there is now a nightly event (runs at midnight) that will automatically reject open bids of a certain age (this age is specified in store settings under the Vehicles section). The setting defaults to 0, which turns this feature off by default. If you want vehicle bids to be rejected after a certain age (eg 30, 60, 90 days), configure this setting.
• Added: (case 11419) the nightly bid event can also automatically mark bid vehicles (status B vehicles) as deleted (status D) after the vehicle has existed for a certain amount of time and the vehicle has no bids or all bids are rejected. This is controlled by a store setting (specified in store settings under the Vehicles section) that defaults to 0, which turns the feature off by default. If you want bid vehicles with no open bids to be rejected after a certain age (eg 60, 90, 120 days), configure this setting.
• Removed: all 4 of the pickable document item views now ignore dirty core items. For now, the system doesn't seem to support picking dirty core items correctly, so this may be reversed in the future when the feature is more fully fleshed out. This resolves some issues with the items showing on picking as well as being picked during auto-pick handling.
• removed: customer.mergedintocustomerid, which is not in use and only exists on some databases.
• Added: there is now a stored procedure, pgetsalesappraisaldata, which populates a temporary table with sales appraisal data. There is also a new stored procedure, called pgetsalesappraisal, which calls pgetsalesappraisal_data and then selects information from the table. The fields returned attempt to emulate the fields returned by the AX and HTP appraisal return data. These stored processes work pretty much the same as the way sales appraisals were done before, but now they calculate the number of results, min value, max value, and deviance.
• Removed: (case 12168) reverting a recent change that would make receiving a PO mark a vehicle's date received. Apparently this interferes with some processes, and is not always accurate. This will be removed until a more acceptable solution can be found.
• Added: (case 11422) a new table called vehiclebidfee. This table stores projected fees for a vehicle bid before it has been accepted.
• Changed: the customer update log has been renamed to follow the standard log table naming conventions.
• Added: (case 11927) the customer update log now saves the ITrack user id session variable so that the log reports what user made the change.
• Fixed (case 12376) an issue where selling inventory would unnecessarily create an entry in costdiscrepancy.
• Fixed: an error with a field for the ebay screen.
• Removed: all database settings in the area "EbayExtension", since all remaining in-use settings have been moved to the area "Ebay Extension". This should keep the settings cleaned up.
• Removed: a bug was introduced into fadjustinventory back in 5.0 that would cause a row to be inserted into the costdiscrepancy table every time a part was validly sold on a SO or consumed on a WO. We're running some queries to attempt to clean those unnecessary records out.
• Removed: a bug was introduced into fadjustinventory back in 5.0 that would cause a row to be inserted into the costdiscrepancy table every time a part was validly sold on a SO or consumed on a WO. We're running some queries to attempt to clean those unnecessary records out.
• Fixed: (case 12477) fadjustinventory now recalculates the average cost of standard parts. Previously, 'returning' a standard part would not recalculate that item's average cost (add-on costs). This change fixes 2 issues with standard parts on sales orders:

1. adjusting quantity upwards on an inventory adjustment (a standard item was 'found' during a count) was causing vehicle costs to become over-allocated.
2. If a standard part was returned (possibly because of a warranty), the original cost the item was sold at will be put on the returned component so that it will be sure to consume it when it is consumed again. This should prevent issues where a part is returned after a vehicle has been completely costed out, but the component is unsellable, causing cost to sit on the vehicle again.

• Fixed: (Case 12662) An error trying to save a PO that used auto-picking on a posting with new quantity received when there were other postings with the same part being posted. Added a SUM to adjust all current postings that needed adjusted.
• Added: (case 8391) searchmodule.rank, which orders search modules.
• Added: (case 11583) Tax charged can now be broken up into any number or sub-charges and stored in the database. This is an optional module.

Data Management

• Fixed: (case 11719) an issue where import files with empty lines would say that the empty lines were being ignored, but then they would cause errors.
• Fixed: an issue where errors during opening a file to parse weren't being reported.
• Fixed: an issue where opening a second file would always fail.

Deliveries

• Fixed: (case 10967) when an item is picked and moved, the document lineitem # is now passed to the database functions. This should prevent a possible error that could happen when picking a document with the same item on it more than once.
• Fixed: (case 11928) a query error that would be displayed if the user displayed the lineitems for a particular document on the run sheets tab.

EBay Extension

• Removed: TurboLister download and checks have been removed
• Fixed: (case 11305) a bug where the default customer edit field wouldn't update
• Fixed: a bug where first time user assignment would require a screen restart in order for all screens to recognize a successful authentication process.
• Added: Listing screen now asks if you are sure you want to close if there are unlisted listings
• Removed: you can't delete the default template anymore
• Fixed: a bug where when closing the ebay extension if the listing page wasn't loaded would cause itrack to crash
• Fixed: a bug where pushing the update button would start but not successfully finish the authentication process
• Added: Users can now switch between sandbox and production mode as well as see what state the ebay extension is in currently
• Added: basic Hold order creation functionality
• Added: Ebay now opens the config page by default if there is no ebay account hooked up so that users can configure everything more easily
• Added: ebay screen is now able to keep track of invoices and hold orders created from the auction screen
• Fixed: some settings were still located in the area "EbayExtension" instead of the newer "Ebay Extension". They now all check the new area for consistency.
• Fixed: an issue where inventory items weren't grabbing their information correctly.

EDocuments

• Fixed: when data sources are matched to variables during variable replacement, backticks are now ignored. For example, {?location.locationid} will now be matched by data source location and location.

Global Settings Extension

• Added: (case 11481) GetReportQueue function, which is required for the report viewer screen to show the report queue tab.
• Fixed: an issue where, if the database could not be reached, or there was no database extension loaded, updates would not be applied when ITrack was closed.

ITMySQLConnection

• Changed: we now link against MySQL client library 6.1.3. This should bring in any performance improvements made in that time and some minor changes to error handling.
• Performance: removed a bit of unnecessary meta-data that was being stored with every query result set.

ITMySQLFramework

• Fixed: (Case 11682) A bug where attachments/binary blobs that had an escaped size close to or over MAXPACKETSIZE for the database connection would cause ITrack to hang for minutes and then report an out-of-memory exception.

Inventory Overview

• Added: (as per user suggestion) the inventory filter dropdown now has a "QOH < Min" in addition to "QOH <= Min". This allows users to build orders composed of only more strict depletions.

Login

• Added: GetUserName function which will look up the name of a user based on the user #. This is required by the print queue page on the report viewer screen.
• Removed: some unnecessary queries being run by several functions that look up user data.
• Added: (Case 11479) support for a new permission used by the transaction list.
• Fixed: a possible crash/error that could happen if the application was launched without database access.
• Added: (case 11879) user account names can now be edited in user configuration. New (unsaved) users can now be deleted as well (saved users are just de-activated).
• Added: (case 11879) when the user hits ok in user configuration, they will now be presented with a more user friendly error if there are duplicate user account names.
• Changed: minor UX tweaks to make user/group configuration easier and more consistent with other screens.
• Added: (case 11614) the configure users page now limits which users can be edited based on the current user's permissions. Essentially, users will only be able to administrate their own store(s) now.
• Added: new user accounts will automatically inherit the current plant that the administrator user is logged into.
• Changed: a user now needs global permission to edit groups, since they are shared across all plants.

Master

• Fixed: a possible crash that could occur when running under windows 8 on touch-enabled devices due to windows accessibility features.
• Fixed: (Case 11743) The dialog for downloading all updates now only triggers if there are no connections to be made (indicating a failure of DLL load or massive configuration failure). In the case that the local database goes away for a moment, the AU gives up on that attempt and waits for the next one. Errors of this nature create automatic entries in our error reporter.
• Fixed: Display bug where the updater would briefly display 'N+1/N Downloads Completed'.
• Changed: the product description that gets compiled into the .exe file now has a better description. This is important because Windows identifies an application by this description in Windows 8.
• Added: support for rich-text edit boxes.
• Changed: (case 11921) it was possible that ITrack didn't have any valid database connection, but it tried to get the local versionlist anyway, which would stop the update process. Now, if that happens, the system acts the same as if no database connection is present and attempts to continue. This should help prevent a state where an installation cannot be used and cannot get updates.
• Added: when the user hits "reset updates", they will now be put into a mode where we force the download of updates. This ignores some things that would normally stop update downloading, including lack of access to the local database or lack of database extension.
• Removed: code for 'demo mode', which is not currently supported and will need to be re-implemented in the future. This should fix some installations with old registration applications from accidentally putting an install in demo mode.

Part Configuration

• Added: (Case 11665) Categories now show their descriptions, and new descriptions can be created with them. Old categories can get descriptions by creating a new category with the same name and the new definition.
• Added: (Case 11734) Edit button and double-click handler for Categories.

Parts

• Fixed: (case 11396) an issue where creating a part with quantity but no locations might ignore the user's choice when they say to "Use the default location".
• Fixed: A bug where text files would attempt to 'preview' their entire blob, instead of having reasonable limits (I chose 50KB) or terminating early (string terminates instead of printing garbage now).
• Added: (case 9726) part messages can now be marked as important.
• Fixed: part messages area is now consistent with other message areas (important messages sorted first, then in date order).
• Changed: all dropdowns on the parts screen have been transitioned to the more modern 'advanced' dropdown boxes. This allows much more advanced auto-complete and auto-suggest behavior, as well as being more consistent with other screens.
• Fixed: an issue where a dropdown on the messages tab would momentarily be visible when opening the screen, causing some minor flickering and slowing down screen opening.
• Changed: when the user types in the location drop-downs matching results will now be found whether the user's input is found at the start or the middle of the string (before, typing "A" would only match "A-1" and "A-2", now it also matches "X-A-4" and "Y-A").
• Added: by user request, the part type dropdowns can now be typed in, allowing the user to search for part types by the middle of a part type name. When the user leaves this field, the currently selected item will replace whatever they have typed.
• Fixed: (case 9315) an issue with unreleased database updates where re-arranging location priority (and replacing the topmost 'primary' location) might cause the previous 'primary' location to be deleted and moved to VARIANCE.
• Added: (case 7890) if the current part meets one of the following criterion, the location dropdown on the part info page is hidden:

1. The part is serialized and there is more than 1 serial
2. The part has more than one location In either case, the location dropdown will be hidden. Instead a 'Multiple Locations' prompt is shown in its place to explain its absence.

• Added: (case 7890) there is now an Edit button next to the location field on the part info tab. Hitting this button will take the user to the locations list on the locations tab if the part is not serialized. If the part is serialized, they will instead be taken to the serials list on the Q&A tab. If the part is not editable, this button switches to "View".
• Added: new store setting "Parts"->"Primary location can be edited on the part information tab". This setting defaults to True. If it is False, the location field on the part information tab will always be read-only, forcing the user to edit locations on the location tab. The user can hit the new Edit/View locations button to take them to the area where they can change the location. This is useful for yards that wish to force users to use the main location interface.
• Changed: (case 12432) non-replenishable parts no longer automatically mark the first location on them as permanent automatically. Non-replenishable parts can still have permanent locations, but it won't be done by default. Replenishable inventory will still automatically mark the first location added as permanent.
• Added: suport for upcoming database performance improvements

Purchase Orders

• Fixed: an issue where adding items to a TO (by clicking the add button on the TO screen or by typing in an ambiguous tag # and then selecting a search result) would send the item to the current PO instead.
• Added: (case 9726) the messages pane now uses boldness/italics/underline/colors to make messages easier to read and important messages more visible. If an important message is loaded, the pane will flash.
• Added: when loading an existing PO/TO, important messages will be shown, but not flash.
• Performance: TO lineitem messages are no longer loaded one lineitem at a time, but are instead loaded in one bulk operation. This can make loading large TOs significantly faster, especially on slow connections.
• Added: (case 11867) support for item descriptions in the order request dialog (transfer orders only).
• Fixed: (case 12095) the "Add Item" button and clicking the "New Item" icon in the list were doing different things, and clicking the icon to search for transfer order parts wasn't working right. Now, both buttons do the same thing.
• Changed: the "Add Item" button and the clicking the "New Item" icon in the list now perform the same action. This should help avoid an issue that happened on transfer orders.
• Added: support for upcoming database performance improvements

Reports

Sales Order 11in

• Added: Now shows tax sub-charges if available.
• Added: Ability to print in French. This is changed with a store level setting.
• Added: a new setting to show counterperson (usual), salesperson (who gets credit for the sale), or both.
• Added: settings for alternate invoice memos for different document types.
• Fixed: Salesorders with no lineitems no longer cause the report to throw an error.
• Added: Set SO# to print at the top of all pages >1 in small text, centered. Good for invoices with many pages.

Report Viewer

• Added: date, time, and datetime fields now have the 'none' checkbox on the left, allowing the user to pass blank dates to reports, for situations were optional dates are desired.

Sales Orders

• Fixed: (case 11363) an issue where selling standard parts with a vehicle might not update the status of the parts to S.
• Fixed: (case 11251) an issue where doing a location-grouped search then sending a serialized part to a SO would add duplicate items to the invoice. It will now also correctly pop up and ask the user which serial # they wish to add, which is important for situations where there are multiple serials at a location.
• Fixed: (case 11512) an issue where the adjustment type dropdown would show as empty when the user selected the adjustment type on a saved, finalized invoice. In some circumstances, this was causing issues on save.
• Fixed: (case 11520) the configure SO document types dialog wasn't loading/saving the "Is Variance" column. Also, this has been renamed to "Is Write-Down" and its tooltip has been changed, both to make the effect of this field more obvious.
• Added: (Case 9726) the messages pane now uses boldness/italics/underline/colors to make messages easier to read and important messages more visible. If an important message is loaded, the pane will flash.
• Changed: the default for the user preference "Sales Orders"->"Show new messages" has been changed to True. This setting controls whether new (non-important) messages are shown to the user automatically by showing the messages page. This will not affect any existing users.
• Added: when loading an existing SO, important messages will be shown, but not flash.
• Performance: SO lineitem messages are no longer loaded one lineitem at a time, but are instead loaded in one bulk operation. This can make loading large SOs significantly faster, especially on slow connections.
• Fixed: a recent regression where clicking on the SO # field would not pop up the load SO dialog.
• Added: (case 11867) support for item descriptions in the order request dialog.
• Fixed: an issue where the customer list would be displayed after the user edited payment methods.
• Fixed: (case 11935) an issue where "Add/Edit shipping methods" would show up in the right click menu twice and one of the options would edit the payment method list.
• Fixed: (case 12193) checking the validity of a location for an item is now case insensitive. This fixes an issue with returning items if virtual locations were disabled and the return bin location was a different case than the setting for the default return location ("RETURNS" vs "Returns").

Search

• Added: as per a suggestion at the 2014 users' conference, the part type dropdown is now an autocomplete dropdown. Whatever the user types will be used to match against entries anywhere in the part type names.
• Added: support for other screens to send searches against vehicle flex fields (the 4 "more" fields) to the screen.
• Added: support for vehicle VIN searches to be sent from other screens.
• Added: (case 12338) the store list on the parts and vehicles search pages now has check all and uncheck all buttons above the store list. This should make it easier to quickly search all stores.
• UX: the part search page has been re-arranged slightly to match the vehicle search page and other areas in the software.
• Added: (Case 12338) if the user performs a search on parts or vehicle search pages with no stores selected, they will get a pop-up. From there, they can either cancel the search or search all stores. This makes the current version somewhat similar to an older version where unchecking everything searched all stores.
• Changed: the Assemblies info pane has been renamed to "Collections". This is because it was already showing other collection types (like teardowns, kits, and templates).
• Changed: the Assemblies info pane now shows the tag # of the master part when showing collections the item is in. Also, the description column now always contains the collection type (kit/template/assembly/teardown).
• Added: (case 8209) as suggested at the 2014 users' conference, the part search results now contains 2 new attention icons. One shows how many assemblies the current part is in, and the other shows how many components the current item has (if its an assembly). This makes identifying items that need to be pulled out of assemblies (or assemblies that might need to be broken down) more obvious. Double-clicking one of these icons opens the Assemblies (now called "Collections") info pane.
• Added: (case 8391) search modules are now ordered by rank, then name.

Transaction List

• Changed: the 'Document Type' list has been renamed to 'Source Name' on the screen and in tooltips. This should help avoid confusion when non-documents are searched as well as confusion between the source name and the document type (like Invoice or Quote).
• Added: (case 11442) replacing a saved search will now update the search description if it has not been modified from its original.
• Added: the way that filters on lineitem or inventory fields work has been completely redone. Before, you would see all lineitems on any document that you searched for. Now, only line items that match the search will be shown. For example, searching for invoices by Engine sales will only show the engine line items on the matching documents.
• Fixed: a crash that could happen if the user doubleclicked a saved search and any error message box came up.
• Added: (Case 11479) document search sources, filters, and fields now each have a right-click context menu. A user with appropriate permission can use this menu to de-activate (hide), re-activate (un-hide), and view inactive search options. Since only users with permission can see and use hidden search options, this allows a company to restrict search options as well as keep the list simpler for how they use the screen.
• Added: (case 11479) a user with permission can right click on any of the search option lists and choose to show inactive as well as active search options. This allows that user to perform searches with these options but keep 'basic users' search option lists short.
• Added: if the user loads/executes a saved search, if any of the sources, filters, or fields that were saved with the search are missing or hidden, the user will be notified that the search won't be able to be performed exactly as saved. They are given a choice to execute the partial search anyway.
• Performance: the time the system takes to refresh the source, filter, and field lists after a change is made (such as checking or unchecking some sources) has been significantly reduced, making the screen feel more responsive.
• Added: the filters and fields lists now have a column that shows a list of all sources each filter and field applies to. This column is only visible if more than one source is selected. This allows the user to tell exactly which sources will be restricted by a particular filter.
• Fixed: an issue where adding/removing a source from a search would cause fields and filters with defaults to be reset to default.
• Added: if a filter or field is hidden for one source in a search but not another, that filter/field will now only apply to the source(s) that it is not hidden for.
• Fixed: an issue where hiding a filter or field for multiple sources would lead the footer to report an incorrect number of items being hidden.
• Added: the source, filter, and field lists now show "items in use/item count" in the footer in the checkbox column. This gives the user an 'at a glance' idea of how many filters/fields they can see (unhidden) and how many are in use on the current search.
• Fixed: a misspelling on one of the labels on the screen.
• Added: Master Part work order filter
• Added: Vehicle Make sales order line filter
• Added: Vehicle Make sales order line field
• Added: Vehicle Model sales order line filter
• Added: Vehicle Model sales order line field
• Added: Inventory Category sales order line filter
• Added: Inventory Category sales order line field
• Added: Balance sales order field

Vehicles

• Fixed: (case 11309) an issue where clicking the new cost button might do noting on windows 8.
• Added: (case 11418) the user can now edit 'user status' in the "Bid Accepted" dialog. By default, no user status will be selected, but if the user chooses something, this will be remembered in the future.
• Added: the vehicles screen now has a "Bid Mode", which hides many fields that are not applicable to bid units. Currently, when the vehicles screen is in bid mode, the whole units, Q&A, performance, and costs tabs will all be hidden, along with several fields on the basic tab relating to whole units and dismantling.
• Changed: when a bid is accepted, the vehicle always changes to status A, leaving "Bid Mode".
• Added: there is now a "Create Bid" button at the bottom of the screen which (if the user has permission to add/edit bids) will switch the vehicle into bid mode and create a bid for the user.
• Fixed: the bids/teardowns tab was not correctly looking at the permission "Edit bids/teardowns" to control if users could edit its contents.
• Added: if the user rejects/deletes the last open bid on a vehicle, the system will ask them if they'd like to take the vehicle out of bid mode (and mark it as status D).
• Added: if the user hits the 'add bid' or 'create bid from copy' buttons on the bids tab, and the vehicle is not in bid mode, it will be put into bid mode.
• Added: if the user begins a new teardown, if the 'teardown date' on the basic information tab is not filled out, it will be set to the current date.
• Added: (case 9531) there is now a new 'duplicate vehicles' dialog that will pop up if the user enters a duplicate VIN. This pops up immediately after the user leaves the field and it will show them all other vehicles that share a VIN with the VIN that was entered. The user can continue, cancel the VIN change, or view these vehicles on the search screen.
• Changed: (case 9531) the warning that alerted the user to a duplicate VIN during save has been modified to use the new duplicat VIN dialog.
• Added: (case 11421) there is now a permission that controls whether the user can add/edit vehicles that are not status B (non-bid units). This essentially controls whether the user can edit vehicles that are not currently in bid mode. A user without this permission cannot make manual changes to the status of vehicles in bid mode.
• Changed: the GL category fields will no longer show as required fields (bold with an asterisk next to it) if GL accounting is turned off.
• Changed: the Type, Category, and GL Category fields are no longer required fields to save when the user is in bid mode. This means those fields will no longer be bold, and the screen won't mention them as required fields when saving.
• Removed: if the global setting was off that controlled whether every vehicle requires a whole unit, it was possible that the whole unit record would be deleted if the user unchecked the "Has Whole Unit" checkbox in the interface. Now, any corresponding whole unit will be marked as status D instead to avoid losing data. This will not affect most users, as this is a very uncommon scenario.
• Perormance: loading vehicles is slightly faster now, as a couple queries have been eliminated that were run on every load.
• Added: (case 11421) if the user starts a new vehicle (or hits clear), if they have the 'can edit bids' permission but not the 'can edit non-bid units', the vehicle will start out in 'bid mode'. Essentially, this represents a user that can only make bid vehicles.
• Changed: now, if a vehicle leaves bid mode, but a user does not have the 'can edit non-bid units' permission, they will still be able to edit the vehicle record until they save.
• Changed: the 'change detected' message box is now the same one that is used on various other screens, and it mentions what page(s) have been modified.
• Added: (case 11421) when the user loads a vehicle, the ability to edit it now follows the following logic: if the vehicle is in bid mode, the user must be able to edit bids to modify it; if the vehicle is not in bid mode, the user must be able to edit non-bids.
• Removed: references to the user setting "Default Whole Units" which was confusing and was not being used.
• Added: (case 11422) the bidding/teardowns list now has a footer control at the bottom of the list with totals in it. This should allow us to eliminate the old totals fields (and show totals for more columns).
• Removed: the old totals at the bottom of the screen. Rearranged the interface to utilize this new space properly
• Fixed: an issue where errors during sales appraisal might cause a crash. Now, those errors are properly reported to the user.
• Added: after a sales appraisal is complete, totals are recalculated.
• Performance: previously, sales appraisals required returning a lot of data from the server and performing a lot of math on the results. This could cause sales appraisals to take a long time to perform, especially on slow connections. Now, sales appraisals are calculated on the server and simply handed to ITrack. This should make performing sales appraisals on teardowns, bids, and breakdowns much faster, especially on slow connections. One benefit of this is that previous calculations only examined the last 100 times an item was sold, for speed. Now, we can consider all sales history.
• Added: support for store-specific sales appraisals. The sales appraisal value is still company wide, but this can now be adjusted in the future.
• Added: (case 11422) the bidding page now has several new columns: "Similar QOH", "Similar QOH (Global)", "Similar Usage (N mo)", and "Similar Usage (Global, N mo)". The first two columns will be used to display the current quantity on hand of similar items at the current store and globally, respectively. The second two columns will display the total quantity sold/consumed in the last N months at the current store and globally, respectively. The number of months to be considered in these columns is part of a new setting, and defaults to 12 months.
• Added: (case 11422) local/global quantity sold (12 mo) and QOH are now retrieved during the sales appraisal process. This is because retrieving extra data like this can be very expensive for large bids or teardowns, and the appraisals were already being offloaded to another thread, generally improving screen performance.
• Fixed: a possible crash caused by columns being hidden/shown when switching between a bid and a teardown.
• Added: (case 11422) the quantity consumed (both local and global) now take WO quantities into account.
• Fixed: an issue where tooltips for the header of the teardown/bid list might get misaligned if the user scrolled, then switched between a bid and a teardown.
• Added: tooltips to many columns in the bidding/teardown list.
• Fixed: an error with sales appraisals for items with an interchange number.
• Added: (case 11422) there is now a vehicle fees list next to the vehicle bid list. It is hidden when a teardown is shown, but it allows the user to manage projected fees for a bid if it were to be accepted.
• Fixed: an issue where the vehicle would not be saved if the user hit save on the "the screen has changed, do you want to save" dialog that would popup if the user closed a modified vehicle.
• Added: (case 11422) there is now a Gross Margin % field next tot he bid amount box. If the user writes a bid amount, the GM% will be calculated based on this bid, all bid fees, and current projected retail on all bid items. If the user fills out a GM%, the bid amount will be calculated such that fits that gross margin.
• Added: (case 11422) at the bottom of the screen, there is now a projected sales field, which is the projected total retail value of all items on the bid.
• Added: (case 11422) at the bottom of the screen, there is now a suggested bid which is calculated based on the projected sales, preliminary fees, and the % of sale price cost setting for the currently selected inventory GL category. There is also a Projected Gross Margin % field that contains a GM% based on the suggested bid, fees, etc.
• Added: (case 11422) if the inventory GL category is changed on the basic page, projected COGS will be recalculated on the bids tab, which can affect suggested bid and GM%.
• Added: when a teardown is selected, the suggested bid field is replaced with an "Estimated COGS" field, which is a sum of the projected total cost of goods sold on all items assuming the current quantity, retail price, and % of price costing setting of items on the screen.
• Removed: if the user loads a teardown with existing items, the "Use" checkbox can no longer be unchecked for those items, since that operation currently has no function (the inventory is not deleted).
• Added: all controls on the bidding page now have tooltips so that the user can learn more about them.
• Fixed: a crash related to teardowns on a vehicle with no bids.

Vendor

• Added: (case 9726) vendor messages can now be marked as important.
• Fixed: vendor messages area is now consistent with other message areas (important messages sorted first, then in date order).

Warehouse Management

• Fixed: (Case 11705) if the user changed a single manual count quantity multiple times, the value would trigger as 'not filled out' if the value was changed an even number of times.

Work Orders

• Added: (case 11867) when the user hits the "Order requests" button, if a job is selected, only the parts on that job will be shown for generating order requests. If no job is selected, all job parts are shown like before.
• Fixed: a possible crash when sending multiple jobs to the order request screen.
• Added: support for item descriptions in the order request dialog.
• Fixed: an issue where the "Use actual hours" checkbox in the WO type dialog wouldn't load the previously saved value correctly.
• Fixed: (case 12208) the tax amount being calculated by WOs was sometimes incorrect if some parts had the tax checkbox unchecked. This didn't affect the sales order that the job got sent to, which always calculated tax correctly.
• Fixed: if a closed WO is viewed, tax is no longer recalculated with the current tax rate. Now, the tax amount that was saved with the WO will be displayed.
• Fixed: an issue where newly created master parts (created on a build order) might use the incorrect store's default location for their location.

Release 6.3

Core Management

• Added: (case 11552) changing the value in the location field when inventorying returned cores will now control what location the new cores will be sent to. For 'new' core records, the default return location is now used, but the user can overwrite this value on a core by core basis. This fixes an issue where new cores are showing up in VARIANCE and require a manual move.
• Added: the returned cores tab has been updated to make its usage more obvious. A prompt has been added to the top of the screen, the tag # column is now bold, and all 3 of the editable columns are now a different color than the other columns to make them more obvious. Many of the column tooltips have been updated to give more specific information on the usage of the screen.

Purchase Orders

• Fixed: (case 12095) the "Add Item" button and clicking the "New Item" icon in the list were doing different things, and clicking the icon to search for transfer order parts wasn't working right. Now, both buttons do the same thing.
• Changed: the "Add Item" button and the clicking the "New Item" icon in the list now perform the same action. This should help avoid an issue that happened on transfer orders.

Work Orders

• Fixed: (case 12208) the tax amount being calculated by WOs was sometimes incorrect if some parts had the tax checkbox unchecked. This didn't affect the sales order that the job got sent to, which always calculated tax correctly.
• Fixed: if a closed WO is viewed, tax is no longer recalculated with the current tax rate. Now, the tax amount that was saved with the WO will be displayed.

Release 6.2

Data Management

• Added: the inbounding module is now standard on all databases.

Database

• Added: (case 11694) log_inventorytransaction now tracks average cost changes.

Deliveries

• Fixed: an issue where (on some database versions) the deliverable item views (used by the deliveries screens) might show blank for their document type.

FIFO

• Added: (Case 11287) FIFO system now records the attached vehicle's source when a standard part is created.

Login

• Added: (Case 11479) support for a new permission used by the transaction list.

Parts

• Fixed: (case 11396) an issue where creating a part with quantity but no locations might ignore the user's choice when they say to "Use the default location".

Reports

Billing

• Changed: formatting changed to increase readability.

Inventory Summary

• Fixed: Margins were getting cut off on the right side.

Label by Location

• Changed: report now sorts by location, tag, then serial number.

Location Label

• Changed: (case 11592) Location name font size now dynamically changes depending on length of the string to allow for longer location names.
• Changed: (case 11639) Added conditional size formatting to the barcode. Locationids over 99999 will print smaller so they fit.

Master

• Changed: the Auto Updater now checks for updates every 15 minutes instead of every 5.

Manage Warehouse

• Fixed: (Case 11705) if the user changed a single manual count quantity multiple times, the value would trigger as 'not filled out' if the value was changed an even number of times.

Tag by Location

• Changed: report now sorts by location, tag, then serial number.

Weekly Sales Insights

• Fixed: sizing issue that was causing the report to push onto 2 pages when previewed first.
• Changed: Switched the order of the top graph so it now reads left to right instead of right to left.

Transaction List

• Changed: the 'Document Type' list has been renamed to 'Source Name' on the screen and in tooltips. This should help avoid confusion when non-documents are searched as well as confusion between the source name and the document type (like Invoice or Quote).
• Added: (case 11442) replacing a saved search will now update the search description if it has not been modified from its original.
• Added: the way that filters on lineitem or inventory fields work has been completely redone. Before, you would see all lineitems on any document that you searched for. Now, only line items that match the search will be shown. For example, searching for invoices by Engine sales will only show the engine line items on the matching documents.
• Fixed: a crash that could happen if the user doubleclicked a saved search and any error message box came up.
• Added: (Case 11479) document search sources, filters, and fields now each have a right-click context menu. A user with appropriate permission can use this menu to de-activate (hide), re-activate (un-hide), and view inactive search options. Since only users with permission can see and use hidden search options, this allows a company to restrict search options as well as keep the list simpler for how they use the screen.
• Added: (case 11479) a user with permission can right click on any of the search option lists and choose to show inactive as well as active search options. This allows that user to perform searches with these options but keep 'basic users' search option lists short.
• Added: if the user loads/executes a saved search, if any of the sources, filters, or fields that were saved with the search are missing or hidden, the user will be notified that the search won't be able to be performed exactly as saved. They are given a choice to execute the partial search anyway.
• Performance: the time the system takes to refresh the source, filter, and field lists after a change is made (such as checking or unchecking some sources) has been significantly reduced, making the screen feel more responsive.
• Added: the filters and fields lists now have a column that shows a list of all sources each filter and field applies to. This column is only visible if more than one source is selected. This allows the user to tell exactly which sources will be restricted by a particular filter.
• Fixed: an issue where adding/removing a source from a search would cause fields and filters with defaults to be reset to default.
• Added: if a filter or field is hidden for one source in a search but not another, that filter/field will now only apply to the source(s) that it is not hidden for.
• Fixed: an issue where hiding a filter or field for multiple sources would lead the footer to report an incorrect number of items being hidden.
• Added: the source, filter, and field lists now show "items in use/item count" in the footer in the checkbox column. This gives the user an 'at a glance' idea of how many filters/fields they can see (unhidden) and how many are in use on the current search.
• Fixed: a misspelling on one of the labels on the screen.
• Added: Master Part work order filter
• Added: Vehicle Make sales order line filter
• Added: Vehicle Make sales order line field
• Added: Vehicle Model sales order line filter
• Added: Vehicle Model sales order line field
• Added: Inventory Category sales order line filter
• Added: Inventory Category sales order line field
• Added: Balance sales order field
• Fixed: an issue where the transaction list was not sorting negative currency values correctly.
• Fixed: a crash the user might experience when double-clicking a saved search.

Release 6.1

Common Resources

• Added: (case 11363) when standard parts are consumed due to a vehicle being sold, fadjustinventory is now properly called with a document type.
• Fixed: (case 11363) an issue where standard parts that are consumed due to a vehicle being sold were not depleting their locations or marking their serial #'s as sold.

Sales Orders

• Fixed: (case 11363) an issue where selling standard parts with a vehicle might not update the status of the parts to S.
• Fixed: (case 11251) an issue where doing a location-grouped search then sending a serialized part to a SO would add duplicate items to the invoice. It will now also correctly pop up and ask the user which serial # they wish to add, which is important for situations where there are multiple serials at a location.
• Fixed: (case 11512) an issue where the adjustment type dropdown would show as empty when the user selected the adjustment type on a saved, finalized invoice. In some circumstances, this was causing issues on save.

Vehicles

• Fixed: (case 11309) an issue where clicking the new cost button might do noting on windows 8.

Release 6.0

Customer

• Fixed: an issue where the user wouldn't be able to delete payment lines for $0 with no invoice association. It was possible to create these but they couldn't be deleted.
• Performance: when a payment is edited, no query is executed anymore for allocations that were not modified. This makes saving large payments on slow connections much faster.

Crystal Reports Extension

• Changed: most of the printing code has been changed to pass reports around in a way that should avoid any issues where a report might get cleaned up before the printing thread used it.
• Fixed: several possible crashes and hangs that could be caused by printing lots of reports very quickly.
• Fixed: if the user launches many print jobs that are waiting to complete, ITrack will now show the correct number of processes waiting to complete if the user tries to close ITrack before the prints have successfully begun.
• Changed: (Case 10612) if the user prints a report with 'advanced options', the printer dialog that pops up now has a quantity field on it, which will be used to override the number of copies to print.

Common Resources

• Fixed: in some circumstances, the thread dialog would crash when running a query (or chunked query) that had an error. This was because launching the error reporting dialog in the thread was colliding with the main UI thread somehow. This is resolved by sending a threaded message up to the main application to show the error at the next opportunity.

Database

• Added: 2 new options to the part modification column list, one for the total cost associated with a vehicle, and another for the vehicle cost that has been allocated (or consumed). This allows users to view more accurate costs when sending whole units to the part modification screen.
• Changed: several database functions have been modified to no longer use a view. This is because some database versions are very slow when views are used within functions.
• Changed: fmovedocument_allocations function to make it compatible with the AU tokenizer.
• Fixed: Re-releasing the "Serial #" search module due to an error in the previous release's query
• Added: a fix that should ensure all databases have the Discount, Credit, and Interest adjustment types set to balance adjustments, not subtotal adjustments.
• Added: (Case 10474) A new log that should catch when documents change inventory quantity. This will record the before and after quantity and the documents that caused the change.
• Added: the necessary queries for creating and populating the ebayconditions tables
• Changed: the messagetype column in the message table has been changed to an enum to help mimimize the size and increase the speed of any indices on the field.
• Added: (Case 10518) The FIFO system now properly handles Sales Order re-opens by removing the documents allocations and freeing the inventory source.
• Added: (Case 10518) The FIFO system now treats returns differently. The system will now record the return as a negative allocation and record the credited document, whereas before it would simply delete credit allocations.
• Fixed an issue where a database error was occuring when a part's quantity was changed manually
• Changed: deliverylinehistory.userid is now NULL-able. This is because these records can no be created automatically by the database outside of ITrack.
• Added: (case 9363) recursion protection to all triggers on deliverylinehistory that call frefreshdocument_delivered. This is because, in the case of auto-picking, that function can alter the deliverylinehistory table, causing recursion.
• Added: (case 9363) frefreshdocument_delivered can now create deliverylinehistory records for all unpicked quantity on auto-pick documents. This will help users see who saved a document with auto-picking turned on (and when). All such pick history is created with an empty location, which shouldn't matter because auto-picking doesn't consider these records to count how many have been picked.
• Added: (case 9363) recursion protection to frefreshdocument_delivered because it can insert deliverylinehistory records, which can cause triggers to fire that would call the function again.
• Fixed: (Case 10867) An issue where a database error could occur when there are multiple items on a Sales Order pulling from the same picking location. This had to do with the inventoryid and inventorystoreid not being considered in the calculation of nMaxMoveQuantity.
• Added: the event that optimizes all tables now specifies the database name to avoid any confusion.
• Added: (case 326) tables for handling the new transaction list.
• Added: rank column to documentsearchfilter for ordering.
• Fixed: (case 11123) previously, serialized inventory would only be moved to a destination location if the source location of the move matched the current serial location. Now, this is only enforced if the destination location is Variance. This means that whenever a serial is moved (or found), the serial will be moved, but a serial will only be 'lost' (moved to variance) if it hasn't also been found.
• Added: there is now a category and rank column for both documentsearchfilter and documentsearchfield. These will help us categorize and order the filters and fields on the screen.
• Added: support for filters to have a documentsearchjoinid (optional).
• Fixed: (case 11099) an issue where finalizing, picking and moving all at the same time would move inventory when it shouldn't had.
• Added: (Case 11059) Fixer query to Update.sql to remedy bad logdiscreteinventorymove handling in fmoveinventorywithallocationspost_execute.
• Added: a new permission, which controls whether the user can open the new transaction list screen "Transaction List"->"Open Screen". Everyone who can perform part searches will automatically be granted this permission.
• Added: a new permission, which controls whether the user is allowed to edit/overwrite/delete saved searches created by another user.
• Added: documentsearchsource records now have a defaultaggregatefield, which is the name of an entry in the documentsearchfield table that the totals page will sum up by default.
• Added: documentsearchfield now has a fieldtype column. A fieldtype of Key specifies that a field will always be returned when that document is selected (for lookup and unique document purposes). A fieldtype of singlular means that those values are 1 to 1 with a document and must be aggregated only for unique document keys. A field type of Multiple represents a one to many relationship, which means we can simply add up rows in the results.
• Changed: the permission to open the transaction list now defaults to whether the user had permission to run advanced reports instead of users that could perform inventory searches.
• Fixed: (case 11385) an issue where the query to create fquantityonorderon_document had an error in it.

Ebay Extension

• Added: Expanded TurboLister export information.
• Added: a config page for settings
• Added: a default ebay customer field that will be used when sending auctions to invoices when the email of the buyer isn't in the customer table
• Added: product specific support for the customer tables and the Customer List Screens
• Added: Send to Invoice now works for enterprise thanks to above
• Fixed: a typo with motorcycle default category
• Moved: Category map things to config tab
• Changed: messages to use the right name for the ebay extension
• Added: Users can now choose how pictures are exported via the Config tab
• Added: A warning is now thrown if there is no matching customer and no default customer for an auction being sent to incoice
• Added: small fix for an SQL error that would be thrown if no ebayaccounts are registered with itrack
• Added: Updated some objects to be ready for shipping options
• Added: Direct to ebay is now functional
• Added: config tab now has defaults for required listing information
• Added: edit and template dialogs now have shipping information.
• Fixed: a crash on direct export to ebay
• Fixed: Account edit now populates on first use
• Fixed: a bug where Shipping Service Options and Payment Methods and Return Policy Options didn't get filled in automatically on EE Ebay listings
• Added: zip code to the query so that zip code will be automatically populated
• Fixed: a bug where items where being cleared from the list but not from the ToList list behind the scenes causing items to be relisted
• Fixed: a bug where sending to invoice wasn't calling the correct setting to ask for the default customer
• Fixed: a bug where the default customer edit won't clear if its passed an empty string (this happens sometimes)

ITrack Online

• Added: a message specific to ebay so that we know when the user is done filling out their account info

Login

• Added: a way for extensions that are shared between products to check some permissions. Specifically, this should allow the transaction list screen to properly check user permissions.
• Added: a way for extensions that are shared between products to get user names. This allows the transaction list screen to show user information.

Master

• Added: handling for a new registered window message, WMREPORTHEAP_ERROR. This message takes an ITErrorReport* that was declared on the heap and launches an error report dialog for it. This is mostly so that threads without UI handling can report errors without causing thread collisions on the main UI thread. To use this, just copy an error onto the heap and call PostMessage to send the message to master.

Part Modification

• Fixed: many possible crashes that could happen if custom columns were created that do not match the name of any columns in the inventory table (and no associated lookup was stored in inventorysettingjoin).

Parts

• Added: (case 10974) if the user adds or modifies a location on the parts screen, the hold quantity is now refreshed. This fixes an issue where switching a location might leave the hold quantity from the previous location. Now the hold quantity should match the new location name.

Purchase Orders

• Fixed: an issue where the "minus" icon wasn't showing up correctly in the returns dialog.
• Fixed: (case 10409) POs should now load the correct vendor catalog record when there are multiple options to choose from and the PO is to the default purchase vendor.

Sales Orders

• Added: handling for ebay auctions
• Fixed: an issue where, if the user attempted to load a new SO when the existing SO was modified and they hit "Cancel" on the save dialog, the subtotals on the screen would not update again until the screen was closed and reopened.
• Fixed: an issue where sending an item to invoice from the ebay screen might not work right if there were already items on the screen. Also, quantity and currency are formatted correctly in this case.

Search:

• Fixed: (case 8619) the search HTP.net button now links up to the year range, category and keyword functionality of HTP.net searches. The base URL for HTP is no longer stored in the ini file, it is now a global database setting.
• Removed: the car-part search button because it relies on a separate executable that is not deployed with ITrack Enterprise and auto interchange, which is rarely present.

Settings

• Changed: a couple modifications to support an upcoming change to the printing framework.
• Added: the edit->options->reports page now loads the valid list of 'printer types' in the printer type dropdown from the list of all types in use on all reports in the database.
• Added: an external function handler for "ViewDynamicObjectDetail", which is designed to open the appropriate object on the appropriate screen, and is useful for 'dynamic' screens that don't know about how to open objects.

Transaction List

• Added: (case 326) This is a new screen for performing searches against documents in the software. The user can search, save/load old searches, export/print results, and group summary data dynamically. In order to use this screen, the user must have permission.

ITMySQLConnection

• Changed: the maximum packet size used by ITMySQLBlob is now capped at 1MB. This is to attempt to battle the out of memory issues some users have received.

Warehouse Management

• Fixed: an issue where changing the location on the manual count page with the mouse might cause the search to be run twice if any pop-ups appeared.