Defect Resolution Log

This is a list of defect resolution changes we have made for Release 30, broken down by the versions below.

  • To view the list of major features for this release, select Major Features.

  • To learn more about using the new features in this release, see Release Details.

Closed30.0 Release

Resolved

ECOMMR-4312 – Closed Jobs No Longer Causing Delays in AccountDetails Requests.
A customer reported that when they had accounts with multiple closed jobs, there was a significant delay (sometimes resulting in time-outs) in retrieving account data when using an AccountDetails endpoint. We have updated this process to eliminate the retrieval of closed jobs on accounts that have these closed jobs, which has significantly improved performance.

LBMHR-487 – Resolved: Unit of Measure Issues when Using the Inventory Import Wizard.
A customer shared that when they used the Inventory Import Wizard, they were experiencing errors when importing items with some lumber/sheet dimensions. We have updated the import infrastructure to expand the item type options to include additional lumber, sheet goods, and hardware units of measure to prevent this issue.

LBMHR-700 – Updates to Billing Entry Recalculate the VAT from Receipts. (UK Only).
A UK business reported that when they processed a payable for some receipts, the application sometimes failed to calculate the VAT amount accurately or at all. In these cases, both the items and the vendor records had VAT codes assigned to them. We modified the application's calculation of VAT amounts for receipts to account for partial payments made originally. The application recalculates the VAT amount based on the remaining receipt values and displays a message indicating that the VAT amount may differ from the original calculation. If the application cannot make this calculation reliably, it will prompt the user to enter the VAT amount manually. Manual entry should occur significantly less often.

LBMHR-749 – Unit Cost Rounding Issue in Purchase Orders Updated.
We updated the unit cost calculation for Purchase Orders to use four-digit rounding rather than two. This four-digit decimal point change also displays in the Purchase Order documents Cost columns.

LBMHR-1027– Consolidated Purchase Order Allocation Issues Addressed.
When the Enable Consolidated PO Pending Transfers parameter is set, you can create consolidated purchase orders for more than one branch to save on the cost of an order. A customer noticed that when the application created a consolidated order for items of the same type but different units of measure, and a user manually adjusted the item quantities in the Purchase Order Entry form, the final item quantities were not always equal to the allocated quantities. This resulted in issues where the incorrect item quantities were delivered. We updated this process so that if a user modifies the item quantities for a consolidated purchase order and the allocated quantities do not match the original purchase order allocation, a warning message displays:

  • Over allocated quantities need to be adjusted.

The application highlights the line(s) in the grid that need(s) to be modified and prevents the PO Order from processing until the allocation quantities are correct.

LBMHR-1137 – Pricing Update Issue when Switching Items Corrected. (UK, Ex Tax Only)
A customer in the U.K. reported that they had the Auto Update UM Pricing feature disabled in their system. However, in Item Maintenance, when they searched for an item by Description, and looked up the pricing for the item, and then moved on to the next related item, the application applied the pricing from the first item to the second item in Branch > Pricing automatically. If they then processed (F12) that record, the application applied the new pricing to the second item, when it should not have. We have correct this error. If the Auto Update UM Pricing feature is disabled, changing the item UM no longer occurs when you move from item to item in Item Maintenance.

LBMHR-1139 – Online Orders/Quotes Submitted to Inc Tax Branches Process Correctly Now.
Some online orders submitted to branches with Inc Tax settings received the error messages OrderTotalError and TaxTotalMatchError. This was due to the parameter tax settings for ecommerce orders, which use a 0% tax rate by default. We now handle this type of transaction using the tax total that is supplied in the original online transaction, which is based on the branch’s excluded tax rate. This resolves the error and processes these transactions correctly. All future eCommerce orders and quotes will be imported with the excluded tax rates whether the branch is configured to use included taxes or not.

LBMHR-1355 – Finance Charges Do Not Add Up Error Resolved.
An ecommerce customer reported that when they submitted a CreatePaymentRequest, they saw a PaymentProcessingError that resulted in the message, Finance charges do not add up. While investigating, we discovered a coding error that was causing the issue, which we have since corrected.

