Defect Resolution Log

Resolved

ECOMMR-8011 – Account Sync Corrected Between Spruce and Spruce eCommerce Portal. Some customer accounts were not appearing in the Spruce eCommerce portal due to a synchronization failure between the application’s back-end system and the customer-facing portal. This prevented customers from accessing their account information online. We corrected the synchronization logic to ensure that all active customer accounts properly sync from the application to the online storefront. The data flow has been restored and verified.

LBMHR-354 – Complete Signature Captures Now Display for M400 Devices.
When you capture a signature on an M400 payment device, you expect the system to display the signature fully when the payment is processed. While the signatures printed correctly on documents, the on-screen display was incomplete. We have implemented smart signature scaling logic that automatically detects signature sizes and adjusts the display in Point of Sale accordingly to prevent this issue.

LBMHR-1575 – Using Inventory Lookup in Point of Sale Works Better Now.
In Point of Sale, when searching for an item in any Point of Sale area by right-clicking the Item field to use Inventory Lookup, if you typed search text in the Filter Description field without first selecting a Group/Section, the application often closed suddenly. When you selected a Group/Section first, the search worked, but the results reflected the entries in that group/section only. We updated the process to allow you to complete the search successfully regardless of whether a Group/Section has been chosen. This ensures that you can search for inventory items across all available groups and sections to find the entered data as expected.

LBMHR-2120 – Air Miles Rewards Now Calculated Correctly for Tax-Included Payments.
When processing payments on charge accounts with Air Miles rewards enabled, the system was calculating tax for these payments in some tax-included regions incorrectly. When the payment amount already included tax, the system treated the payment as if tax still needed to be added on top. This defect affected any business in a region/tax scenario with tax-inclusive payments. This resulted in:

• Inflated tax amounts displayed in the Air Miles dialog box

• Customers received fewer Air Miles rewards than they should have earned

We corrected this issue by updating the tax calculation process to ensure the correct tax basis is used to calculate Air Miles rewards from account payments.

LBMHR-2196 – Open Charge Credits Display Correctly in Spruce eCommerce.
In the EvolutionX system, open charge credits displayed incorrectly with a Paid status before they were applied to invoices. This caused confusion about outstanding balances and made it difficult to identify which credits were still available. To resolve this issue, we updated the system logic to accurately reflect credit status. Posted credits now show as Paid, while open or partially applied credits correctly display as Unpaid until they're fully applied to invoices.

LBMHR-2612 – Unexpected Database Error During Point of Sale Transaction Resolved. Customers reported that during some Point of Sale transactions, the message, Unexpected Database Error (The transaction is either not associated with the current connection or has been completed.) appeared and the application closed suddenly. Despite attempts to retry the transaction as prompted, the system indicated it had already completed it, so the retry was unsuccessful. We updated the application to properly handle completed database transactions and prevent retry prompts from appearing when they cannot succeed. We also improved the error-recovery processes to eliminate the loop that caused repeated error messages.

LBMHR-2615 – Updates to the Total Report Correct Comparative/Trends Style Issues.
Previously, the Totals report displayed zero values when using the Comparative or Trends style with the default date selection. The report failed to parse the current year correctly, resulting in an invalid date (year 0026), and there was no corresponding sales data. Additionally, the date selection did not properly switch to Selected month when you chose the Comparative style. We corrected the date logic to properly display the year and fixed the date selection to default to the Selected month when you select the Comparative or Trends report styles. These changes ensure the report generates accurate MTD, PY MTD, and YTD comparative totals.

LBMHR-2617 – Daily Sales Report Tax Totals Issue Corrected.
We corrected an issue we found that caused the Daily Sales Report to merge tax totals from all branches into a single, inflated figure -- even if you selected one branch. This occurred because a recent fix for clothing-tax duplication inadvertently omitted the branch-filtering logic in the report’s underlying database query. We updated the process to explicitly include a BranchID filter to ensure the SQL query confined the tax data to the selected branches only. This fix restores correct branch isolation while maintaining the previous fix for clothing-tax duplication. This change will correct the issue when you upgrade to the latest patch.

