2026.1.3 Resolved Issues

In the mobile app, time tracking for project tasks was not available to users with Employee User or Executive User licences because they did not have access to time logs and the time-tracking screen. These users can now access time logs and use the timer from the web and mobile app.

Unlike other mobile fixes, this fix is only available once a site has been upgraded to 2026.1.3 or later, rather than updating the mobile release.

If a business event was configured to send the report as an attachment to the email notification subscriber, the report could be generated empty. The issue occurred when the report had a drop-down parameter, such as Document Type, and the value from the business event field was passed to the report parameter.

On the Import Settlement Batches (CA507000) form, when a user imported a refund batch from the Fortis processing center and created a deposit, the system excluded the surcharge amount from the deposit. As a result, the deposit amount recorded on the Bank Deposits (CA305000) form did not include the surcharge and differed from the bank statement amount.

On the Account Details (GL404000) form, when a user clicked a link in the Ref. Number column for a WIP adjustment transaction that had been created by Manufacturing and posted under the Inventory module, no document opened and no error message was shown.

When a user processed a credit card payment for a sales order with credit terms that required prepayment, the system accepted the payment as a successful prepayment regardless of the payment processing status. For example, the payment transaction could have a status that was not valid for prepayment acceptance, such as Capture Failed/Declined, Authorization Failed/Declined, or Voided, or the payment could have no active transaction. As a result, the sales order was assigned the next status after Awaiting Payment, according to the order type workflow, and could be shipped.

On the Create Purchase Orders (PO505000) form, service order and production order lines that already had related purchase orders remained available for processing. This issue occurred when the lines were marked for purchase and the related purchase orders had been created but were still open.

In the Modern UI, if a user clicked a data cell in a pivot table that used a date field with a selected date part (for example, Month, Day, Hour, or Quarter), the drilldown results did not apply the selected date part filter. The issue occurred on pivot tables based on generic inquiries and caused the drilldown to display unrelated records outside of the selected date range bucket.

The issue could also affect the filtering behavior in dashboards and generic inquiries in the Modern UI if the filter referenced a field not yet recognized by the system at the time the filter was applied. In these cases, the Modern UI could display incorrect drilldown results or filtering results inconsistent with the Classic UI.

If user-defined fields were configured in the system, emails were not created on the All Emails (CO409070) form when they should be sent by an automation schedule linked to an email template with an empty Screen box on the Email Templates (SM204003) form. In this case, the automation schedule history showed successful execution, but no outgoing email record was created. On the Request Profiler (SM205070) form, the system displayed the following error message: Unable to persist the record of type 'PX.Objects.CR.CRSMEmail'. No matching ScreenID exists for graph type 'PX.Data.PXGraph' to determine what UDF fields are required. Please ensure that you use a typed maintenance/entry PXGraph instance or provide an explicit ScreenID via PXContext when operating on data access classes with UDF fields attached.

In some cases, the generic inquiry could not be opened in the Modern UI, and the system displayed the Unexpected token error. An issue could occur if a side panel navigation parameter referenced a table for which no relationship was declared in the generic inquiry configuration. This issue could occur on the Opportunities (CR3040PL) form and other substitution forms that contained incorrectly configured side panel navigation parameters. The issue could also occur when a user selected a side panel action in the Classic UI.

On the eSign Accounts (ES301000) form, when a user attempted to connect a DocuSign production account by clicking the Connect button and completing OAuth authorization, the connection could not be completed. The system displayed the following error message: The connection to the eSign provider has failed. In some cases, the underlying error was Value cannot be null. Parameter name: source.

High SQL Server CPU usage and degraded database performance could occur if an active automation schedule with an empty screen ID was triggered repeatedly while the associated feature was disabled. This issue affected the predefined Cross-Selling ML Generation schedule when the Related Item Assistant feature was disabled, which resulted in excessive database activity.

If an API session lasted too long, the system could unexpectedly restart because of excessive memory consumption.

When an ARM report was exported to Excel or PDF from the Modern UI, the system generated a file name that contained only the current date. The report name was missing from the exported file name. When the same report was exported from the Classic UI, the file name included both the report name and the current date, as expected.

If a value of a user-defined field or an attribute was set by using the PXCache.SetValueExt() method in a customization project, the system could create an invalid push notification entry. This issue could cause the push notification queue to stop processing, preventing subsequent Business Events from being processed.

On the eSign Accounts (ES301000) form, when a user clicked Connect to authorize a DocuSign account, the connection could fail after successful DocuSign authentication because the encrypted OAuth access token exceeded the database storage limit. In this case, the connection to the eSign provider could not be completed, and the system displayed the following error message: The connection to the eSign provider has failed.

On the report forms in the Modern UI, after a user ran a report and then closed it, the report data was not cleared from memory. As users continued to run and close reports, this behavior could result in excessive memory consumption over time.

During application runtime, the workflow service retained references to recently used screens longer than necessary. This behavior could increase memory consumption and reduce application performance.

If multiple users frequently opened forms, for example, the Sales Orders (SO301000) or Bills and Adjustments (AP301000) forms, within a short period of time, the application could retain unnecessary objects in memory longer than needed. This behavior increased memory consumption and could reduce system performance in environments with a heavy user load.

In the Classic UI, users could not enter any values in the selector boxes on the forms such as Inventory Summary (IN401000), Account Details (GL404000), and Storage Summary (IN409010) when using the Microsoft Edge browser.

