Of course, everyday <> Six Months. Right?
2 Likes
Hmm… I have a different take. We would have been comfortably waiting in 10.2.700, running dot release patches as needed, waiting for a much more complete version of Kinetic instead of wasting 18 months of testing, trying (3) iterations of Kinetic, just to prove that their release has been premature.
7 Likes
Touche! 
Is it the frequency or the number of changes per upgrade? 
1 Like
There we are, nice point.
True. An always brighter side to look towards…
1 Like
I would argue differently. If every two WEEKS there was a release with just a few fixes and a new feature, it would be so much easier for you to test with a lot less effort. Epicor would get feedback right away and it would be easier to change then instead of scheduling for 202X.Y. Three iterations is what is causing the pain, IMHO.
1 Like
We are browser-only. We have been live for almost 3 weeks. Without a doubt, the BIGGEST challenge is Epicor’s internal Quality Assurance with regard to page caching, page loading, custom layers, and all things related -and when they release something not fully tested (IMHO).
I give it a solid 7 out of 10. I know it will be amazing … even as soon as they fix this stupid caching issue, endless spinning wheels, and make the dashboards be able to be sortable across non-native tables without downloading everything first.
We HONESTLY spend more time dealing with innate Epicor issues than anything else. We have numerous work-arounds, published EUPs, and band-aids in place - all related to an issue we shouldn’t be having. This has cost us months of time “figuring and testing” over the last 15 months.
When Epicor is firing on all cylinders, it’s fast, and it’s great - when we are in an endless load, cache-issue, or base vs. customized layer mix-up issue; well, it drives everyone in the company nuts. Related; we also resorted to putting TITLES on our custom layer pages to make sure our reps and users know they are on the correct screen and not some base-layer fallback mixup that happens all the time right now.
That being said, again, I know that when they get this cleaned up, it’s going to be great; wading through the swamp right now is tolerable at best.
Good hunting all and THANK YOU to all the users here, it’s made our life way better with regard to all things Epicor.
11 Likes
Thanks for the feedback and helping other users understand the current landscape as most on prem users are trying to figure out when to upgrade and how (mixed forms, all kinetic, all classic).
1 Like
Not this again 
, this is how we lost the 
10 Likes
A post like this keeps me going… (the feeling of not being alone)
5 Likes
I’ve had that feeling since we went live…not enjoyable by any means
Coming here? People helpin people, or at least sympathetic to our causes
2 Likes
But you gained an 
!
1 Like
It would have been better if I had earned it.
An empty medal for a battle lost.
4 Likes
I thought we could just add as many as needed like discord or something. I didn’t know there was a limit!!!
1 Like
There might not be a limit per se… just a preference for uniformity and symmetry 
You just have to plead your case.
3 Likes
There is no real limit, other than what can reasonably fit in the pop up window.
2 Likes
enjoy 
8 Likes
Seeing a handful of comments here mentioning Epicor ending all access to Classic UI in the coming 2024.2 update, and forcing browser kinetic UI only. Is this true? If so, can someone point to some kind of official confirmation of this? This would be a huge deal for a lot of companies, I would be surprised if they forced everyone’s hand this quickly when so many issues are being experienced by Kinetic UI still.
There is another thread discussing it and it got pushed to 25.1
3 Likes