LBMHR-2661 – Local Launch Setting Now Visible for Remote Client-Supported Stations.
When a Remote Client station connects to the server, the server runs a lookup to retrieve the station’s branch settings. At the time this defect was reported, the Local Launch setting was not returned during this lookup process, meaning Remote Client had no way to know whether Local Launch was enabled for a given branch. We updated the database procedure to also retrieve the station’s Local Launch branch settings with the existing settings, which resolves this problem. If a branch hasn't configured this setting, the station defaults to off (false), rather than causing an error.

LBMHR-2711 – Bank Card Process Permission Issues Resolved.
We discovered that when the Restrict Manual Bank Card Entry security setting was enabled in User permissions, the application incorrectly disabled both Manual Card Entry and the Card Not Present payment options at Point of Sale. We corrected the security logic so that restricting manual entry no longer affects these settings, which are particularly required to process phone orders from clients.

LBMHR-2719 – Performance Issues Associated with Price Updates Corrected.
During the automated price update process, the system was experiencing significant performance slowdowns and database blocking. We found that the database queries responsible for cleaning up processed price updates were using an inefficient search pattern, particularly when the system needed to delete records from the Price Updates table after applying changes. We updated the system's price record search to use a faster, more direct method, improving performance.

LBMHR-2729 – Resolved: Document Issue that Prevented Lengths for Hardwood Tally Items.
A customer reported a defect that prevented the dimension information of Hardwood Tally items from appearing on Purchase Orders, Inventory Receipts, Sales Invoices, and Order documents. This prevented vendors and customers from receiving complete physical specifications for hardwood tally items on their paperwork. We corrected this issue to ensure that Hardwood Tally item entries display the full dimension string (depth × width × length) across all document types. The fix has been incorporated into the document-generation logic to prevent similar errors in the future.

LBMHR-2744 – Image List Images Displaying in Point of Sale Again.
When working in the Point of Sale area (and right-clicking the Item list to review and display Image List tiles), the header tile images were not displaying, although individual item images appeared correctly when you expanded the lists. When we investigated this issue, we found several problems that prevented the images from displaying correctly, and we created a more unified process for item display to address this problem. As a result, we corrected the image assignment process to use the scaled image variable to ensure proper flag updates, added new control logic to repaint the image when parent panels are resized or modified, and added comprehensive testing to prevent similar display issues from recurring.

LBMHR-2745 – Corrected: Notification Queue Printing Issues.
Some users encountered issues when attempting to print messages from the Notification Queue (Main Menu > Messages):

• Print jobs were reported as failing even when they succeeded using Remote Client

• Printer list displayed incorrect printers (showing server printers, not client printers)

• Print-to-PDF and other virtual printers produced corrupt or empty files

We corrected these printing issues for both local and Remote Client-users. The system now correctly displays client printers in the printer selection dialog box and properly renders the requested output for both physical and virtual printers (including Print-to-PDF). Print jobs no longer show false failure messages.

LBMHR-2854 - Account and Item Maintenance Memory Leak Issues Resolved.
Some customers reported slowdowns and unexpected application closures after repeatedly opening and closing Account Maintenance (POS > Database > Account) and Item Maintenance forms throughout the day. We found that technical object handles were not being properly released when users closed these forms, causing the slowdown and closure issues.

As of the latest release, we have enabled three new memory-leak corrections that do not require manual database scripts. To benefit from this fix:

• Upgrade your application to the latest release, which contains the fix

• Restart the application after the update is applied.

The memory-leak mitigations take effect after you restart the application.

Contact your System Administrator if your performance issues persist after the restart.

LBMHR-2761 – Update Prevents EDI-Based Price Update Lock Issue.
Customers reported that when processing large EDI-based price updates, some Point of Sale stations reported timeout errors that prevented sales from completing. This affected credit card processing and other payment methods most. After investigating, we found that the system was locking the inventory database to prevent overwriting item prices during transactions. We have improved this process to shorten the lock window to prevent transaction processing issues. However, we recommend scheduling large EDI price update processes outside of business hours to avoid such interruptions.

