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.

ECOMMR-8138 – Consolidated Contract Pricing Now Displays on the Website.
We investigated an issue where the contract pricing in the application was not displaying correctly on the Spruce eCommerce website. We found that our pricing calculation process didn’t include consolidated contract pricing and was only looking for specific job numbers. Since consolidated contracts use a special identifier that wasn't being considered, we updated the pricing calculation to apply your consolidated contract prices correctly. In our testing, we found that this now works as expected.

ECOMMR-8698 – Accounts Appearing Correctly on Storefront After Data Sync Process. (SPEC Only) Some customer accounts created in the application did not appear on the Storefront portal after the synchronization process was complete. We improved the database query process that retrieved new accounts and removed a problematic database hint that prevented their successful transfer. All accounts are now reliably retrieved during the data synchronization process.

LBMHR-32, LBMHR-2766 – Issue Resolved: Material Vendor and Pre-Receipt Vendor are different.
When a Direct Ship purchase order includes an adjustment (adder) that is billed to a different vendor from the material vendor (for example, freight is charged to a separate freight vendor), processing the purchase order often resulted in the error:

• Material Vendor and Pre-Receipt Vendor are different.

This prevented the invoice from being paid. After some investigation, we found that the non-material vendor record was locked, which prevented the Purchase Order from validating. We corrected this issue to ensure that you can process this transaction successfully. As a temporary workaround, you can code these adder invoices to a holding liability account. As of this release, you'll be able to process Direct Ship adder invoices normally through Payables Billing Entry with no additional steps.

LBMHR-303 – GL Inventory Reconciliation Report Alignment Issues Resolved.
In the past, some GL Inventory Reconciliation Reports displayed totals that did not align with GL Balance Sheet totals for the same period. The report incorrectly included non-inventory accounts (such as those reflecting labor costs) and showed doubled amounts when the branch mapping configurations were inconsistent with the Chart of Accounts structure. We resolved this to ensure accurate reporting when the System Journal mapping is configured properly.