LBMHR-1598 – To Improve Security, the Help > About Link is No Longer Live.
If you click Help > About, a box displays to show you the version information for the current instance of the application. This is useful for you to know what version of the software you are running. There has been a link in that box that accesses our ECI website, which discusses the application benefits and uses. For security reasons, you will still see this text in this box, and you can copy it into a browser URL field, but you cannot link directly to the website from the text.


LBMHR-1690 – Orgill Images Displaying in Catalog also Displaying in Item Maintenance Now.
Some customers noticed that when the Orgill process retrieved inventory updates including images, the images displayed in the Catalog list but not in Item Maintenance. We have updated this process to ensure that the images display in both forms.

LBMHR-1691 – Large Quote and Orders No Longer Result in Errors.
In the past, when you created a very large order or quote, there were times you received the message:

  • Error Creating Window Handle

In this case, the application was keeping too many forms open at the same time. This caused a memory issue that resulted in the error. We have updated the code to close the forms in a timelier way to prevent this issue.

LBMHR-1698 – EDI Process that Turns Off the Do It Best BOPIS Flag Working Correctly Again.
When you apply the DIB BOPIS Exclude flag to one or more items via the EDI process, the items should not display on the Do It Best BOPIS website. We have corrected the issue that prevented this process from working.

LBMHR-1737 – Copying External Text into Non-Stock Item Order Form Allows Fewer Characters.
A customer reported that when they were working within the Non-Stock Order form and they tried to paste text from an external site into the form, an error resulted that closed the application. To improve performance, we are now limiting the number of characters you can paste into the Non-Stocked Item Order form to 1088 characters. If you try to paste text longer than that into the form, the text is truncated (reduced) to the first 1088 characters, but it does not cause an error.

LBMHR-1769 – Progress Made in Resolving Out-of-Memory Issues.
A business reported that they were experiencing system slowness and out-of-memory issues while using multiple different areas of the software. We found that the system was keeping many of these windows open, even when the user was done with them. We are now closing those windows in a more timely manner, which is improving performance and preventing the out-of-memory issues from occurring.

LBMHR-1858 – Regression Issue Resolved: Processing AP Batch Invoice Issue.
A customer reported that when processing ENAP invoices using the AP Batch Process, an error occurred, causing the application to close. The application was misinterpreting the number of adjustments attached to a transaction, which caused the error. We have corrected this issue.

LBMHR-1943 - API Method Updated to Ensure If Paid By Amounts Match the Context.
A business reported that when their customer used the Ecommerce API to retrieve their statement, the If Paid By amount was different online than when the statement displayed in the application. Upon investigation, we found that the Ecommerce API method, CreatePDFDoc, was not applying the open credits correctly in the context of the request date. We have corrected this issue.

LBMHR-1946 – Payment Process Issues for the FiServ Hosted Payment Page Resolved. (UK/AU Only)
Some merchants using Clover or Linkly devices reported issues that prevented the completion of credit card payments using the Manual Payment process. At the end of the transaction, after you chose the Manual Payment option and finished the Spruce process, the FiServ Hosted Payment page displayed, but prevented merchants from continuing after adding the card payment details. We have updated the manual payment process in the background to ensure the payment goes through correctly, and we verified that the credit card information displays correctly in the point of sale documents.

LBMHR-1965 – FanBuilder Coupon Requests No Longer “Spamming” Orgill API.
In the past, when retrieving FanBuilder coupons from the Orgill website, the FanBuilder site was interpreting the coupon request as a call for all accounts that were a partial match for the requested Account ID. We changed our transmission format to ensure that the Orgill website could only interpret our coupon request for one specific account or contact.

LBMH02-3792 - Open Item (Terms) Account Payments Issues Resolved. (SPEC Only)
In response to some customer inquiries, we found that when applying payments to Open Item (Terms) accounts, the application did not apply the discount amounts that were appropriate for some invoices, which resulted in discrepancies between the payment amount made and the payment amount applied to the invoice balance. We have updated this process to ensure that the discounts are applied accurately to the Open Item Terms account invoices in the application.