Skip to main content
Solved

Error when publishing any customization: npm run build failed

  • May 17, 2026
  • 7 replies
  • 66 views
lauraj46
Captain II
Forum|alt.badge.img+9

We are receiving an error when attempting to publish any customization in a SaaS 2025 R2 sandbox.  We were able to publish these same customizations successfully in this environment a few days earlier, and nothing has changed as far as I’m aware.  I have already tried clearing cache and a front end Application Restart, as well as unpublishing and republishing.  The customizations validate successfully - the error occurs during the publication process.

 

Has anyone else seen this error, and what is the solution in a SaaS environment?

Best answer by lauraj46

On further testing, it looks like this issue may have been related to a missing screen dependency in one of the tenants.  The projects published successfully from a different tenant.

Laura - https://www.linkedin.com/in/laura-jaffe-965a411a/ ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.

7 replies

lauraj46
Captain II
Forum|alt.badge.img+9
  • lauraj46
  • Author
  • Captain II
  • Answer
  • May 17, 2026

On further testing, it looks like this issue may have been related to a missing screen dependency in one of the tenants.  The projects published successfully from a different tenant.

Laura - https://www.linkedin.com/in/laura-jaffe-965a411a/ ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
    A
    Jr Varsity III
    Forum|alt.badge.img+3

    Hi ​@lauraj46 recently I face this error in Sandbox & what I did is removed MUI files from customization & published. temporarily removing Modern UI files from the customization project, publish (which should succeed), then re-add them and publish again. This forces the system to lay down fresh copies.

    Since you're in SaaS, you can't access the server filesystem directly, so this option is there.

    you can only remove MUI screen files which is in this error (IN202500, IN801000, IN802000).

    Abhishek Nikam || MVP @2026 || https://www.linkedin.com/in/abhisheknikam3
      lauraj46
      Captain II
      Forum|alt.badge.img+9
      • lauraj46
      • Author
      • Captain II
      • May 18, 2026

      Hi ​@Abhishek Niikam ,

      Thanks for this advice.  I’ll keep that in mind if this error crops up again!

      Laura

      Laura - https://www.linkedin.com/in/laura-jaffe-965a411a/ ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
        R
        Captain II
        Forum|alt.badge.img+6
        • ray20
        • Captain II
        • May 28, 2026

        Publish customization project fails on 2025 R2,NPM build runs successfully. The same project can be published successfully on 2026 R1. | Community

        ​@lauraj46 I might have met the same issue with you . How did you solve it?  

        lauraj46
        Captain II
        Forum|alt.badge.img+9
        • lauraj46
        • Author
        • Captain II
        • May 28, 2026

        Hi ​@ray20 ,

        In our case the issue was related to a published customization in a different tenant on the same instance.  Once we published from that tenant, we were successful.

        Hope this helps!

        Laura

        Laura - https://www.linkedin.com/in/laura-jaffe-965a411a/ ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
        R
        Captain II
        Forum|alt.badge.img+6
        • ray20
        • Captain II
        • May 29, 2026

        ​@lauraj46 
        Thank you Laura, the "tenant" you mention refers to the tenant within the Acumatica instance, right? Not the SaaS subscription tenant?

        Let’s say one Acumatica instance has 4 tenants. If I publish a customization with Modern UI screens in tenant 1, will the customized Modern UI screens in tenants 2, 3, and 4 also be affected? Or does publishing only impact the specific tenant where I perform the publish action?

        lauraj46
        Captain II
        Forum|alt.badge.img+9
        • lauraj46
        • Author
        • Captain II
        • May 29, 2026

        Hi ​@ray20 ,

        Yes, I am referring to tenants within one instance.  It's my understanding that modern UI screen changes deployed via a customization project affect all tenants.  However screen personalizations through the UI outside of a customization project are tenant specific.  I am still learning and far from an expert on this.  Maybe others can add to this.

        Laura 

        Laura - https://www.linkedin.com/in/laura-jaffe-965a411a/ ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
        Terms & ConditionsAccessibility 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