I guess I am in the “lowered expectations” camp by now. Usually it’s
“Why did they take this away?!”
“Oh never mind; I see you can still do that; it just takes eleventeen times more work.”
So you want actual examples of unmitigated “This is better than classic”?
Processing...
I guess buttons (or any controls) and their events are a breeze now IMHO. I know others will probably disagree, but for an anti-coder, they are way better than the old classic customizations. That wild code to create and destroy was just foreign to me.
[Edit below]
Found it! Here is what I mean. This was the code required for one button in classic. (It would be spread out all over the place; I’m just showing the snippets.)
Most importantly, learn the rules of Fizzbin, they will help you to understand Epicor’s thought process with most things Kinetic for the first 6 months while you are still used to Classic.
Once you get used to it, its actually not that bad, but the initial learning curve is pretty harsh.
This is so sad. Landing pages are one of the things my users love the most. I can understand there might be some specific programs where you don’t want them, but to just remove all of them?
Agreed. Landing Pages are great for our actual users.
You know how all of our users think Epicor is like Excel? Then they try to explain to themselves how Epicor works using the mental framework of Excel. They will never get from A to B with that thinking.
Likewise, please stop trying to fit Kinetic into a mindset of Classic.
The goal is not to strip Kinetic of everything new and beneficial.
You need to approach this as if you have not been doing this for 10 or 20 years.
One benefit over classic… Speeeeeeed, shame there are, some circumstances a lot more clicks… but just like you @klincecum been avoiding it poking at the edges, now I have to.
Going to push back a little bit here. Do they love Landing Pages or the new search paradigm? Landing pages that make us wait to pull in the first 100 parts/orders/etc that we’re not interested in are a waste of time and bandwidth.
If we could have the nice filtering we see with Landing pages but not download everything to the client in order to do so, then we have the best of both worlds. This seems to exist with Angular and the Kendo components.
Excellent point, and on the one hand, of course you are right; it’s the searching.
But that initial data splash has to be displayed there for the first several generations of users, so they know What This Thing Is.
iPhones do this. They introduce a new paradigm (that word is so geeky, but it is the right word), then drag everyone along for a version or two, then assume everyone got the hang of it and stop nagging you on how you need to use it. (Say, like swiping from the corner to get to settings.)
So, I’d argue we need to collectively live with the data grid filled in for a year or two (past 2026.1), till people know what it is.
I have no problem with that, but instead of the first alphabetized records, use the last X number of recent records. At least there’s a really good chance that it will be one that I’m interested in. (Starting to see this capability already in a few landing pages.)
I think if you save your layout in that way (if that criterion exists in the data set already), it will do that - it will apply the sort before loading.
Once you do that layout save, you have to do a browser refresh to actually see what I mean.