Our “core” issues include excessive “row has been modified”, very random “logged out for inactivity” (even when in the middle of working), “spinner of death” (many grids randomly spinning and spinning, never to load the data), grids with personalization setings regularly lose desired order and/or the display of added field (clear browser history/refresh to fix), “long running process” message when user didn’t run anything / no known process running.
Other issues include sums on some grids not accurate to the data dislayed (e.g. job completing/closing calculates the sums from a previously loaded job#, causing much frustration/doubt. Open orders for customers in grid sometimes not displaying the same results for two different users (clear browser history, refresh, then it matches). When running multiple filters on dashboard, results sometimes not accurate (users now export all results to Excel, then find/filter/sort for accurate calculations). Part Advisor / Job Closing regularly missing needed columns/data (clear history / refresh to see). Popup window “open in a new tab” stays displayed on home screen, eventually blocking the buttons, requires refresh… that’s a skim of the list.
Yeah, it’s been strange. I like the direction of Epicor, and probably 95% of the system works well, but these issues, along with those I didn’t post, have really shaken internal confidence.
Yeah I hate that it’s these small things that shake the confidence when 95% of it is by all means an incredible achievement. You think about how many companies use this ERP, how much money rides on this thing and how they’ve been doing that successfully for years.
I wish that we could clearly communicate these things too, it’s hard to do in a ticket every time without it taking 30 minutes to clearly capture and explain. And some things you just can’t explain and there’s not much help after that in my experience.
All day every day. Have a ticket open now I am trying to push for some kind of answer on. It should not matter that I can’t reproduce it on demand. Its a real problem and if I take all users to the browser they are going to absolutely lose it having to login in/refresh all the time.
Yes but both of these happen in the client when using kinetic too. Worse is the personalizations that get corrupted and then have to be deleted and there is still no purge program.
This is a bug that is supposed to have been fixed
Just got this accepted as a problem yesterday
Keep logging those tickets! It’s not going to get better if we don’t persist in reporting the issues.
Why did you guys migrate so early? I’m waiting until Epicor tells me I need to or till I hear a good report. Not running windows 11 yet either.
Certainly good to start working on things ahead of time, but being an early adopter in a corporate setting seems risky if its gonna go so bad you want to change ERP systems.
Because, the kinetic UI experience is supposed to be better in the browser than in the client, plus you get to eliminate the hassle of installing and updating clients.
What I get from their messaging is they have pushed back the Kinetic only date, and haven’t announced the removal date for classic because they want the majority of customers to have a smooth transition. They aren’t adding new features to classic, because they want people to be putting in work to head in the Kinetic direction.
I don’t think they were trying to put so much pressure on people that they migrated into a disaster when they haven’t even given a deadline yet. I think they are happy when customers are making the switch, but if you aren’t a company that can accept a beta experience I think you should prepare a ton and put it off until you are confident in the product.
I agree with you, I’m just playing the advocate for anyone new who has no idea about the moving safe harbors that have changed quarter after quarter and only sees the generic statements about kinetic forms being the future.
They already conveyed that they would take away the ability to log into the classic client AT ALL as early as 2024.2 (a couple months from now). Meaning the only way to use classic forms would be the extremely-painful process of launching them one by one via the edge agent. That effectively ends classic, for us anyway.
They have already stopped adding critical features in classic (years ago).
They have now stopped fixing bugs in classic too. This is a catch 22 because often when there is a bug in kinetic, they tell me use classic. But now when there is a bug in classic, they are telling me to use kinetic.
So all of that is to say, there doesn’t have to be a hard deadline to end classic. Classic is going away quicker than you think. The transition is harder than you think. Start now because you aren’t going to have as much time as you need no matter how far that ultimate date gets pushed.
Yes, I believe .Net 8 on the server is the reason behind Epicor’s internal versioning of 11.2 to 11.3, but I doubt that has much to do with the rocky start.
Maybe it’s just me but I feel the .1s have been rough, maybe they are trying to push too much in those releases. The .2s have seemed more stable.
that’s what I did, and honestly as @Evan_Purdy said though it was a huge leap of faith and had potential to put me in a very tough spot with the management of the company, but we did it, we went live on Kinetic forms and only switched it to classic when someone absolutely couldn’t do their job.
But they compare it to vantage 8 that had no problems like these so it’s super hard to sit here and advocate for future upgrades given the long list of issues that comes of it, none of which benefit our core line of business.
I just upgraded my dev to 2024.1 and was looking forward to trying to roll that out because we have a bug on our current kinetic version that makes it so they get {strings} messages and unexpected errors that won’t let them open end activity and a bunch of other forms.
It’s just a tough bind and I support Epicor in what they are doing, I’m really hoping we land on a really stable version with nothing brought up like the long list @Adam brought up. I can’t bring those types of issues to them and say it’s for the good of Kinetic. And the edge agent thing like @aosemwengie1 said and many others here is very erratic and I wouldn’t put trust in that as the only thing that makes classic work.
Very true. If I thought it would be smooth and easy I wouldn’t be so cautious.
I’m not completely sure if that is true or not. They accepted a PRB for me that was classic just recently and I still see classic fixes in the latest change log. I have no doubt they have rejected ones you submitted though. They are definitely putting most of their effort into Kinetic. I’m sure they are not a priority, but classic is stable enough that even with very few or no bug fixes I know the business can run on it.
If the experience is that bad, I wonder if it might be possible to leverage the uptime clause in the Epicor hosting and get some kind of discount? Probably not, but ya’ll need to make sure your account managers know how unhappy you are, not just us folks on the forums. If the migration experience is so bad people are considering a new ERP system, that is definitely information that needs to be fed back up the chain.
Nope. The uptime commitment is only a single 9, which is far below anything I have ever seen before. And only FULL downtime counts, i.e., nobody can access anything, not just stuff isn’t working. And the disruption has to occur outside a scheduled maintenance window.
Correction, its not even a single 9, its a single 7.
I appreciate where the new UI is going, and it has made vast improvements, and I certainly recognize that. It still has a long way to go however.
I think Epicor, (as a corporate entity) should put a lot more resources into their development side, and get these issues worked out. I’m sure the coders and managers in these departments are doing their best, but I bet they would do better with some sorely needed resources. I hope they give it to them.
Of course they have, what else would they do? “Don’t use my stuff, it ain’t ready…!” lol