If a pro forma invoice was deleted in one browser session, and a user deleted the same invoice again in another session on the Pro Forma Invoices (PM307000) form, an orphaned record could appear on the Invoices tab of the Projects (PM301000) form. The record displayed the reference number of the deleted pro forma but had no other data. As a result, users could not release subsequent pro forma invoices.

On the Production Order Maintenance (AM201500) form, when a user tried to cancel a production order that was linked to a child production order with a different unit of measure (UOM), and no unit conversion was defined between the UOMs for the parent item, the system displayed the following error message: IN Error: Unit conversion <UOM> is missing.

On the Clock Entry (AM315000) and Multiple Production Clock Entry (AM316000) forms, when transactions were processed concurrently for the same employee or a user clicked the clock-in or clock-out action multiple times, the clock entry counters could become out of sync with the existing clock transaction records. As a result, the clock-in action could complete without any visible response, or the clock-out action could fail with the following error: Another process has added the 'AMClockTran' record. Your changes will be lost.

On the Inventory Planning tab of the Item Warehouse Details (IN204500) form, when the Planning Method was set to Inventory Replenishment, a user could not select the Override check box for Reorder Point if the Override check box for Safety Stock had been selected.

On the Move (AM310000) form, when a user released a move transaction with a partial quantity for a production order that was linked to a sales order and then tried to release another move transaction after the sales order demand plan had been re-created, the system displayed the following error message: An error occurred during processing of the field DemandPlanID value <DemandPlanID> Error: DemandPlanID <DemandPlanID> cannot be found in the system.

On the Production Order Maintenance (AM201500) form, multiple production orders were created and linked to the same sales order line split if the user did the following:

1. Split a sales order line into multiple lines with an equal quantity of the initial line quantity in the Line Details dialog box of the Sales Orders (SO301000) form
2. Processed these line splits on the Create Production Order (AM510000) form

If a user later tried to delete, cancel, or unlink these production orders, the system displayed the following error message: 'OrderDate' cannot be empty.

On the Production Orders (AM201500) form, if a production order used the Actual costing method and a user released multiple final move transactions, and then released a negative final move transaction that fully reversed the completed quantity, the system overstated the WIP balance. This issue affected production orders for inventory items that used the Average valuation method.

On the Shipments (SO302000) form, for a sales order line marked for production, the Completed status of the production-linked line split was cleared when a user did any of the following:

• Selected or cleared the Allocated check box of a line split
• Edited the Quantity of the line split
• Added a line split
• Removed the line split

When the user then tried to confirm or correct the shipment, the system displayed the following error message: The line cannot be deleted because it is linked to a shipment.

When the New Release Process check box was selected on the Production Preferences (AM102000) form and a production order used the Actual costing method, the system could calculate an incorrect cost if the following sequence of actions occurred:

1. A user manually released a material transaction.
2. The user completed the production order by releasing a multi-line move transaction in which the last-operation line was not the final line.
3. The user reopened the production order by releasing a negative move transaction on the Move (AM302000) form.
4. The user reversed the material transaction on the Materials (AM300000) form.
5. The user completed the production order again.

The system then created an inventory receipt with an incorrect cost. As a result, the WIP Balance box on the Totals tab of the Production Order Maintenance (AM201500) form was overstated.

When a user imported a refund from Shopify for an unfulfilled order that had been refunded with the Restock item check box cleared in the Shopify store, the system created a return (RC) order for the refunded items even though the previously imported sales order had the Open or On Hold status and the items had not been shipped. In this scenario, the connector also canceled the original order and incorrectly applied the refund payment to the newly created RC order instead of the original payment.

This issue could also occur when refunds were imported for edited Shopify orders from which unshipped items had been removed. In this case, the refund synchronization created a return (RC) order for the removed items and a refund payment that was not applied to any document, which left open balances.

When a user synchronized a company between Acumatica ERP and Shopify by using the Company entity, the system did not remove contact roles in Acumatica ERP when a contact was deleted or removed from a company location in Shopify. As a result, the removed contact remained assigned to the corresponding customer location on the Customer Locations (CR303010) form. Also, if a company location was inactive in Acumatica ERP, the system continued to export it to Shopify, creating duplicate inactive locations instead of ignoring them.

Fix Description: The synchronization process now correctly removes contact roles from customer locations when the related contact is deleted or removed from the corresponding company location in Shopify. Additionally, inactive customer locations in Acumatica ERP are no longer exported to Shopify.

When a user clicked Shop for Rates to get the USPS ShipEngine rate for a shipment on the Shipments (SO302000) form, the rate displayed in the Shop for Rates dialog box was about twice the actual rate. However, after the user confirmed the shipment, the system displayed the correct freight cost on the form. This discrepancy caused delays in shipment processing due to uncertainty in carrier rate calculations.

When two users concurrently modified the same service order and one of its appointments on the Service Orders (FS300100) and Appointments (FS300200) forms, the system silently corrupted the internal line counter (LineCntr) of the service order. As a result, the affected service order and its appointments became unusable. Users could no longer add detail lines or create or link AP bill documents. The following error messages could appear:

• An attempt was made to add a duplicate entry.
• An unhandled exception has occurred in the function 'MoveNext'. Please see the trace log for more details.
• Object reference not set to an instance of an object.

The issue occurred after concurrent saves when one user edited a service order while another user saved its appointment.