This wouldn’t fall under the “Who Moved My Cheese?”, but rather “Who STOLE My Cheese!”
And just taking the day off from my regular job. I got so much unused vacation that I’ll lose at the end of the year, that I end up taking every Friday in Nov and Dec. And a week for Thanks giving and at least another week around Xmas.
He still lives on, since any time you search ANYTHING you will invariably have this post in your results.
If you know, you know.
Well, I reach my Social Security FRA in February 2026, so at least I have an option. 
With so much still broken or a hot mess, this sounds like a fantastic idea.
No pressure, no diamonds
I’m on the cloud now too!
Oh no you don’t. Get back here.
We understand the importance of this topic to many of our customers and appreciate the engagement. We will provide an update to Kinetic users early next week with more information on our roadmap and continued investment in delivering an optimized, flexible, and easy-to-use experience.
I ran into a few of those in my conversion of our Classic dashboards to Kinetic. The good thing was they weren’t important columns in my BAQ so I was able to remove them and get the application to work.
We went full browser about a month ago, moving from all Classic/client on 10.2.700 to 2024.1, while also moving from a hosted service to on-prem. I personally find it much better and greatly look forward to being able to fully use Data Directives, uBAQs, and DMT in the browser so that I rarely ever need to sign into our server to do something.
For those of you who are bemoaning going from the client to the browser, from a user standpoint I can tell you that our users love it–most of them didn’t even do the “mandatory” training I assigned them in preparation and the switch was a shock, yet they still like it. It’s much more convenient, noticeably faster, and overall everyone likes the look/layout.
That’s not to say that it doesn’t still have its limitations and frustrations (why are grids still so finicky?!?), but they at least make a lot of effort to listen to us all in improving it.
This thread was started with incomplete information due to a partner releasing details ahead of schedule. To ensure our discussions are based on accurate and official information, we’re temporarily closing this thread until Epicor releases the formal announcement. This upcoming announcement will provide more comprehensive information, facts, and guidelines.
Speculating on what is or isn’t happening won’t help until we have the facts. Once the official customer announcement from Epicor is released, we’ll reopen the conversation so we can all engage with full understanding.
In the meantime, I’ve marked @timshuwy’s reply as the solution for now.
Thank you for your patience and understanding.
See:
