Skip to main content
Question

Modern UI: Screens Customized by Multiple Customization Projects

  • September 2, 2026
  • 1 reply
  • 15 views

KrunalDoshi
Semi-Pro III
Forum|alt.badge.img+6

I have a question regarding the best practice for converting existing customized screens to Modern UI.

Suppose I have an Acumatica screen that has already been customized through multiple customization projects. For example:

  • Project A modifies the screen
  • Project B also modifies the same screen
  • Project C is a third-party/ISV customization that also modifies the same screen

If I want to convert that screen to Modern UI, what is the recommended approach?

My understanding is that Convert to Modern UI generates the Modern UI files (such as the .ts, .html, and view.ts files) as part of a customization project. However, if the same screen is represented in multiple customization projects, it seems that we could end up with multiple projects trying to own/modify the Modern UI definition of the same screen.

For customizations that I own, I can potentially consolidate the changes or decide which project should own the Modern UI files. But what is the recommended approach when one of the projects is a third-party/ISV customization?

I'm particularly interested in the best practice/architecture for this scenario, rather than just a workaround for a particular screen.

What is the recommended approach from Acumatica for managing Modern UI conversion when the same screen is customized by multiple independent customization projects, especially when one of them is an ISV customization?

1 reply

JKurtz29
Varsity II
Forum|alt.badge.img+1
  • Varsity II
  • September 2, 2026

I generally create my Modern UI files by hand as the built in conversion tool isn’t all that great at placing things in the proper location in the .html file.

You can have multiple customizations modify the same screen -- that’s not an issue.  Keep in mind that when you use the built in conversion tool, the names of the files are something like SO301000_ProjectName_converted.ts and .html.

In rare occasions, you may have dependencies on another modified screen.  If that’s the case, just make sure your file name is greater than the one you depend on as the files are merged together for compiling in alphabetical order.  You can go into Edit Project Items and alter the names of the generated filenames if needed.

In the screenshot below, you can see that I have multiple extensions for the same screen.  The highlighted section in the bottom half is where you can edit the filename.

Secondary note:  If your customization project name has a period (and possibly other special characters) in it, then the filename it generates will just use the characters of the project name up to that period.