MYOB Acumatica 2025.1.6 Release Notes

The 2025.1.6 release makes an Acumatica enhancement to Classic UI available for MYOB Acumatica users. It also includes other fixes that were available in an Acumatica service pack (2025 R1 Service Pack 1 Build 25.101.0153.11).

Enhanced Classic UI Support for Chromium-based Browsers

Support for the Classic UI has been enhanced to ensure compatibility with Chromium-based browsers, such as Google Chrome and Microsoft Edge, after client-side XSLT processing is removed from these browsers starting November 17, 2026. The system renders Classic UI screens correctly even when XSLT support is disabled in these browsers. This enhancement allows users who have not yet migrated to the Modern UI to continue working with Classic UI forms in Chromium-based browsers.

This enhancement was originally part of an Acumatica service pack. See the Acumatica Community forum post.

Finance

AC-374163: After the upgrade of Acumatica ERP to 25.201.0213.3 or 25.101.0153.9, when a user selected the Email Invoices option on the Print/Email AR Documents (AR508000) form and processed records, the system used the SO Invoice email template and report instead of the correct AR Invoice email template for invoices created from sales orders (that is, available on the SO Invoices (SO303000) form).

In some cases, the system displayed one of the following error messages:

  • CR Error: Email send failed. Notification Settings 'SO INVOICE' not found./li>
  • There is no active notification source to process the operation.

Workaround: Please find the workaround in this knowledge base article.

System and Platform

AC-373167: If an integration executed an API request to the DAC Schema Browser during the site startup, it could cause repeated restarts of the Acumatica ERP instance. The issue occurred when the API request triggered a long-running metadata collection that timed out and threw the System.Threading.ThreadAbortException exception type while the cache was initializing. In this case, the system cached the exception, and all subsequent API calls immediately rethrew it. As a result, the Acumatica Resource Governor detected a corrupted state and restarted the application.

Workaround: Minimize API requests to the DAC Schema Browser during the first few minutes after the application starts.

​