Skip to main content
Solved

25R2 form cannot be switched to the Modern UI

  • February 19, 2026
  • 8 replies
  • 0 views

Forum|alt.badge.img+1

I have a custom form; it works fine in Classic UI. I’ve migrated it to Modern UI in build 25.200.0248 and it works fine in my dev environment.

We have a staging server; I’ve deployed it there and it also works fine.

But on the customer’s tenant I get the error message “The .. form cannot be switched to the Modern UI because it does not support it yet.”.

(The customisation project includes the correct .html, .ts and .css files.)

Does anyone have any ideas??

 

(It’s not just the one form it looks to be all of the New custom forms.)

And none of the customisations of standard forms are working.

Best answer by allisterchambers48

The fix was to use Publish to Multiple Tenants and tick every tenant.

My mistake was to assume that I could publish to one tenant, and then publish to the remaining tenants without affecting the first.

It looks like the publish process will remove Modern UI customisations from All Tenants, regardless of whether they are selected for publishing to.

8 replies

  • Freshman I
  • February 19, 2026

Hi ​@allisterchambers48 ,

This issue is most likely caused by a version mismatch, not the customization itself.

Since the form works correctly in Dev and Staging (Build 25.200.0248), the .html, .ts, and .css files are valid and properly implemented.

It appears that the customer tenant may not be running the same/latest 25R2 build. Upgrading the customer environment to the latest 25R2 version should resolve the issue.

Please let me know if you need any further clarification.


Forum|alt.badge.img+1

Hi ​@tareshpatil51 

The customer was upgraded to Build 25.200.0248.4 last night.

Our test server is running 25.200.0248.

As is my dev laptop.


Forum|alt.badge.img+1

Hmm. I wonder. I published to the primary tenant, and then used Publish to Multiple tenants without selecting the primary. Maybe that removed the modern files from the primary tenant.


  • Freshman I
  • February 19, 2026

Hii ​@allisterchambers48 , I recommend to once try to rebuild the Modern Ui files .

Open the source code , try to find the FrontendSources\screen open in the terminal and run command

 npm run build-dev

 

and let me know if this works


  • Freshman II
  • February 19, 2026

@allisterchambers48  Are you encountering this issue with other screens (such as standard Acumatica base screens), or does it only happen with your custom screen? If possible, please provide the trace information—it would be very helpful.


Forum|alt.badge.img+1

The fix was to use Publish to Multiple Tenants and tick every tenant.

My mistake was to assume that I could publish to one tenant, and then publish to the remaining tenants without affecting the first.

It looks like the publish process will remove Modern UI customisations from All Tenants, regardless of whether they are selected for publishing to.


Forum|alt.badge.img+1

I think what happens is that the Publish process removes *everything* from FrontendSources\screen\src\customizationScreens\*\screens

Rather than only purging those folders that are specific to the selected tenants.


Forum|alt.badge.img
  • Jr Varsity II
  • February 19, 2026

If it works in Dev and Staging but fails on the customer tenant, the issue is almost certainly tenant-level configuration.

 

Most likely Modern UI is not fully enabled or provisioned on the customer tenant (feature flag, build mismatch, or site-level setting).

 

Have them verify Modern UI is enabled and confirm the exact build version matches your staging server.