Epicor Classic Screens

Kinetic ERP
1

For those of you who also are stuck on Classic screens and don’t have resources to upgrade to the browser interface, vote in the Epicor Ideas Portal to let Epicor know! They have announced a sunset date of about a year from now for the classic UI. Epicor Ideas: KIN-I-6289

Here is what is hindering us from changing:

  1. There is functionality that is missing in the browser UI that is essential for our organization (reports, screens, reliable printing, etc).

  2. The browser UI is non-intuitive for our users with a very different UI from what we are used to.

  3. The browser will require extensive retraining and IT overhead where we do not have resources to support this change.

  4. Many day-to-day tasks require extensive retraining to figure out how/where to find them.

3 Likes
2

https://epicor.ideas.aha.io/ideas/KIN-I-6289

3

While I agree they should delay a tad bit longer, you’re probably not gonna get far with this.

We’ve all known this was coming for a while.

:people_hugging:

7 Likes
4

I agree that it still needs work, but keep posting here about what you are needing and they are listening to what needs to get corrected. I was on the 25.1 webinar today and they are committed to the timeline.

I did a sandbox to 24.2 last weekend and am going to evaluate where we stand as far as readiness before Insights.

2 Likes
5

Yeah, it’s a pretty discouraging situation here. I’ve been sending out the alarm how urgent this is, and how much work needs to be done. Management keeps making decisions to continue to add more features to the classic UI customizations, which just deepens the technical debt. I keep trying to work on converting everything to the browser, but am continually get pulled off of it to work on other things.

11 Likes
6

GIF by Amazon Prime Video

4 Likes
7

Thats kind of where we are at also. Not sure if management understands the potential amount of work it will take to make the browser work for us.

8

One thing you can do right now is to expose people to the browser for trackers, which generally have fewer customizations. Two of the three items listed were about training. Keeping people on the client and “protecting” them from the browser will not ease the pain. Our people have seen what the browser will look like for two years now. We have about a dozen customizations remaining to uplift and only two or three are heavy with client-side code. The users who use the browser for CRM, payroll, Intranet, etc. are pleased they won’t have to open another app.

But Epicor does need to address your first item, or it’s going to be a real :dumpster_fire:.

2 Likes
9

So… tell them no?

Also… management knows what Epicor is?

I am fortunate in that:

  • First few years here: management didn’t care what Epicor looked like and I had omnipotent authority over it
  • Last few years here: management cares but totally supports modern UI and software upgrades and tells everyone to get on board with the future
8 Likes
10

Perhaps compile a list of customizations that will not work as-is in browser and ask them which of those they are willing to give up so that they can have their new customizations that will only last 12 months or less, before they all expire along with the rest of the classic screens…

Easy for me to give such advice from this side of the keyboard :sweat_smile: it’ll take guts, but they have to accept the truth or drown in delusion

5 Likes
11

I laughed at your “tell them no” suggestion, but I guess that’s effectively what I’m doing. I stopped my HSA contributions last month. So, in 5 more months I’ll be in a position to apply for Medicare, start taking Social Security, and give them an absolute no.

7 Likes
12

Good point. Customizations fall in two classes…need-to-have and nice-to-have. If it’s something absolutely required to do business, they need to be focused upon. If it’s something that might take a couple extra mouseclicks going forward, that’s not mission-critical.

Drowning Thumbs Up GIFs - Find & Share on GIPHY

2 Likes
13

Enter a support case for every single thing. Use the word parity. When they tell you to make an idea, then make an idea and share it here so we can vote for it. They aren’t going to address gaps that nobody complains about. This will be a lot more effective than trying to convince them to abandon kinetic altogether.

Yeah but honestly you can overcome this. Its not THAT different. All the same stuff is there, you basically do all the same things in the same order, they have just taken what were horizontal tabs and turned them into vertical navigation. At the same time they have added Explorer cards, and a field search, which are both big improvements over what you get in classic.

If you space it out, its really not that extensive. Just take one major screen at a time. The more screens people get used to using in kinetic, the easier it is to adopt the next one.

I have not found this to be true. All the “actions” are now in the overflow. Everything else can be located with the field search.

10 Likes
14

What will they do about DMT which has no browser-based counterpart, and relies heavily on the same files as the smart client to function?

15

They are releasing a set of “Power Tools” that include that.

2 Likes
16

Just latching onto this comment, has anyone seen a post on here that lists out these things, i.e. where the functionality in browser does not match classic. I’m not thinking about where Classic ‘does it nicer’ but just where ‘browser just can’t do it’.
I feel like they come up now and then in separate posts but would be interested if anyone has compiled a list in one place that can be shared. That would give us all a useful checklist, and remind us to raise cases/vote ideas.

17

That would be a very long list.

3 Likes
18

Barry,
Here are a couple specific issues that I have seen so far where the functionality doesn’t exist currently (although hopefully Epicor will fix prior to May '26).

  1. DMT DMT for Kinetic Browser | Epicor Ideas Portal

  2. Conversion Workbench for Epicor Express Conversion Workbench for Epicor Express | Epicor Ideas Portal

  3. Epicor Configurator (Doesn’t natively work) Epicor Configurator For Browser | Epicor Ideas Portal

2 Likes
19

“Tell them no”, one of the best ways to trigger a resume generating event.

I understand the love for Classic, I really do, I was right there with you all on it for a long time. I didn’t even go with the ‘Modern’ menu option when they gave us that, I stuck with Classic and the last time before we went Kinetic-Browser with 2024.1 I even disabled the ability for anyone to even choose Modern and forced the Classic Menu so as to not have to support the two menu versions.

All that being said, Kinetic-Browser definitely has its flaws and it’s missing features (I speak of 2024.1 with little knowledge of the future many are living in with 2024.2) but once you actually use it, and I mean really use it, it is not so bad. It will seem slow and cumbersome at first but that is almost 100% down to pure muscle memory, the same number of clicks are required to do most things, it is just now you will need to think about them as opposed to your arms moving automatically.

I can almost guarantee at this point that no amount of ideas and votes will push back the end of the smart client and ultimately classic so you really do need to focus on either drawing a line int he sand and sticking with a version that gives you want you want and forgo any future updates, switching to another ERP system that will have far more challenges like those outlined above or accepting that you cannot roll the rock up the hill for much longer and stat migrating people/departments/screens/etc to the Kinetic and ultimately Browser UI.

When we made the upgrade to 2024.1 we were 100% Classic, not a single Kinetic screen in sight, we started testing/training in May 2024, went live at Christmas 2024 and now in April 2025 we have 2 screens that remain on Classic, one of which will be turned off May 1 and the 2nd, an updatable dashboard that has some consultant created Base Method code that will likely require them to troubleshoot a specific issue in the Kinetic version.

Most feedback, once everyone gets past the WTF moment and has used the system for a month is that it is fine and they don’t really miss classic.

The major gripes at this point for us are:

  • Grid filters that you can stack (seemingly being addressed in 2025.1).
  • Grid filter against other columns int he grid.
  • Color options in Row Rules that you can distinguish and that make any kind of sense at all.
  • The ability to retain those colors when you export to excel.

I’ve managed to work around all of the Kinetic Configurator oddities and while painful to learn how to get around the ridiculous regressions from classic, once you know what to do it is pretty straightforward.

7 Likes
20

Lol, this doesn’t work. I tried that on my last one and still had to fight to get it pushed through.

2 Likes