Skip to main content
Answer

Error when Publishing Customization with Modern UI files

  • July 25, 2025
  • 5 replies
  • 240 views

MichaelShirk
Captain II
Forum|alt.badge.img+5

Has anyone seen this error when attempting to publish a customization with Modern UI files?
Build 24.209.0013 

I build a simple maintenance screen on the Classic UI, now I’m trying to convert it to the Modern UI and add the files to the customization project in preparation for when I need to do this with our production customizations. 

I created the MUI files and successfully built them in the FrontendSources/screen folder using the 
npm run build-dev --- --env screenIds=SWUI0001 command. 
Then I was able to switch the screen to the MUI and it worked as expected. 

I then added the files to the customization project, but it won’t publish, and the error doesn’t point to any specific files.

 

 

 

Best answer by MichaelShirk

After upgrading my site to the 25R2 Beta version and recreating the files (lost them during the upgrade process,) I was able to go through the build process, add them to the customization, and publish the successfully. 

I can’t 100% know whether it was rebuilding the files, or upgrading the version that fixed it, but the files are super simple, and had worked prior to adding them to the customization, so I’m inclined to believe it was an issue with the Acumatica version.

@darylbowman I didn’t need to build for production. Building for dev worked.

5 replies

darylbowman
Captain II
Forum|alt.badge.img+15

Did you build them for production before adding them to the package (ie: npm run build)?


MichaelShirk
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • July 29, 2025

@darylbowman no I didn’t, is that a requirement? If so, is it specified in the documentation?


darylbowman
Captain II
Forum|alt.badge.img+15

I’m not sure if it’s a requirement. I would recommend trying it.

Remove and re-add the files to the package AFTER doing so.


MichaelShirk
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Answer
  • August 29, 2025

After upgrading my site to the 25R2 Beta version and recreating the files (lost them during the upgrade process,) I was able to go through the build process, add them to the customization, and publish the successfully. 

I can’t 100% know whether it was rebuilding the files, or upgrading the version that fixed it, but the files are super simple, and had worked prior to adding them to the customization, so I’m inclined to believe it was an issue with the Acumatica version.

@darylbowman I didn’t need to build for production. Building for dev worked.


darylbowman
Captain II
Forum|alt.badge.img+15

Makes sense, since Acumatica rebuilds the files for production during every publish