LBMHR-2854 - Account and Item Maintenance Memory Leak Issues Resolved.
Some customers reported slowdowns and unexpected application closures after repeatedly opening and closing Account Maintenance (POS > Database > Account) and Item Maintenance forms throughout the day. We found that technical object handles were not being properly released when users closed these forms, causing the slowdown and closure issues.

As of the latest release, we have enabled three new memory-leak corrections that do not require manual database scripts. To benefit from this fix:

• Upgrade your application to the latest release, which contains the fix

• Restart the application after the update is applied.

The memory-leak mitigations take effect only after you restart the application.

Contact your System Administrator if your performance issues persist after the restart.

LBMHR-2936 – Complex Orders with Currency Rounding Issue Processing Normally Again.
When processing a special item order with a payment adjustment and delivery charges, and refunding a penny difference, a customer reported that the application closed with an error message. The root cause was a calculation issue related to currency rounding during the payment process, which we have resolved.

LBMHR-2949 – Overpaying an Order in Cash No Longer Causes Application Freeze.
An error occurred when a Cashier entered a cash overpayment on an order deposit in Point of Sale. After entering a cash amount higher than the balance due and completing the deposit, the system displayed the change-due screen with the message, Press Space Bar to Return. However, if the Cashier pressed the Space Bar, the application froze, leaving the Orders interface disabled and requiring the Cashier to force close and restart it. We corrected the logic to ensure that the application re-enables the Orders form after the change-due message is dismissed. No workarounds are required after this update.

LBMHR-3126 – Items Display in Folders (F4) tab for Inventory Adjustments Again.
After a recent update, when you selected the Folders (F4) key during an Inventory Adjustment, item details no longer displayed, and some of the other tabs appeared blank too. We restored the missing logic that displays these details, so the Folder tab details display correctly for this process.

LBMHR-808 – Large EDI Processes no longer Causing POS and Inventory Locks.
When processing large Do It Best EDI processes or running a PO Build, some POS terminals and inventory forms froze across multiple branches and caused timeouts until the inventory receive or build finished. We corrected this issue by managing the update of the inventory pricing information in a way that does not affect these processes. We still recommend that you schedule large EDI processes outside of normal business hours (before or after the store closes) to minimize the effects of these important transmissions.

LBMHR-1952, LBMHR-2761 – Managing Register Errors Caused by Database Locks During Price Updates. When running a large vendor EDI Price Update during the business day, the system could lock up inventory records for a thousand or more items at a time. When this happened, Cashiers received Database Locked errors, preventing them from completing sales. The bigger the price update, the longer the lockout. We updated this process to break large price updates into smaller batches and release the item database lock between each batch, rather than holding them for the entire process. This dramatically shortens the window during which the register is affected. We recommend running this kind of large price update during off-peak hours to prevent database locks from impacting the checkout line.

LBMHR-2761 – Update Prevents EDI-Based Price Update Lock Issue.
Customers reported that when processing large EDI-based price updates, some Point of Sale stations reported timeout errors that prevented sales from completing. This affected credit card processing and other payment methods most. After investigating, we found that the system was locking the inventory database to prevent overwriting item prices during transactions. We have improved this process to shorten the lock window to prevent transaction processing issues. However, we recommend scheduling large EDI price update processes outside of business hours to avoid such interruptions.

LBMHR-3110 – Corrected: Identifier Labels Not Printing from Purchasing Receipts.
Some stores using a Dymo label printer found that the Document Identifier label (the barcode/receipt ID sticker) stopped printing automatically when they finished processing a receipt (Purchasing > Receipts > Process (F12) > Finish (F12)). The form displayed the message: Processing Complete, but no label printed. We corrected this process to ensure the purchasing receipt identifier label prints as expected.

LBMHR-3126 – Items Display in Folders (F4) tab for Inventory Adjustments Again.
After a recent update, when you selected the Folders (F4) key during an Inventory Adjustment, item details no longer displayed, and some of the other tabs appeared blank too. We restored the missing logic that displays these details, so the Folder tab details display correctly for this process.

