I’m sorry if I came across as victim blaming. It sounds like you tried your best and did your due diligence and you still got burned.
I hope Epicor makes it right with you. 
3 Likes
No, no it’s good (my first thought, however, was “Is this an Epicor employee?”). 
It is easy to come here and complain (strangely, I find relief by browsing this forum when I’m having a frustrating Epicor day). My initial question was really me trying to figure out if I should try and reel back browser-only to mixed-mode in order to gain more stability.
Recently we’ve had a couple of Epicor employees say things like “We have thousands of customers that have no issues” and “we have not heard of these issues before”, yet I come here and find most of our issues, in one way or another, represented.
Our staff has been doing their best to handle the daily (hourly sometimes) browser history clears, the mysterious error popups, random bugs, etc. I’m hopeful that case-by-case these things will get resolved, and hopefully before every case comes back with the “upgrade to the next version” statement.
4 Likes
Preach on. We haven’t had the levels of issues that it sounds like you’ve experienced but we can all sympathize. Our environment is pretty vanilla except for a handful of areas (mostly compliance/customer-related…EDI, labeling, etc).
There does seem to be a common ground that we’ve all experienced with support (“we cannot replicate at will” is the one that really drives me bonkers batspit crazy)…but not all support experiences have been negative either.
I’m glad we’re hanging at 2023.2.11 for the foreseeable future. If we have to wait things out and keep doing the workarounds/datafixes, at least we’re able to conduct business.
2 Likes
If we don’t complain, and also the opposite, praise, then they don’t have the information they need to make the software work well.
Everyone just needs to remember to be civil and fair in your complaints, and to give credit when credit is due for the wins.
5 Likes
I’m not sure if I’d go to two years, but I think less frequent would be good.
Twice a year is too much. (To be honest, on us and them)
(Security and bug fixes excluded obviously)
You love us…
3 Likes
The tl;dr for the article:
Firstly, most of these tasks become much more difficult as the amount to do increases, but when broken up into smaller chunks they compose easily.
Big ugprades suck. Always have.
Feedback is a second reason
Now you’ll have to wait two years for a feature, year one to develop it and wait until next year for the improvement, and maybe a third to get it right.
A third reason is practice.
Practice makes us better and the more we do it, the better chance we have at automation.
Some of the pain we felt when first going to cloud was we trying to do everything the same way we used to, or trying to remember what we used to do. Year End close, an annual Physcial Inventory is always an adventure because we forget how to do it.
2 Likes
I’m familiar with the concept, but there is a limit, and I believe it’s been exceeded.
Now that’s just my personal opinion, and I know what I can potentially do with it.
3 Likes
I don’t know that the frequency is the main problem. Its biting off more than they can chew. I want to see increasing stability, decreasing bugs, and feature parity with classic. A lot of the development seems to be focused on new features instead. And its a struggle to even get development to look at the bugs because support won’t submit them.
7 Likes
I thought there would be a 1 year warning to get rid if Classic. Is this a new thing, not allowing client ?
1 Like
We are referring to the browser first initiative. You can still get to your classic forms, but they would be launched by the edge agent.
The login would be browser only.
2 Likes
I am a big fan of an Electron Client to separate ERP from Browser. Then you can control how hyperlinks open and have access to the OS layer, with ability to build a plugins ecosystem and tap into Chrome Extensions.
Everyone who has a web-version still came out with an Electron or PWA App.
- Outlook
- Slack
- Telegram
- Messenger
- Discord
- Postman
- Asana
- LucidCharts
- You name it…
For those who complain, please remove all PWA and Electron Apps from your PC, use Chrome exclusively.
In short Kinetic Community Client is in the works 
Where is Kevin to help.
Very Old Prototype
(Classic style toolbar relays click events to new toolbar which is hidden), not that I would build it this way, but the idea is that we can make even a tabbable UI with color coding for Menu type what not if we want.
4 Likes
Great, Having issues with Edge agent in RSD environment( have been for a while) …argggggg
The problem, I suppose, isn’t the frequency, per se, but the instability that arises during Epicor’s frequency. We work with many other software packages that have similar cadences, but inject nowhere near the amount of labor on us, the customer, to test, debug, troubleshoot, report, argue, escalate, etc…
The article cites, “Continuous Integration by integrating every day, the pain of integration almost vanishes”… not feeling it with Kinetic.
5 Likes
Oh god, my javascript is only passable at best, and they just made me management.
You may be on your own… but I wanna watch!
3 Likes
The new Teams client switched from Electron to WebView2 and it’s much faster. Thoughts?
When @klincecum takes charge…
7 Likes
WebView2 is very fast… Epicor uses EO which is using CEFSharp once we switched to WebView the speed increased like 10x.
3 Likes
I wish we had the flame icon as a reaction 
3 Likes
But to Mark’s point, imagine if they didn’t do it this frequently and did everything they’ve done over the past 3 years, but all at once. I’d pass out haha
1 Like