I hear you. Is there a way to simplify the DataView/payload to reduce the parsing logic at the client? 
1 Like
For what it’s worth, we experience almost all of the same.
2024.1 hosted on prem
We migrated to Epicor and went live 2023.2 In January. We drank the Kool-Aid and went all in on browser only full Kinetic.
We’re surviving but there are so many pain points such as what you listed.
Death by a thousand cuts.
It’s rarely a show stopper but definitely impacts productivity and morale.
I frequently feel that I am an outlier. I think the outlier is just that very few are fully browser.
3 Likes
We’ve seen this with Sales Order Entry/Tracker most often…especially if doing an export to Excel (accidentally or on purpose)…user task runs forever and ever and ever…usually need to kill the task and/or recycle the app pool if it’s really eating up resources.
I guess we’d be 99% browser…only a couple of people using Citrix and that’s for stuff like DMT and BAQ design (cuz I prefer the client LOL).
It took us a while to get over the hump but we’re pretty stable now (~18 months live)…less app server/pool problems (reboot scheduled on the weekend), less phantom errors where we need to reload the base screen in App Studio (only once in the last 2-3 months)…fewer datafixes…etc etc etc.
That being said, I can’t say it’s all been 
and 
by any means.
3 Likes
Thanks for the update John, hoping to pop up to 2024.2 when it comes out.
Chilling on 2023.1 right now.
1 Like
2023.2.11 here…I think we’ll remain on it for a little while…
2024.1.10, we went Live in May, SaaS Kinetic Browser only. We’ve had to use classic as a workaround here or there, but it has been a steady improvement over time. Our consultants pushed us to Kinetic only, it was not prime time ready when we started our implementation, but at this point all the functionality we need is present in Kinetic, so no ragrets! Even forced myself to BAQ and BPM in Kinetic, how fun! 
5 Likes
Thanks for sharing! Glad that it’s working out well for your company!
8 Likes
Yeah that is the one thing I couldn’t do. The BAQ thing was glitchy in Kinetic on our version so I couldn’t trust it.
2 Likes
2023.2.x Kinetic BAQ designer is buggy and doesn’t support uBAQs. I’m hoping 2024.2’s version will be stable and I already know it support uBAQs.
I’m scared of the Kinetic BPM designer. I haven’t even looked at it yet
2 Likes
Yeah, for the average “user” Kinetic is good and we use it 100% for daily activities. But admin and data manipulation stuff, I still use Classic for almost all that stuff.
6 Likes
We’ll hold onto Classic admin tools for for as long as we can.
3 Likes
We’re not yet live on Kinetic - but we’re going browser-only (maybe next spring on 2024.2)…
I only use Classic for Functions and for getting Dashboards started.
Regarding BPMs and BAQs in Kinetic browser … on 2023.2, they are maybe a little less responsive (pause between clicks), click-to-drag widgets is a bit funky (sometimes have to click again to set the new location), and sometimes the right-click menus don’t come up (for deleting and copying directives/subqueries)… but it’s not enough for me to load up the slow client app
…and I dread having to load up E10 to support users on our current production system - the trace does not compare to what is available on Kinetic in the browser, and I get a bit lost trying to find data sources 
.
5 Likes
That’s our plan too.
I feel the opposite. I know Classic trace so well but doing a trace in browser makes me feel lost/overwhelmed by the Dev Console.
3 Likes
In 2024.1 if you move your widgets too far up,down,left,right whatever around the design editor, you wont be able to open the workflow up in classic! Neat feature!
10 Likes
I’m just saying, 4 spikes on the widgets is not enough. I need 12 like classic.
Also yes, very buggy.
4 Likes
2 Likes
We can not use BAQ design in the browser as it produces the dates in the incorrect CSF so we have to revert to classic for all date-based BAQs. Pity as I liked the browser it was a little buggy but that’s outweighed by its new features.
5 Likes
You can do the external queries on the browser, classic can open the BAQ
You can’t do updatable queries in the browser, classic is the only way to do an updatable BAQ.
I have been logged off many times while working on a BAQ
Save often
To many times that I have had to refresh the browser not just the Epicor process screen.
Kinda working really demonstrates that this is a BETA program not a real GA program.
1 Like