We have upgraded (TEST) from 10.2 to 2023.1. Trying to get a handle on the process for converting customizations, since they did not appear to convert to the Kinetic UI.
As an example, we have a customization ABC on the sales order entry form. The customization has three UD fields, one of which is required.
The conversion workbench error says that the conversion failed because the layer already exists: ABC. Customization conversion failed with an error: LayerName ABC already exists… [, App.SalesOrderEntry.SalesOrderForm, , , EP, Customization]
I can launch the customized view from the tree, but only in classic UI.
My assumption is that the UD fields must be added via Application Studio to the Kinetic UI. I can do that, but… does that mean we are now maintaining two versions of the customizations – one for each UI? Or can I give the new layer the same name and will Epicor understand that they go together?
I have not yet found an example of linking the classic UI customizations with their Kinetic UI versions, if that is possible.
Yes you have to rebuild the customization in a kinetic layer (imo trying to work with the broken conversion attempts is not worth it).
No Kinetic will not understand that the classic and kinetic layers go together for the same program. You either have to force everyone to use kinetic (by switching the menu item to kinetic app and attaching the kinetic layer), or else have two separate menu items, one for your classic program with classic customization and one for your kinetic app with kinetic layer attached. Or third option, leave it in classic only and hope that Epicor improves the transition capabilities in a future release.
Ouch. For example epicor contains 10 Part screens and if we use different customizations on them due to different user groups assignemts, this means I need to create 10 copies of screens for kinetic. Awsome
I had written that answer when we were on 2023.1. This is much improved in 2023.2 when the “browser first” functionality was added. You CAN now add a kinetic and classic customization on the same menu item.
How? I can not. Kinetic customization field grayed out because application type is “menu item” and if i choose “kinetic app” then i can not add clasic customization and documentation says the same:
When I am in kinetic menu maintenance, and I have a “menu item” with a classic customization attached, I am able to browse and also select a kinetic layer to attach - its not disabled even though it does look sort of grey.
Right- in my case, it was a pre-existing classic customization, so it had already been copied to the current company and I was just adding a kinetic layer on top. If it was a standard menu item it would have to be copied first.
Well in my case it is already copied I had classic customization and converted it to kinetic but I am not able to see any kinetic layers (picture bellow) until i change program to kinetic app but after that I am not able to add classic customization
This does not help also, yes it is published did this 4 times might be it is search issue because classic customization search does not show anything also I need to type customization name manually
Ok found issue when i used conversion workbench it converted customization and assigned it as company specific and since menu contained checkbox “All companies” customization was not visible in search
because classic customization search does not show anything also I need to type customization name manually