How Is 26R1 + Modern UI Performing for You?

We’ve upgraded in June and ever since, we are experience massive delays in receiving Bills and Adjustments via an API/Interface set up.  It takes about 9 mins for one entry to import, and we receive errors when the 2nd entry is posted.  This was never an issue on our previous versions.  Any suggestions?

​@rpearson69 
Hi,

We've been on 26R1 with the Modern UI for quite some time and have already deployed it to Production after completing our testing.

Overall, our experience has been positive.

Performance

• Initial page loads after login can be a little slower while assets are being cached.

• Once the session is established, navigation feels more responsive.

Bugs & Regressions

• We noticed some minor behavioral differences with pop-up dialogs and side panels.

• If you have customizations that use Web Forms for pop-up windows, you may need to review and update those customizations to align with the Modern UI.

UI & Navigation

• The interface has a much cleaner, more modern look.

• Improved spacing and readability make screens feel less cluttered.

• Overall, the refreshed visual design is a welcome improvement.

So far, the platform has been stable in our Production environment, and the transition has been smooth after addressing a few customization-related UI changes.

Hi everyone - There is a post that the product and engineering teams are following. You are welcome to participate.

I’m not an Acumatica developer but I support sales and development users by deploying demo and sandbox systems for them to use so I can’t comment on actual feature usage, just server-side stuff.  Loaded some 26R1 Manufacturing on-prem demo systems for our pre-sales engineers and initial loading times of many screens seemed slightly longer, with more complicated screens like dashboards taking up to three minutes to load.  After they loaded and were cached by IIS subsequent loads were snappy but if they fell out of cache it was back to long waits.  The only solution I found for this was to set up Application Initialization in IIS to preload the entire Acumatica instance into cache after any kind of app pool recycle or server restart.  These systems are running both the web and SQL servers on the same system but they are also very well resourced and running on all-flash SAN storage.  I have not tried separating the two (yet) but loading very similar all-in-one demo systems with previous versions never required the use of App Initialization to remediate long load times.