Fixes and Enhancements – MYOB Acumatica v2023.1.500

For those seeking some further detail on fixes and enhancements contained within the 2023.1.500 release (excluding Payroll), here's a run down: 

Finance:

• if a user signed in to an operating system with a locale that was configured with a comma as the decimal symbol and a period as the digit grouping symbol, and then the user entered a number in a box in the Summary area of a form and clicked any button, the comma was displaced 2 decimal places to the right of its intended position (for example, if the user entered 123,50, the value changed to 12350,00).

 

Inventory and Order Management

• In a sales order with the Invoice, Credit Memo, or Mixed Order automation behavior, which is defined on the Template tab of the Order Types (SO201000) form, the values in the Unbilled Quantity and Unbilled Balance boxes on the Totals tab of the Sales Orders (SO301000) form were not updated to 0 after a Acumatica Release Notes for 23.118.0016 sales invoice was created and released for this sales order if the sales order had a zero Ordered Qty.
• On the Sales Orders (SO301000) form, when a sales order had multiple lines linked to drop-ship purchase orders, clicking the link in the Drop-Ship PO Nbr. column on the Details tab did not open the corresponding drop-ship purchase order on the Purchase Orders (PO301000) form. The same issue was with opening sales orders by clicking the links in the drop-ship purchase orders on the Details tab of the Purchase Orders form.
• On the Commissions tab of the Invoices (SO303000) form, the Commissionable Amount value was calculated incorrectly if a group discount configured for a customer was applied in a document that was prepared for the shipped sales order. The error occurred if the invoice was prepared for a sales order whose type had the Recalculate Discount on Partial Shipment check box selected on the Order Types (SO201000) form.
• If an item's quantity was greater than its Available for Shipping quantity in the specified location and Ship Complete was selected in the Shipping Rule column for this item on the Details tab on the Sales Orders (SO301000) form, a user could link this sales order to a shipment by using the Add Order button on the Details tab of the Shipments (SO302000) form and saving the shipment.
• If a sales order that collected taxes and was in the Back Order status in Acumatica ERP was modified in a Shopify store and then synchronized with Acumatica ERP, the connector failed the sync record for this order and showed the following error messages on the Sync History (BC301000) and Process Data (BC501500) forms: The following tax identifiers from the external system could not be matched: . The ERP has failed to save the tax ID or the tax amount differs from the one that has been expected. Make sure that taxes are configured for the tax zone and tax categories. Also, make sure that taxes either have the same identifiers in the ERP and external system or are mapped on the Substitution Lists (SM206026) form. This issue occurred if the Tax Synchronization check box was selected, the Default Tax Zone box was empty, and the Use as Primary Tax Zone check box was cleared in the Taxes section on the Order Settings tab of the Shopify Stores (BC201010) form.
• If an invoice was released for part of a sales order, the payment for the order was released, and then if the application was reversed on the Application History tab of the Payments and Applications (AR302000) form, users could not remove the payment from the order because of the error, which indicated that the Transferred to Invoice amount was not equal to 0.
• If a lot- or serial-tracked item was added to a return order by adding an invoice line on the Sales Orders (SO301000) form and then a partial receipt was created for that item on the Shipments (SO302000) form, the following error occurred when a user clicked the Confirm Shipment command: Item in invoice lot/serial number quantity returned is greater than quantity invoiced.

System and Platform

• In the trace logs for any form, the company ID was empty for the long-running events.
• Simultaneous search for many values separated by a space in a drop-down list on any form could lead to a stack overflow exception and the restart of the instance. Fix Description: If there are more than 10 values to search for, the system takes only the first 10 values.
• If an action execution was selected as a subscriber on the Subscribers tab of the Business Event (SM302050) form, the system could not process this subscriber when the business event occurred and showed the following error message: Object reference not set to an instance of an object.
• In some cases, the statistics on the System Queue Monitor (SM302010) form were not displayed if multiple tenants were configured in the system.
• In rare cases, if two transactions were nested in each other and one of them failed, the system still saved the results of the other transaction in the database, potentially causing data inconsistency, which could include duplicate GL batches, shipment counter corruption, or a 200-status code response to the PUT CBAPI request with no entity created.

Retail-Commerce

• The Shopify connector has been aligned with the Shopify API version 2024-01 to support instalment transactions for orders paid with the Shop Pay payment method.
• In some cases, when a Shopify order and its payment was imported to Acumatica ERP, the imported sales order was created on the Sales Orders (SO301000) form with the Tax Calculation Mode set to Tax Settings on the Financial tab, an incorrect order total, which included sales tax twice, and a nonzero unpaid balance. The issue occurred if the following conditions were met:

o   In the Shopify store, sales tax was set up to be included in product prices and shipping rates.

o   Avalara AvaTax was configured as the tax provider on the Tax Providers (TX102000) form.

o   On the Shopify Stores (BC201010) form, tax synchronization was enabled for the store and the Avalara tax zone was selected as the primary tax zone

Integrations

• On the Shipments (SO302000) form, if a user shopped for rates by using the UPS Ground service method and increased the gross weight of the package beyond 50lbs, the following error occurred: UPS: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'PX.UpsRestCarrier.Model.CodeDesc' because the type requires a JSON object.

Service Management

• If the time zone on the user's computer was set to UTC+12, on the Staff Calendar Board (FS300400) form, the week numbers could duplicate in the Month view.
• In some cases, on the Service Orders (FS300100) form and on the Appointments (FS300200) form, when a user was adding a new line on the Details tab of the form, it took approximately 20 seconds for the system to load the information from the Inventory ID selector.