ECOMMR-5529 – Enforcing the Branch Tax Code use for Pickup of Online Orders.
In the past, when a customer placed an online order and requested pickup as the delivery method, we applied the tax based on the delivery address rather than the branch address. We have updated this to ensure the branch-based tax code is applied when the customer picks up the online order at the branch.
LBMHR-205 – Adding Adjustments to Direct Ship POs Corrected.
In Direct Ship transactions, you can add a Purchase Order and apply any necessary adjustments to complete the transaction. Salespeople typically add the adjustment to the transaction in the PO Processing form using the Adjustments subtab. The application allowed the salesperson to add the adjustment, but after processing, it did not appear in the Purchase Order document. There are, in fact, two possible types of adjustments involved here: the PO adjustment and the Direct Ship Order adjustment. We modified the process to ensure that any adjustment appears on the appropriate document. This ensures that financial data and order costs are accurately transferred and accounted for in the Point of Sale and Purchase Order documents.
LBMHR-438 – Weight Display Issues on PS Invoice Dispatch Documents Corrected.
Not all items in your inventory may have weight measurements, so when you create a Dispatch document, not all items in that document will contain weight measurements. A customer asked us to correct an issue they noticed: when the first item on the InvoiceDispatch document lacked a weight setting, the weight measurements for the other items did not display, even when weight measurements had been assigned. We have corrected this issue to ensure that any item that has weights assigned to it display correctly in the InvoiceDispatch document.
LBMHR-492 – After Reconnecting to Remote Client, Icons No Longer Stack in Task Tray. In the past, when you reconnected to the Remote Client utility after an outage, an additional application icon displayed in the task tray to represent the new connection. This was confusing because you couldn’t be sure which icon was the live connection. We have updated this process to replace the old icon, preventing multiple icons from displaying in the task tray.
LBMHR-627 – Adding to Favorites Improved.
Adding certain application form areas to Favorites makes it easy to access those settings quickly. A customer reported that when they attempted to add the Purchasing > Inquiry > Vendor setting to the Favorites in the toolbar, the option was disabled, even though the user had Purchasing > Inquiry permissions. We have corrected this issue to ensure that any form a user can access can be added to their Favorites list.
LBMHR-650 – SPEC Orders Populate “To Be Delivered” Date Successfully.
An ecommerce customer reported that when they imported ecommerce orders, the To Be Delivered information was not populating the Order Processing form. This was true for auto-processed orders and for manually imported orders. We have updated this process to add a DeliveryDate field to the OrderRequest model in the ecommerce API to ensure that when we import ecommerce files we include the delivery date information shared in the customer’s order. See New Setting Prioritizes Online Orders based on Requested Delivery Date (SPEC) for more information about this change.
LBMHR-788, LBMHR-977 – Deleted Cost Percentage Adder No Longer Duplicating Adder Cost Subtractions. A customer reported that after adding a cost adjustment to a sale transaction, if the adjustment was later deleted, the application subtracted the adder cost twice. We identified where the application was performing this second subtraction and removed it from the code. This is working correctly again.
LBMHR-798 – Multiple Order Number Printing/Display Resolved when using F5 Invoice. We corrected the issue that prevented multiple invoices that are processed together (using the Invoicing (F5) key in Sale entry) from printing and displaying on the Order Document record.
LBMHR-821 – Image List Display Issues Resolved.
When you want to see what an item in a data grid looks like, you choose the Image List option in the context menu to view it. A customer reported that they were unable to view the images they had saved using this process, and that attempting to do so caused the application to close suddenly. After some testing, we found that the size of the image was causing the issue. We now display the same image at a lower resolution to ensure the security and reliability of the display process.
LBMHR-986 – Clothing Item Tax Issues Resolved in Daily Sales Report.
There was a place in our code where we were adding the tax exemption for clothes (when enabled) in more than one place, which resulted in errors in the Daily Sales Report. We have corrected this issue and added additional tests to ensure that we check for this type of error in the future.
LBMHR-1167 – Import Wizard Misapplication of Suggested Retail Price Resolved. (Non-US Locations). A UK customer requested that we resolve an Import Wizard issue that applied the Suggested List Price of the first item in an Import Wizard file to all entries in the file, then applied them to the catalog during import. This error occurred because some data structures we built for UK-specific tax settings were not cleared properly. We have corrected this issue.
LBMHR-1344 – Resolved: Authorized Gift Card Issues Applying Partial ROA Payments.
When customers made payments on account using an authorized gift card for part of the outstanding amount, the application incorrectly applied the total payment amount to the account. This caused issues in the Point of Sale journals and the End-of-Day reports, resulting in a loss of revenue for the business. We have refactored the partial payment process to disable the Bankcard field and set it to 0, and testing shows we are handling the partial payment process involving gift cards correctly.
LBMHR-1351 – Cancel (F9) Issue in the Attachment Maintenance Utility Resolved.
Customers reported that when they were working in the Attachment Maintenance Utility and they clicked the Cancel (F9) key, the application would close with an error message. After investigating this issue, we found that there was a problem with enabling and disabling the Delete button on this form, which, when you clicked Cancel, caused the application to close. This prevented unauthorized access to the delete function in Attachment Maintenance, but it was a bit extreme. We now handle authorized access to the Delete button more effectively, so this error no longer occurs.
LBMHR-1418 – Credit Issues Associated with Interim Statement Corrected.
When investigating a business’s concern, we found that we were not collecting all of the open credits in the billing cycle when creating interim statements. We have updated the search criteria to resolve this issue and have tested it to ensure this works when creating interim statements for all Balance Forward, Open Item, and Open Item with Terms accounts.
LBMHR-1419 – Sales Tax Report Issues using Previous Month Setting Resolved.
A customer reported that when they attempted to generate a Sales Tax Report by selecting the Previous Month setting from the Selected Month list, the application produced a report with all zeros. We investigated this issue and corrected the problem to ensure that this report runs correctly with this setting.
LBMHR-1516 – Creating Duplicate Discount SKUs during Promotion Issue Corrected.
When you create an Instant Credit Promotion, you set item number limits and tie them to the promotion’s sale price. When a customer attempts to purchase a quantity above the promotion limit, the application should not add an additional promotional SKU to the transaction to expand the discount. This issue has been corrected.
LBMHR-1762 – Processing Some Cost Corrections no longer Causing Database Locks.
A customer reached out to us after experiencing database locks when processing cost corrections. In researching this case, we found that a user was attempting to process a cost correction for a receipt that was over a year old. This is not permitted, but the application did not notify the user of this issue. We have updated the application to display this message when someone tries to submit a receipt cost correction for a receipt that is over a year old.
Another issue we found was that a user attempted to process a new cost correction for an inventory item that had an unprocessed cost correction. We have added a message to ensure this situation is clear, and to offer options.
-
A previous cost correction, document <document ID>, did not complete successfully. To attempt to process this correction, now respond Yes or respond No to not attempt at this time. Responding Yes may result in an additional delay.
Based on the message response, the application either processes the previous cost correction and then processes the new cost correction, or ignores the previous cost correction and processes only the new correction.
LBMHR-1766 – Improved Security on Restricted Manual Card Entry Behavior.
When you set up a Point of Sale user ID, you can specify Manual Card entry settings to allow that user to perform these transaction-based tasks. If those settings are not enabled, the user should be able to process transactions only through the existing automated processes. A customer reported that when their customer cancelled a transaction, the system reverted to a manual entry process option, even if the user did not have manual transaction processing permissions. We have corrected this issue to prevent unauthorized users from seeing the Manual Card process options. Only Cancel and Retry options are available in this case. We have tested this update under a variety of similar circumstances to ensure this works as expected.
LBMHR-1773 – EDI X12 Receive Process Improved to Prevent Multiple Receipts.
A customer shared that they were using the Bulk Receive option using Benjamin Moore X12 EDI process, which resulted in duplicate and sometimes more item receipt files. After investigating, we added a process that checks to see if the purchase orders that are requested have been requested before and if so, displays a task list warning:
LBMHR-1789 – EDI X12 Benjamin Moore Bulk Receive Process Issue Corrected.
A customer reported that when they used the Benjamin Moore X12 Bulk Receive EDI process, some of the Purchase Order updates were unchecked by default. This prevented the system from retrieving the updated POs as expected. When we investigated this issue, we realized we were not setting the correct state for the Update button on the Preview screen, which led to some PO settings being deselected. We have corrected the logic for the Update flag, so all available Purchase Orders are updating as expected.
LBMHR-1811 – PO Receipt Reflects Renamed Items Correctly in a Customs Manifest.
A customer reported that when they attempted to process a PO receipt that was part of a Customs Manifest, and an item in the manifest had been renamed, the system did not update the manifest with the new SKU. We have resolved this issue to ensure that the Customs Manifest reflects the correct SKU when an item is renamed.
LBMHR-1813 – Price Group and Contract Pricing No Longer Affected by Volume Discounts. We noticed that Volume Discounts were applied to transactions that already had Price Group and Contract pricing settings, which was unintended. We have updated this process to ensure contract and price group pricing is respected. We have also tested to ensure that unit price break settings are affected by volume discounts only when they are not part of these other price settings, as originally intended.
LBMHR-1907 – Setup > Notify > Internal Tab Visible Appropriately in Parameter Settings.
When you have administrative permissions in RockSolid MAX and you have access to the Parameter Settings form, Setup > Notify tab, you should also have access to the Internal tab. We have restored access to the Internal tab to authorized administrators.
LBMHR-1952 – DIB Price Change/Sale Price Processing Slowness Issues Resolved.
A customer reported that while processing Do It Best price changes and sales price updates, database deadlocks occurred, which prevented transactions from completing at multiple stations. This issue occurred at individual branch locations and when the update was for multiple stores. We have solved this process by breaking down the update process into smaller batches. While this does tend to slow processing down for the entire network, it does not cause deadlocks, and transaction processing still works. An alternative that prevents system slowness is to process price updates outside normal business hours.
LBMHR-1956 – Retrieving LMC Invoices Process Improved.
A customer reported that when they used the LMC invoice retrieval script to download new invoices, the script retrieved only one invoice, even when there were multiple invoices waiting. We updated the script to ensure that all receipts were retrieved as expected.
LBMHR-2022 – Updates to the AML Kiosk Working Better with Latest WebView2. (Caribbean) If you are using the AML Kiosk to check prices, you may have seen a message that asks you to restart the device so it can be updated. However, when you do, the same message appears again. After some investigation, we found that the Kiosk was using the incorrect version of WebView2. We have updated the installation process to check the version number of WebView2 by default now, and when we find an invalid version, this message displays:
We have also enhanced the logging to ensure that Support can use the RemoteClient logs to diagnose and resolve this type of issue quickly.
LBMHR-2123 – Ecommerce API Method Returns Nil Results for Some Terms-Based Posting Fields. When you use the GetAccountBalanceDetail method in the Ecommerce API and you apply it to an account with Terms settings, the application returns a nil (null) result for the DiscountDate and DiscountRemaining fields. For all other account types, the DiscountDate and DiscountRemaining fields should be populated.
LBMHR-2275 – Adding a Section to Inventory Group Displays it in the Right Group.
When you add a new Section to a Group, you expect the section ID and description to appear within the selected Group list. This was not happening due to changes we made to the database where this information was stored. We have corrected this issue so the new Section displays numerically where it should in the Group Section list.
LBMHR-2289 – File > Branch List Order Displaying Correctly.
A customer noticed that when they added a new branch between two other branches, the new branch displayed at the bottom of the File > Branch list rather than in the order the branches would fit. We updated this process to ensure that branches display in numerical order, as expected.
31.0 Release