When I package a file located in “FrontendSources\screen\src\development\tenant\screens\”, it appears in “Modern UI Files.”
The recommendation for new screens that are converted is to place the .ts and .html files in “FrontendSources\screen\src\screens”, but these files do not appear in “Modern UI Files” due to their location.
If I move the .ts and .html files of these new screens to “FrontendSources\screen\src\development\tenant\screens\XX/XX000000” and publish them in another instance, the screen is not recognized, and the issue is that after publishing, the screen appears blank.
Answer
How to export Modern UI from a screen created from scratch in 25R2
Best answer by Vignesh Ponnusamy
Hi
In 25R2, to be able to add the files to the Customization project you have to have the Modern UI files in the following path, FrontendSources\screen\src\development
When you publish the package in another the Modern UI files will be automatically placed in the following path, FrontendSources\screen\src\customizationScreens\{tenantName}screens\{Module}\{ScreenID}
From you comments, I see you have the tenant folder within the development folder which might be causing the issue here.
Few other recommendation you can review,
- If you are developing an extension for existing Acumatica screen. The files should be placed in the extensions folder of that respective screen. For example, if you are developing an extension for RQ301000 screen then the files should go in the below path
- FrontendSources\screen\src\development\screens\RQ\RQ301000\extensions
- If you are developing a custom screen in a custom module, make sure you have two character folder name for the module. For example, right structure will be
- FrontendSources\screen\src\development\screens\TT and not FrontendSources\screen\src\development\screens\TTT
Hope that help! Please feel free to back post if you have any question! Thanks,
+15If I move [them] and publish them in another instance, the screen is not recognized, and the issue is that after publishing, the screen appears blank.
Have you checked the site map to make sure that screen is configured to use the Modern UI? If you have no ASPX files, it may appear blank. As far as I know, customizations use the Classic UI by default.
How can I make this screen appear in Modern UI Files if the .ts and .html files are located in FrontendSources\screen\src\screens?
+15You can’t. From what I’ve gathered, you’re expected to develop them in /src/screens/ and then when they’re ready, move them to /src/development/screens/
Daryl⚡Freelance Acumatica developer (MVPx2🏆) ⏩linkedin.com/in/darylbowman 🛒store.deftstrokesdev.com
+5Hi
In 25R2, to be able to add the files to the Customization project you have to have the Modern UI files in the following path, FrontendSources\screen\src\development
When you publish the package in another the Modern UI files will be automatically placed in the following path, FrontendSources\screen\src\customizationScreens\{tenantName}screens\{Module}\{ScreenID}
From you comments, I see you have the tenant folder within the development folder which might be causing the issue here.
Few other recommendation you can review,
- If you are developing an extension for existing Acumatica screen. The files should be placed in the extensions folder of that respective screen. For example, if you are developing an extension for RQ301000 screen then the files should go in the below path
- FrontendSources\screen\src\development\screens\RQ\RQ301000\extensions
- If you are developing a custom screen in a custom module, make sure you have two character folder name for the module. For example, right structure will be
- FrontendSources\screen\src\development\screens\TT and not FrontendSources\screen\src\development\screens\TTT
Hope that help! Please feel free to back post if you have any question! Thanks,
+5
#VP
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.