In the Application Studio app, clicking the plus button in the top right-hand corner allows you to create a new Kinetic application from scratch. Normally, I would generate a dashboard then customize it with a layer. When I’m ready to move it to our live environment, I use Solution Workbench and select the dashboard definition and the Kinetic customization layer.
However, in one instance, I did use the new application button. This is nice, as it generates a clean palette for me to build upon, without all the extra dashboard events I need to cancel or workaround. I was a happy camper up until it went to exporting the application: Solution Workbench doesn’t allow you to include Kinetic apps (that I’m aware of). Since I had put so much work into the application, I resorted to a hacky way of grabbing the application’s JSON and highjacking a SaveApp call in the production environment to successfully import it.
So, should I not be using the new application functionality in Application Studio if I’m not licensed for the SDK? Why is it available if the application can’t be exported? What am I missing?
No that looks good. I think as long as you get everything that matches in Key1, then as long as your type is KNTCMetaUI and KNTCUDApp, you should get everything.
Thanks. Any thoughts on what namespace and naming conventions user created apps should use? The first one I made was in Ice.UI, but I now feel like that could have been a mistake.
So, I took another look at Application Studio and found that they have added Import and Export functional in the grid actions menu! They appear to be working.
Thank you! Nice find and it exported without a hitch. I did not pull it in yet. I am building a list of what to do for when Epicor sunsets customizations and this was one of them.
