Skip to main content
Question

Classic UI to Modern UI customization compatibility

  • September 5, 2026
  • 1 reply
  • 8 views

Forum|alt.badge.img

We have a large number of existing customizations built for Classic UI, including ASPX changes, JavaScript, PXControls, grid customizations, actions, and screen extensions.

When the same screen is converted to Modern UI, which types of customizations typically require complete redevelopment rather than minor modifications?

1 reply

Naveen Boga
Captain II
Forum|alt.badge.img+20
  • Captain II
  • September 5, 2026

​@John Masi74Β  Β In general, server-side customizations are more likely to be reusable, while customizations that depend heavily on the Classic UI framework typically require redevelopment.

Usually reusable with minimal changes:

  • DAC Extensions and custom fields
  • Graph Extensions and business logic
  • DAC attributes
  • Server-side PXActions
  • Business logic implemented through C# events

Typically require review or redevelopment:

  • ASPX page/layout customizations
  • Classic UI-specific PXControls
  • Custom JavaScript that relies on DOM elements or generated control IDs
  • Client-side grid customizations
  • Custom Classic UI controls
  • Classic UI-specific SmartPanel/UI behavior

The biggest challenge is generally Classic UI-specific JavaScript and UI customizations, since these cannot simply be carried over to Modern UI and may need to be rewritten using the Modern UI/TypeScript framework.

I would recommend auditing each customization and separating business logic/data customizations from UI-specific customizations before estimating the upgrade effort.

Hope this information helps!