Dear All,
I hope all is well.
I have a question regarding Kinetic upgrade from Epicor 10.2.700.
Could I easily migrate all my customizations which were made in E10 to E11’s new UX? Or should I recreate them from scratch?
Please keep in mind that my customizations sometimes reach 2000 to 3000 lines of code.
Any information you can throw my way regarding this topic is always appreciated.
Kind Regards,
Aamer.
It should migrate seamlessly to classic UI
To the new UI NOTHING will migrate you’ll have to recreate it.
Sounds like there is too much business logic in those UI customizations. Consider moving that logic to Epicor Functions when moving to the new UI.
I do everything I can in the backend, but some things just can’t be done in the backend, or
the current Kinetic UI.
I’m scared to death.
I’d agree that we can’t do everything the same way in current Kinetic UI. But often this gives an opportunity to rearchitect the solution that is web-friendly and adds more value.
Get back to me when I can easily add some javascript to the kinetic ui.
We have been able to do everything we need without JavaScript
It just takes some refactoring and moving things around
Can you add JavaScript though? I’ve been exploring the Application Studio for the past couple of days, and I haven’t found a way to add code in it.
The Application Studio seems to me like glorified BPMs on the application layer, without the ability to write code, and it is frustrating.
No… Well, technically yes but it is not supported and will eventually be patched
But again you can do pretty much everything you could think of with a little creativity
I’m going to ask why do we want to add business logic code to the UI layer? Like Jose said, with some creativity we probably can add JavaScript, but should we? It seems that the current situation would have been a lot less challenging if non-UI related code was moved to the server back in 10.x.
Besides maintainability and testing, one quickly finds that adding non-UI code to the client will be less secure. One will most likely leak secrets (credentials to external resources or Kinetic API keys) since it’s impossible to hide them in client code.
Many have found the Clean Architecture/Onion Architecture/Domain Driven Development programming method very helpful in writing code that is easier to test, easier to maintain/upgrade, and easier for the next person who has to deal with it. Here are a few links I have found useful:
Clean Architecture with ASP.NET Core | Blog (ardalis.com)
Onion Architecture | Programming with Palermo (jeffreypalermo.com)
Best Practice - An Introduction To Domain-Driven Design | Microsoft Learn
I worked on a pharmaceutical solution when I first started, and I got familiar with customizations a lot faster than I did with BPMs, and due to time and management pressure, I had to finish the work with the fastest way possible, and that was with customizations.
That’s why there is too much business logic on the UI layer.
Huh, well, I believe I need to recreate my logic in either BPMs or Epicor Functions then.
Thank you for your help.
You are not alone. We’ve all been there.