We’ve been live with Kinetic 2024.1 browser-only for a couple months and have many issues. We’re considering reverting to use the client to see if that clears up any of the issues. Anyone running browser-only 2024.1?
2 Likes
No, not yet.
2 Likes
Yes. The 2024.1 update did create a number of issues… several posts on here about some of them. I would wait before making any hard decisions to retreat until they push the next update which should (hopefully 
) correct some of them.
2023.2 was pretty stable and we’ve been live on browser-only kinetic since early last year. Huge progress along the way. But again, this latest update is buggy.
6 Likes
I’m trying to run browser only just by myself before it gets inflicted on the users. I still haven’t heard confirmation if Epicor is still planning to force that in 2024.2 or not.
I also experience constant issues with it but I think its too late to put the genie back in the bottle. If you’ve got users on the browser no point putting them back on the client only to turn around and put them back in the browser in a few months. Just keep logging the support cases or else it will still be just as bad when you have no choice but to use the browser. At least now you can still fall back to the client in an emergency.
2 Likes
Are you fighting anything specific we can help with? (or at least join in with you on the specific pain point, haha).
Misery loves company!
3 Likes
*no choice… well, the bugginess has caused the owners and management to begin shopping for another ERP.
I’ll keep logging cases, but man it is so often a slog, esp with the issues that we can’t get to consistently repeat.
5 Likes
Nothing you can do about that. Even if a decision is made to implement a different ERP, that is a months or more likely years long path and in the meantime you will still be keeping things running on Epicor.
1 Like
Thanks. I get pulled in so many directions, trying to prioritize the issues. Our users are clearing browser history like there is no tomorrow, giving them some relief for a few hours or a couple days.
Most recently our shipping department has increasingly been receiving the “Edge Agent Not Detected” message on all their computers (we daily reboot and clear browser history). This comes after many print jobs on the same computer, then suddenly the message. The printer box spins and spins, they can’t get it to go away, so a full computer reboot and reboot of printer. It gets them back up and running, but now it is almost a daily basis.
5 Likes
Yes, understood. I’m wading through PDT, trying to find anything that may be adding to the static.
1 Like
I have given up on edge agent. It’s honestly less trouble to just print preview and then print from the pdf viewer than to keep dealing with that nonsense.
10 Likes
2 Likes
But, isn’t it needed to find local files for adding attachments to records?
1 Like
Yeah I think so
1 Like
We went through the same issues with ours for a while (2023.2.11 on-prem 3P-hosted). Edge Agent was wonky for individual users but not everyone…and was completely random when it did. Clearing cache (all-time, not just last x minutes/hours/days) and reboots were the common solution/workaround. Something in Edge Agent just doesn’t play well with others…and isolating is difficult.
Theoretical: if everyone’s running the same version of Edge Agent, maybe it drops down into each user PC…browser type, browser version, OS, patch level, printer driver, available memory, etc?
2 Likes
We’ve been browser only for about 6 months now. Initially, we also started on the client and we had a fair amount of issues with it that were slowing down our implementation a good bit. Our userbase wasn’t super thrilled with it either, and constantly chasing fresh installs and updating clients that fell out of cadence was pretty time consuming.
The browser version definitely has its fair share of bugs that can be a pain sometimes, but in general it’s worked better for us as a whole and the users seem to like it a lot more just because of the ease of access. A lot of the day-to-day tasks they do interface with the web also, so it’s nice to just click a bookmark and log right in.
I definitely agree that the Edge Agent has been one of our biggest pain points. We too have gone the route of just previewing and printing/downloading the PDF because the EA works great UNTIL it doesn’t. Trying to figure out the root cause and remedy it on multiple machines all at once was definitely a mess.
Otherwise I’d say it’s a solid 7/10 overall so far. (For now 
)
9 Likes
We’re browser-only…sorta…would be 8-8.5 I guess.
Except for the stuff that isn’t available in browser yet (Citrix/client for those).
And those occasional glitches where screens randomly fail to load and you have to do the AppStu workaround (open base layer, then exit without saving).
And for BAQ Designer, cuz the browser version’s a little rough on my old eyes.
2 Likes
Let me clarify, I personally do most of the time unless I need to use one of the screens that isn’t kinetic yet or has a huge bug, but I use browser almost 95% of the time probably.
4 Likes
All of our UAT testing with browser-only went pretty well, but once we went live and had the whole business using it is when we started seeing an avalanche of bugs/issues.
5 Likes
Can you elaborate?
Also are you excluding the row has been modified by another user from this review or is that part of the avalanche?
1 Like
We have had this too, but we quit the edge agent from the system tray, restart it, then close epicor and re-open.
1 Like