I’m in the process of converting custom screens from classic to modern UI for 26R1. Some of these screens are primarily used by shop floor employees via the mobile app.
Is there anything special I need to do for that, or will they still keep working?
Are there upcoming changes that will require updating the mapping to accommodate the move to the new UI?
I haven’t been able to find answers on this.
Solved
How are/will screens mapped to the mobile app be affected by the switch to Modern UI?
+8Best answer by MichaelShirk
Based on the 26R2 documentation, the MSDL scripting does need to be updated to work with the 26R2 release. I’ve updated the “Best Answer”.
Copied from the Release Notes:
“The Acumatica mobile app connected to Acumatica ERP 2026 R2 switches from using the names of containers and fields from the WSDL schema to using view names and DAC fields. As the result, the way you refer to the fields and containers in the mapping has changed, and MSDL scripts may not work as before.
If your customization project contains MSDL scripts, you need to update them to use view names and DAC fields.”
Hello
When it comes to mobile app, it would remain as it is. But there are screens where both web and mobile will be used (Ex: Uploading purchase receipts) So the web interface can have some changes with modern UI.
Changing screens from classic UI to modern UI can be done through the site map.
Hope this helps.
Thank you
Hi
your existing mobile app mappings should continue to work. The mobile app layer is separate from whether the browser screen is rendered in Classic UI or Modern UI.
+5
WSDL schema could be different for classic and modern UI, and when your customization contains both classic and modern UI definitions and you create/customize mobile screen, (25R2 onwards, I believe) system prioritizes modern ui wsdl schema for mobile.
If only classic ui(aspx) exists in the system, mobile picks up classic wsdl schema.
As far as development/customization is concerned, I think you should take this into consideration.
maybe
+8Based on the 26R2 documentation, the MSDL scripting does need to be updated to work with the 26R2 release. I’ve updated the “Best Answer”.
Copied from the Release Notes:
“The Acumatica mobile app connected to Acumatica ERP 2026 R2 switches from using the names of containers and fields from the WSDL schema to using view names and DAC fields. As the result, the way you refer to the fields and containers in the mapping has changed, and MSDL scripts may not work as before.
If your customization project contains MSDL scripts, you need to update them to use view names and DAC fields.”
Login to the community
No account yet? Create an account
Social Login
Login with your Acumatica accountEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.