Skip to main content
Answer

Guidance Needed: Upgrade from 2024 R1 to 2025 R1 – PX.Concurrency Namespace Issue

  • September 4, 2025
  • 1 reply
  • 76 views
K
Freshman I

Hi community,

We are in the process of upgrading our customer's environment from 2024 R1 to 2025 R1. when we published our existing customization package on the 2025 R1 environment, we encountered the following validation error:

[2025-09-02 11:27:41.384] Building directory '\WebSiteValidationDomain\App_RuntimeCode\'. [2025-09-02 11:27:42.797] \App_RuntimeCode\SOInvoiceEntry.cs(7): error CS0234: The type or namespace name 'Concurrency' does not exist in the namespace 'PX' (are you missing an assembly reference?) [2025-09-02 11:27:42.797] \App_RuntimeCode\SOShipmentEntry.cs(40): error CS0234: The type or namespace name 'Concurrency' does not exist in the namespace 'PX' (are you missing an assembly reference?) [2025-09-02 11:27:42.797] Compiler time, in seconds: 17.8884243 [2025-09-02 11:27:42.891] Validation failed.

In the 25 R1 release notes, we noticed that the PX.Concurrency namespace was renamed/modified.

PX.Concurrency was renamed → PX.Async

However, we only have access to the most recent source code of our customizations and do not have the older code versions where this namespace was originally referenced.

Could you please advise on:

  1. The correct replacement namespace or class for PX.Concurrency in 2025 R1.
  2. Whether there are official migration guidelines or code samples provided by Acumatica for resolving such breaking changes between 2024 R1 → 2025 R1.
  3. Any best practices for handling these types of breaking changes in customization packages during upgrades (especially in cases where we do not want to rename the source code manually).

Your guidance will help us ensure a smooth migration process.

Thank you in advance for your guidance.

Best answer by DipakNilkanth

Hi ​@kviranga38,
As per Acumatica’s release notes for 25 R1,  The PX.Concurrency namespace has been renamed to PX.Async.
 

To resolve this issue, locate the SOInvoiceEntry.cs graph code (this can be found in the Code section of the Customization Editor if you have extended the graph). Update the namespace reference by renaming it to PX.Async as outlined in the Acumatica 25 R1 release notes.

If the PX.Async namespace is not being referenced anywhere in your code, you can safely remove those references from the graph.

    1 reply

    DipakNilkanth
    Pro III
    Forum|alt.badge.img+13
    • DipakNilkanth
    • Pro III
    • Answer
    • September 4, 2025

    Hi ​@kviranga38,
    As per Acumatica’s release notes for 25 R1,  The PX.Concurrency namespace has been renamed to PX.Async.
     

    To resolve this issue, locate the SOInvoiceEntry.cs graph code (this can be found in the Code section of the Customization Editor if you have extended the graph). Update the namespace reference by renaming it to PX.Async as outlined in the Acumatica 25 R1 release notes.

    If the PX.Async namespace is not being referenced anywhere in your code, you can safely remove those references from the graph.

    Dipak Nilkanth || MVP @2025 || https://www.linkedin.com/in/dipak-nilkanth-293591102 || Acumatica Developer
    Dmitrii Naumov
    B
    Chris Hackett
    Terms & ConditionsCookie settingsAccessibility statement
    About Acumatica ERP system
    Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
    © 2008 — 2024  Acumatica, Inc. All rights reserved