Note: If the Branch check box is enabled for inventory accounts in System Journal setup (such as Receiving journal sequence #1), corresponding branch-level accounts must exist in the Chart of Accounts.

We recommend that you review your System Journal setup under General Ledger > Setup > System Journals. For inventory accounts that either:

• Disable the Branch check box if branch accounts do not exist, or

• Create branch department accounts that match your inventory structure

This alignment ensures that the GL Inventory Reconciliation Report reflects your business’s accurate totals.

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-1518 – Installed Sales Currency Rounding Issue Corrected.
When completing Installed Sales contracts with third-party labor costs that included cents (such as $50.25), we discovered a small rounding discrepancy that remained in the General Ledger's Deposits account. This prevented the General Ledger account from balancing properly and required manual adjustments. We corrected the rounding logic used when processing third-party labor adjustments to handle decimal values properly. This ensured that the GL account balances automatically without leaving these discrepancies.

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-1799 – Delivery Notes in POS Process Tab No Longer Causing Closure.
Some users experienced unexpected software closures when adding or editing delivery notes during the Order process. This occurred on some workstations without displaying an error message, preventing the update of delivery details. The issue occurred when the system attempted to update the text field and the scroll bar at the same time. We corrected this issue to ensure the successful addition of delivery notes during the Order process.

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-2206 – Negative Final Billing Amount for Installed Contracts Resolved. 
A customer reported a defect that allowed users to enter billing amounts, resulting in a negative final billing balance for installed sales contracts. The issue arose in two scenarios where customer orders included deposits linked to the installed contract. Because this deposit-linked workflow does not automatically create a "Billed" line item, users entered the recurring bill amounts manually. Without system-level guardrails this resulted in:

• Recurring billing amounts that exceeded the total contract amount or the remaining billing balance.

• Reducing the contract amount to a value below the remaining-to-bill balance, creating a scenario where more was owed than the contract was worth.

Both conditions produced installed contracts with invalid negative final billing amounts. After the application created a negative balance, it required manual correction. We resolved this issue by adding validation rules on the Installed Sales > Billing Tab that the application checks automatically before an installed sale can be marked as complete. These rules include:

• Validating the Billing Amount.
  The application checks whether a recurring billing amount exceeds the contract amount or the remaining-to-bill balance. If either condition is true, the system displays an error to prevent the user from saving the entry.

• Validating the Contract Amount.
  The application checks whether a user is attempting to reduce the contract amount to a value below the current remaining-to-bill balance. If so, the system displays an error that prevents the change.

• Ensuring the Final Billing Amount is not Negative.
  When a user tries to complete the installed sale process, they cannot proceed if the final billing amount is negative.

We implemented these validations as new task list error messages, which are now built into the Installed Sales Billing processes. These guardrails are automatic and require no setup. If you encounter a validation error, please review the recurring billing and contract amount fields to ensure they are consistent with any deposits already applied from linked customer orders. No workflow changes are needed beyond responding to these new on-screen error messages.

LBMHR-2574: Memory Leak in Manufacturing Area Resolved.
A customer using the Manufacturing feature reported issues when processing quotes and orders: the application did not release memory after completing these transactions. This caused the application to slow down during the day and even required a reboot at times. We resolved this issue to improve event handling, clean up enhanced memory issues, and added automated unit tests to catch similar issues that could occur in the future. No changes to your daily process are required.

LBMHR-2597 - Recurring Bills Use the Vendor's Default VAT Code Automatically.
Before the fix, when you used Copy Recurring Bills utility to create accounts payable invoices, the new invoices did not pick up the default VAT code set on the vendor record in Vendor Maintenance. Instead, they used the first VAT code in the list in alphabetical order. If the first code was EXEMPT, the application created the invoice without a VAT code, which meant the transaction could be left off your HMRC VAT return. We now ensure that this utility assigns the VAT code the same way as it does in manual Billing Entry, using the vendor's default VAT code. Invoices created from recurring bills will carry the correct VAT code and report accurately on the VAT return. If you previously created a duplicate VAT code to force correct ordering, that workaround is no longer needed.

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-3072 – Selecting Multiple Branches for Installed Sales Report Working Correctly.
When running the Installed Sales report for an account with a designated report/POS branch, selecting multiple branches caused the Installed Sales report to return no data. We corrected the internal logic error that caused this report to fail, and it now handles selecting multiple branches 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.

LBMH21-554 - Delivery Notes in the Ticket Process No Longer Causing Closure.
Some users experienced unexpected software closures when adding or editing delivery notes during the Open Ticket (Advice Notes) process. This occurred on some workstations without displaying an error message, preventing updates to delivery details. We corrected this issue to ensure that you can add and modify delivery notes successfully during the Ticket 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-2408 – Vendor Adder Billing Link Issue Related to EasyAP Process Resolved.
When using Easy AP (the third-party import invoice tool) to process invoices tied to purchase orders with vendor adders, the system failed to properly mark those adders as billed. As a result, Billing Entry (Payables) still showed adder charges as unbilled, even after they had been processed, so the received dollar amounts on imported bills didn't match what was received. We traced the issue to a sequence-numbering error. The process miscounted adder line numbers (starting at -1 instead of 0), which prevented the identification of matching rows; this left the billing linkage unset. We corrected this issue to ensure that we parse adder sequences accurately and record received amounts correctly. We confirmed that this resolution matches the behavior of the manual Billing Entry process. After the fix is deployed, you may want to perform a one-time clean-up of any previously imported bills with broken adder links. The Support team can assist you in identifying and correcting those records.

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-3092 – Email Transmission Issue Corrected.
Some beta customers reported that their emails were not transmitting successfully after upgrading to version 33 for testing. We have corrected this issue.

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-1911: Installed Sales Billing Issues Resolved.
In the past, when an associate used the Percent option for Installed Sales billing on the Billing tab, Spruce could calculate bill amounts to fractions of a cent, like $2,216.778, even though the form may only show normal dollars and cents. When those bills were posted, Accounts Receivable could end up with small fractional open credit that associates could not apply or clear; this required a manual data fix. We have corrected this issue by rounding Installed Sales bill schedules correctly to whole cents when you save a percentage billing.

Additionally, when a store associate tried to mark an Installed Sale as Complete on a contract using the Scheduled Invoice billing method, the system threw a Task List Error and would not allow them to close out the job — no matter what they tried. We corrected this issue so you can complete the scheduled invoice billing without any errors.

LBMHR-2750 – Bulk Inventory Import in UK Systems Working Correctly Again.
In the UK, VAT-enabled systems using the Bulk Inventory Import wizard (Inventory > Database > Item > F2 Import > Wizard > Update Inventory) to update prices for fixed-price items (PrcType P) failed silently, retaining the old prices rather than applying the imported values. Other pricing types (such as Markup, Margin, etc.) updated correctly. This was apparently due to a tax-context calculation that overwrote the imported fixed prices with the old database price during the wizard's validation step. Interimly, customers used the Level Maintenance feature to update prices of this type, rather than the Bulk Import Wizard for fixed-price items. We updated this logic to ensure that the system correctly keeps the imported fixed prices during the Bulk Update process and no longer overwrites them with the old values.

LBMHR-2840 – Update to Installed Sales Ensure Accurate Margin / Profit Totals.
On the Installed Sales form > Analysis tab, when a Labor SKU was set as non-stocked, the application counted the price twice — once under Materials and again under Labor. This overstated both Estimated and Actual totals, making margin/profit percentages inaccurate. We corrected the calculation logic to ensure that non-stocked labor items are now recognized consistently and are excluded from Materials totals. This applies to both Estimated and Actual totals in the Analysis tab. We added tests to confirm the numbers stay accurate going forward.

LBMHR-3065 – Reversing/Closing Vendor Bills No Longer Uses the Branch Logic Incorrectly.
When reversing and closing an AP credit invoice (vendor bill), the system incorrectly blocked the action, showing the following error message:

• Original vendor invoice was processed in a different branch.

Upon investigation, we found that this error message was inaccurate, as the user was attempting to reverse the invoice from the original branch. We corrected the branch-validation logic to ensure it properly recognizes when the branch’s vendor bill matches your current session, so the reverse and close process works as expected. The new logic only applies to the cross-branch check process when the branches genuinely differ. We added tests to prevent this error from recurring.

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-2115 – Billing Error No Longer Impacting Direct Ship PO Transactions.
Some customers reported that when they tried to process a Direct Ship Purchase Order in the Billing Entry form, the system closed suddenly when they attempted to generate the invoice. We corrected this issue. You should be able to process Direct Ship POs successfully and without errors through Billing Entry.

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-3200 – Billing Error Due to Advanced Payments on Installed Sales Contracts Resolved. When a customer with an Installed Sales contract made an advance payment (paid more than was due), the system incorrectly blocked the next scheduled bill. We corrected this process to ensure the application properly applies advance payments before calculating the next bill amount.

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.

LBMHR-3213 – EasyAP Adder Charges Handled Correctly Now.
When you imported an EasyAP bill from a receipt that included Adder charges (such as freight or handling fees), the application did not include those Adder charges in the Process AP Batch process. Because these adders were never marked as billed, the same charges remained available for billing again, which risked duplicate charges on future invoices. After some research, we found that EasyAP labeled the adders differently than the billing batch screens expected, which prevented the application from matching them. We updated the import process to ensure that the EasyAP import and Process AP Batch process language is aligned. This resolved the issue.