LBMH01-8007 – Deleting Adjustments from a Transaction Deletes them Entirely Now.
When you enable the Unlimited Adjustments feature (Parameters > Purchase Orders), the feature also applies to Point of Sale transactions. If you added an adjustment to a transaction and then deleted it before processing, the application did not delete the adjustment entirely, which caused some differences in totals and reports. We have corrected this logic to ensure that adjustments you delete before processing (in Point of Sale and in Purchase Order Entry) work as expected.
LBMHR-726 – TrueValue Data Send Issues Resolved.
A customer reported that they were unable to perform a Data Send to TrueValue for specific items in their inventory, reporting:
We found that when the items had a negative suggested retail value, and the items were returned, the application was unable to transmit that sales information to TrueValue using the Data Send process. We updated the stored procedure to account for this condition and the application can send these records to TrueValue without issue.
LBMHR-974 – Unbalanced EOD Issue Caused by AP Disbursement Resolved by Adding Errors and Messages.
When you pay a local vendor using a foreign check account, it creates unbalanced EOD issues for AP disbursement GL journals. Now, when you attempt to apply this kind of disbursement, a message displays, warning the user about this inconsistency and asking them to confirm this action. This should prevent these end-of-day issues from occurring again. These protections have been added to AP Billing and to Disbursements to prevent these GL journal and EOD issues.
LBMHR-1005 - EasyAP Utility Supporting Discount Adders Correctly.
We have modified our processes to ensure that all adjustments, including discounts, can be applied to EasyAP utility receipts. We have also corrected adjustment index issues that were occurring during the import and receipt selection process.
LBMHR-1061 – Incoming TrueValue Price Updates Contain Correct Suggested List Price.
We have modified our EDI process to ensure that when the application receives True Value price updates, we check to see that if we have already converted the suggested retail price, we do not attempt to do it again. This caused the reported error that set the new list price to 0.00. This change corrected the issue.
LBMHR-1089 – Modified Notes of Online Orders No Longer Affecting Delivery Information.
A Spruce eCommerce customer reported that when the customer updated an online order or quote to add order notes, these notes were displacing delivery information in the resulting documents. We have corrected this issue to ensure that changes to notes display where they are intended and the delivery information is not affected by these changes.
LBMHR-1240 – Corrected Statement Rescaling Printing Issues.
A customer reported printing issues when they attempted to rescale reprinted invoices. This turned out to be a printer tray issue, which we have resolved.
LBMHR-1275 – Branch Notification Issue Corrected for Ecommerce API Payments.
A customer showed us that when they received online payments, and the branch notification setting contained a user or user group ID with a particular number, and that number was present in other user IDs, the notification message went to all users that had that same number in their user IDs. We have corrected this issue to ensure that only the user(s) specified in the branch’s Branch Setup > Ecommerce tab > Notify User or Group list receive(s) payment notifications for online payments.
Note: If the eCommerce Notification User/Group in the Ecommerce system parameters is set but the branch notification user/group is not, the application sends the notifications to the user/group designated in the Ecommerce system parameters. If neither the Ecommerce notification parameter nor the branch notification settings are enabled (contain a valid user ID), notifications are not sent when Ecommerce payments are received.
LBMHR-1302 – New: Prevent Spruce eCommerce Order Data from Replacing Account Info.
When a customer submits an order through Spruce eCommerce, and that customer’s account exists in the application, it is important that the order data does not replace the data in the account. The code now prevents the account’s phone number from being overwritten by the phone number submitted in a Spruce eCommerce order.
LBMHR-1338 – Rounding Issue that Caused a Posting Credit Error Resolved.
We discussed an error a customer was seeing when they tried to post a credit to an account and received the message: Passed in credit amount cannot be more than credit amount selected. Please (cancel) then post again. After some investigation, we found that the application was rounding the credit amount it was trying to apply so that it exceeded the amount that the person specified in the posting transaction. We have modified our process so the rounding is taken into account for this process, which prevents the error from occurring.
LBMHR-1359 – Processing Invoice Documents No Longer Causing Error.
When processing invoice documents in Point of Sale, a customer reported receiving the error message Object Reference not set to an instance of and object. We have corrected the issue that caused this message to display and this process runs correctly for this customer again.
LBMHR-1385 - Inventory Cost Corrections Processed Correctly, Even the Next Day.
We discovered that if you processed an inventory cost correction on a day after the inventory was received, the General Ledger files were not posting the change correctly to the Inventory General Ledger. We have corrected this issue.
LBMR-1412 - Corrected: SO Issue when Manufacturer's SKU Copied into Catalog Field.
A business reported that when they tried to create a special order for a non-stock item, and they entered the manufacturing SKU, the application copied it into the Catalog field before the order was processed. Then, when the manufacturer's SKU was the same as any vendor's SKU that already existed, it would replace the chosen vendor with the vendor associated with the matching vendor SKU, which resulted in an order for the wrong item. We corrected the code that caused this issue. This process works as expected now.
LBMHR-1453 – Viewing Attachments Issue Corrected.
When a customer tried to open an attachment file, they reported that they encountered the message, Unable to open specified attachment file before the application closed suddenly. This turned out to be an empty error message that did not display. We have corrected this issue to ensure that the error message displays when the attachment cannot be opened.
LBMHR-1564 – EasyAP Due and Discount Date Issues Resolved.
When importing AP billing information from the application, the due date and the discount date were sometimes set incorrectly. This appears to be an issue when the due date is more than three months from the current date at the time of processing. This change ensures that we use the dates in the supplied file, so the payables match the data we receive.
LBMHR-1605 – Report Parameters Box Heading Displays Correctly Regardless of Scaling Setting.
We updated the Report Parameters Box to display the Required heading correctly. It was cut off in the previous release.
LBMHR-1614 – Updated the Mapping for Do It Best Purchase Orders.
We updated the Do It Best purchase orders mapping to ensure a more successful delivery.
LBMHR-1660 – Charge Return with VAT Tax Issue Resolved. (Caribbean Only)
When processing a charge return with a VAT tax, the customer noticed that the application was closing suddenly with a message, Object reference not set to an instance of an object. We found that this issue was tied to the returned transaction containing a disabled tax code. We have modified this process to show a prompt when this circumstance occurs so the user can replace the disabled tax code with the new default code. This works for orders and for quotes.
LBMHR-1669 – BOPIS Messages No Longer Causing EDI/Universal Log Issues.
A customer reported that the BOPIS messages in their EDI process were preventing the load and display of key Universal Log and EDI Log data. We have implemented changes in both processes to better manage the flow of information in these lists. The EDI Log now contains the date range setting (like the one in the Universal Log), which will significantly reduce the amount of data the application will attempt to load at a time.
Purchasing > Inquiry > EDI Log
In the DIB In-Store Pickup Settings, we have also added a new Logging Level option, which will expand or limit the amount of BOPIS data the application will collect and display. We will update this information in the Help System to ensure these changes are clear.
Maintenance > Database > Branches > EDI > DIB > DIB In-Store Pickup
LBMHR-1688 – iDashboards Form Understands Users Better Now.
When a user who was not an iDashboards administrator attempted to load iDashboards (in some instances), the application did not recognize them as a valid user. We have corrected this issue.
29.0 Release