Well Jose already hosed us down, and no one is yelling at each other.
I say leave it be unless it get’s nasty. If I were in Epicor’s shoes, I’d like to know, I hope
that’s how they see it.
I do like this though:
Huh, OK. Even on Epicor’s cloud?
I had recalled a user here (not a regular, IIRC) saying that it was forced, but I guess I believed something on the internet.
Thank you for correcting me on the internet!
I love correcting people on the internet!
They key to my heart is most definitely SFW KEVIN.
Jeez.
And Epicor is the only one that holds it?
It’s highly possible that it’s just the way my mind works.
I’ve been contemplating it there isn’t a ton of value here… but so far everyone is being mostly constructive so. However It is getting close to an echo chamber.
Does someone wanna volunteer to summarize this into a Single Post (solution) of what the ask is and maybe we’ll close it with that as the solution? I don’t really want to continue with Me Toos and I agree it is fairly obvious at this point that most of us agree that Kinetic UX (App Studio) isn’t 100% there yet.
But, hat in hand, what are the specific things we need from Epicor? They are already working on fixing most of the issues they are aware of and 2023 is leaps beyond where we started. So what is the ask?
Parity before Expansion.
Documentation that is accurate is number one on my list. Aside from any bugs, just knowing what I am doing is key and a bunch of nested freeform textboxes to plug “???” info into is not useful.
A set of labs that walk through common situations and needs and importantly they get updated if they steps change. (Also, if there are 3 different ways to do the same thing, show me all 3)
If we can get that, I can suck it up long enough to be useful.
At risk of getting a valuable employee poached - Epicor should really consider incorporating @hmwillett (and compensating her) as few are in as deep as her.
Taking you with me Kevin.
It’s gotta be what disclosure was thinking about in this song:
That’s not in the style of “Bardcore”, I’m not interested.
My mind was long gone before Kinetic. 
hahahaha been typing for well over an hour
We have been trying to switch from our old ERP to Epicor since the end of 2019. Yes, 4 years ago. As a developer who was hired mostly for that huge project, I had to learn the world of not one, but two different ERPs.
We were first introduced to the Classic version. Soon or later, the Epicor Roadmap scared us.
The more Classic customisations we add, the more we will have to recode in Kinetic.
We will be stuck with a Classic version that will no longer be maintained by Epicor.
Our users will have to adapt to completely new interfaces TWICE (old ERP to Classic, Classic to Kinetic).
So … we are lucky enough to not be in production yet. Why not Go-Live in Kinetic?
Oh god what if I knew.
#noDocumentation
#layersGettingCorrupted
#slowGrids
#fulfillmentWorkbenchUnusable
#contextMenuMaintenanceBrokenAF
#whyEpicorStillUsingRestV1
#causeTheyBrokeRestV2Dates
I love this group though 
I actually had something relevant to say, but y’all got me laughing so hard, I forgot.
So see y’all on the next 
I think we might have to give @utaylor or @Chris_Conn the badge for this one.