At least it was only one division. Iām not going to have anyone switch until I can use the web browser exclusively at least three months without any issues. Thank you for putting in the work to get those problem records created.
I think there have been enough posts like this that anyone who frequents this form should know to be cautious about implementing Kinetic UI.
Our expectation was that not everything will work. Itās new. We decided to use Kinetic screens but if the functionality wasnāt up to classic or there were bugs, then we also have that classic screen on the menu. We have some users who still use the Kinetic screens while others use the same classic version. This gives everyone the experience of what is coming while still having stability.
Thanks for posting this @jkane. And sorry to hear about the massive data loss issue. Iām surprised at how upset I am FOR you.
Have you gotten in touch with Tim Shoemaker? Heās heading up the Kinetic Adoption group and should be aware of all of this so something can get done instead of waiting.
This is a big one for me. My whole thing for the last six months is ādrag and drop it into Epicor and plug in any metadataā. Like, upload the supplier cert and type in the expiration date. Iāve even been driving some BPM logic off of it.
Itās been wildly successful. People actually, legitimately love it. Any step backwards from that simplicity is going to be rough.
Big Brain: Keep things server side to separate UI from business logic.
Bigger Brain: Keep things server side to ensure an easy transition from rich client to browser.
Galaxy Brain: Keep things server side so I donāt have to learn Javascript yet.
Weāre in this same boat right now moving from E9 to Kinetic. This has been a big discussion for us. Weāre really pushing hard to fully deploy the kinetic version, but itās been frustrating at times. There are some nice features that we like, but other areas itās quite a struggle. Weāre concerned if we allow both classic and Kinetic screens people will never want to migrate away from Classic. For those of you doing a mix of screens, have your users been open to both?
We do have some users that have switched to classic on a few more screens and others who like Kinetic better. Everyone knows the clock is ticking on classic and we constantly remind them that the plug will be pulled eventually. People using just the browser love the performance. In the end though, we need Kinetic to be as good or better than classic to get buy-in.
Are you using a web browser directly, or whatever the client uses if you open a Kinetic screen? Iāve found its MUCH faster if you are operating directly in your web browser of choice vs letting the client open whatever it wants.