LBMHR-3139 – Lost Sales shows Description and Valuation Item Details in POS.

In the past, when you reviewed the Lost Sales information for an inventory item in the Point of Sale data grid, the Description field and the fields in the Valuation box did not display these item details. Viewing this data required a workaround that was a frustrating extra step. We corrected this issue to ensure that all item details display properly when you look up the Lost Sales information for a selected item.

Lost Sales Form > Description and Valuation Fields Highlighted

LBMHR-3141 – Workstations Log Out Automatically Based on Inactivity Setting Again.
Some customers reported that workstations were not logging out automatically after a normal period of inactivity, even when that logout time was pre-configured. We corrected this issue. You can set this timeout period in the Inactivity Timeout field in the Security Options tab of the User ID Maintenance form.

LBMHR-551 – Item Records Updating Correctly when you Change Vendors.
When a store switched to a new EDI vendor (for example, moving from ACE to Do It Best), and downloaded a purchase order or invoice from that new vendor, the application was supposed to recognize that the item already existed in inventory by matching its UPC barcode that was stored in the item record. Using the UPC barcode, it could update the item record to use the new vendor's item number instead. The error occurred when the system began creating a duplicate SKU without a UPC barcode for the new vendor’s item, while leaving the UPC attached to the old item. This caused inventory clutter, mismatched barcodes, and confusion when receiving products from multiple vendors that carry the same items. The application now looks up the existing item by UPC during an EDI PO Update and adds the new vendor's item number to that item instead of creating a duplicate.

LBMHR-2635 – Update Resolves EOD Processing Issue with Finance Charges.
When someone posted an AR payment that applied to multiple Finance Charges at once (and the account had two or more outstanding Finance Charges), the system saved an inaccurate Finance Charge total, behind the scenes. This caused an End-of-Day (EOD) process failure, which prevented the books from balancing. We updated the Finance Charge calculation logic to ensure we apply the appropriate Finance Charge amount to each outstanding account balance and store it accurately for the EOD process calculation.

LBMHR-2820 – Opening SPEC Account Payment Documents Works Correctly Again.
When a customer made an account (ROA) payment on the SPEC portal and a user opened the payment document in the Document Viewer in the application, the application sometimes closed suddenly. This happened because the system mistakenly pulled in dozens of unrelated receipts and attempted to load them all simultaneously. We corrected this issue to ensure that you can open these documents safely.

LBMHR-2864 – Emailed PDFs are Readable Again.
Some customers reported that their customers were unable to open the invoice or statement PDFs sent through the application. It displayed correctly when you opened the PDF locally in the application, but not after it was emailed. The workaround was to save the document locally and send it manually, but it was a lot of work. After some investigation, we found that the process was adding an extra blank byte to the document, which caused this issue. We corrected this issue.

LBMHR-3049 – Promotional Item Updates Running More Efficiently Now.
When running a Promotional Item Update in the Vendor EDI area, some TrueValue customers reported that the application suddenly closed, displaying an Application Abort error. This was caused by the system taking too long to update the expected ship dates across all open purchase orders after loading the item promotion information, resulting in a timeout. We updated the logic to limit the expected ship date update to only the purchase orders and promo items that are affected by the uploaded promotion, rather than scanning all open POs across the system, which resolved the issue.

LBMHR-3143 – Adding New Items to Inventory Works Better for ACE Rewards Stores.
For multi-branch businesses that use ACE Rewards, we used to run a promotional setup process when you added a new ACE item. This caused the application to run several processes simultaneously, which resulted in a database deadlock. This sometimes prevented transactions at the workstation from completing or forced the application to close. We now run the promotion setup process after the item has been saved to prevent the deadlock. If a similar situation occurs in the future, we display a Try Again message to prevent the application from closing unexpectedly.

LBMHR-3206 – Preventing Large Do It Best POs From Locking Up POS Stations.
Some stores reported that when they processed large Do It Best purchase orders, the application sometimes locked up the Point of Sale workstations across all branches. We restructured this process to prevent the validation step from causing this lockup. We still recommend processing DIB POs during off-peak hours to prevent this type of issue.