12.10.22
The following 12.10.22 stability notes are additional changes made after the parent release 12.10.6 and prior stability releases. For a summary of all changes, please see the 12.10.6 summary notes. Notes are listed in order of our project tracking numbers.
D-41934 - Point of Sale / Utility / Order Merge
Previous correction would only work if there was only one (1) job on the account. Multiple jobs would cause an error where the address fields on the new merged order would be blank. Corrected. (12.10.22)
D-42427 - Point of Sale / Reports / Invoices & Tickets
Quantity was not being included in the summarized details. (12.10.22)
D-42451 and D-42356 - Point of Sale / Random Length Tally Returns
When returning a random length tally (either a partial quantity return or full quantity return), the quantity in the grid reverts to the quantity on the original invoice. For example, if 200 were sold on the original invoice and then 60 were returned (by entering -60 were on the random tally form), after the user selected the original invoice on the item return form, the quantity in the grid reverted to +200. (12.10.22)
D-42453 - Point of Sale / Utilities / Item Returns
When Special Order goods were marked for resale from the utility and the user sets a new unit price, the code was setting only the suggested list price but not any of the item's price levels. Prices levels are now updated as well. (12.10.22)
D-42512 - Maintenance / Database / Devices - Remote Client - Deactivate
The call to the deauthorize web method is now wrapped in a Try/Catch to prevent exceptions from being thrown if SpruceWeb web services are not available. Instead, we now log the exception to the UniversalLog table with a log source of RmtClient. Previously this call would cause a "snap dump" exception if SpruceWeb was inaccessible. (12.10.22)
We re-factored the FTP routine to prevent database transaction locking. (12.10.22)
B-45653 - Receivables / Close Cycle - Scheduling Time
Changes were made to allow the run time to be set to other than the default time of 12:30 AM. Additional range of times allowed are 6:00 AM - 9:00 PM are now permitted. An issue was identified with the message that warns if a user attempts to set the time out of the supported range. This will be corrected with a future stability update. (12.10.22)
TFS-153039 & TFS-153037 - Receivables / Close Cycle
Message #2069 updated to "First Close Billing Cycle schedule date is within 20 days from the live date. Do you want to continue?" Also, removed check for five (5) days within the live date. (12.10.22)