12.3.9
Release Notes and Help topics can refer to changes, features, and fixes that your company may not yet have installed. Use Help and About to check your application version for comparison to the Help version. The current Help version is 12.15.35. When an update is installed, all changes up to that version are included even if your company "skipped" one or more prior updates.
It is possible for some changes, particularly fixes, to overlap more than one release. For example, an issue may be fixed independently in our production line (current release) as well as our beta or development lines. For this reason, you may see similar items that are also referenced in other notes.
Identifiers are now included with most items in the notes. These are used by our project tracking software, or source control, and are sometimes linked to support tickets. Identifiers prefixed with the letter "R" are requests, "D" are defects (fixes), and "B" or "E" stands for backlog items (enhancements or new development usually).
|
Note: To find individual release changes on this page, you can use the "find" function CTRL-F. Later notes for updates (stability) are also provided in separate topic(s) so that users can just view those changes. We provide links in the main "feature" notes to any stability notes topics. |
|
Data Grid Quantity Colors We have removed the change to display below minimum items in a brown color. No indication will be done for items less than minimum but above available. When completing an Installed Sale Contract, we now leave the ticket and invoice documents in an open document status. Orders are still marked as closed. Normally, when a ticket is invoiced, the document status would be left as "open." Some reports, Canadian Sales Tax by Invoice, specifically, were excluding "closed" documents, so this caused the installed sales invoices to be excluded. The report has also been changed so that it no longer excludes "closed" documents. Verifone Point would get an exception if the invoice total was changed before the item display was shown on the device. Some transactions like charge sale signatures would not show up on the device unless a reset was clicked on the process form. Changed the pad to the item display to show as soon as the process form is brought up in case adjustments are added before items. |
|
The "Notes" text area was only allowing six (6) lines of 30-characters (180 total), but was capable of allowing up to 256-characters. Additional text can now be entered. No scroll bar is provided, please use the arrow keys to view additional lines. Vendor EDI AP Receive: Updated logic for when an invoice is received that already exists in the system If the vendor invoice that matches in the system is either older than the PO that matches the invoice or the vendor invoice is older than a year, instead of matching against that invoice it will add a new one with the same invoice number. This allows vendors to re-use invoice numbers and still have them be generated in the system. |
|
The indicator on the Alerts report when using the MTD GM alert filter was overlapping the percentage. This has been corrected. Selections made for comparisons between the catalog and inventory were not being properly interpreted causing any query to fail. We now check to make sure at least one selection has been made. If not, a message that "no fields were selected" will be displayed. There is an issue with the "unit cost" comparison which is returning suggested list from inventory and retail price from the catalog instead of costs. This issue will be corrected with the next release. Unit Cost is only available for the True Value catalog. We now allow updating one location at a time instead of requiring that all locations to be updated together. The checks for merge from items no longer retrieve all records for Tickets, Orders, Quotes, Purchase Orders, and Transfers for better efficiency. Now, we just retrieve a count of documents containing all the necessary checks to save memory. Changes to allow for printing bar-coded unit labels for new single item unit tally SKUs. Prior to the change, the data grid would only bring in the item one time when doing an Import (F2), Receipt. Since the same item can exist multiple times on the same receipt document (with different unit tags), it needed to work a bit differently. Due to the length of the tag ID, it will print the 128B format. Defaults to a quantity of one label per unit. As part of on-going development, a new context menu item has been added to the Transfers transaction in Inventory for use by a new WMS (Warehouse Management System) feature we are developing. The selection of locations in Transfers was modified to filter input based on the item selected in addition to the branch ID. Added a single quote (tick) mark after the lengths in the tally comments. Coding changes were made to isolate unit item tally code in the Purchasing, Receipts and Point of Sale areas unless the parameter for unit item tally has been enabled. |
|
"MfgMarket" type Adjustments were not being saved when associated with a work order (the adjustment total was correctly calculated). This has been corrected. When an item being received is associated with a work order, the work order totals need to be recalculated. While the code was recalculating totals based on the visible rows, the material list (hidden row) totals should have first been recalculated. |
|
Close Receipts (Utility) The totals text-areas listed in the upper right-hand area of the form were not read-only and should have been. Cosmetic change only. New Open Receipts report to provide results similar to the Close Receipts utility. Vendor selection controls were added, and we have made the branch select panel not visible (branch selection is not enabled at this time). Since the utility lists receipts by branch, and the report is not, if you compare the two (2) or want to report on specific branches, set the "sort by" to branch when running (with subtotals). This will provide a sub-total for each branch location's open receipts. |
|
Journal Entry and Posting The check for journal cycle against the current open cycle was not working for companies using non-standard GL. Due to this, it was possible to create and post journals for closed cycles. Initialize Balances Utility The cycle name and year text-areas were not read-only. Cosmetic change only. Users could not choose one journal type, we were processing all types regardless of selections. Also, the report would not save journal selections with a space in the name. |
|
As a part of on-going development, we have added new "tax control" parameters for sales tax reporting in Puerto Rico. Added system parameter SPHostedViewerTop for use with cloud-hosted customers who have issues with the document viewer appearing behind other windows. |
|
When errors occur during Email, Fax and Mobile background processing, we are now recording those errors in the UniversalLog table instead of the Windows Event Viewer. This is to help with error logging in the hosted environment particularly. In those cases, Windows service users don't have permissions to write to the Windows event log and it also reduces the number of systems using the event log (which can make it difficult to find a particular installation's errors). Remote Desktop App Connections This release includes code for troubleshooting and potentially fixing a problem occurring at certain cloud hosted customers over a remote app connection where an input would appear active, but not allow keyboard input. |
|
Sales Tax Reports (Canada) We have changed the selection criteria of invoices to only include documents with a status 0 or 1 (open and closed). This is consistent with how the US code works. |