What can I do to speed up the Kinetic dashboard groupby filter expansion?
I’ve got an Open PO Dashboard for our buyers, which shows Open PO’s, with info from lines, releases, and the supplier and parts tables.
In classic, it loads ~900 rows nearly instantly. If I want to groupby the buyer field, I can right click, turn on groupby, drag the buyer field to the top of the grid, and it instantly groups all the data. I can click the + to expand the group, and nearly instantly, it shows that buyer’s PO’s.
In Kinetic, it’s a dog! If I don’t set pagesize on the gridmodel, it takes a second to load (good enough). If I click the filter icon, and drag the buyer field up to groupby, that’s instant. Then when I click the triangle to expand that buyer’s PO’s, it takes 12 seconds.
Our buyers will not like that at all…
If I set pagesize to 2000, it takes 12 seconds to load initially, then another 12 when I expand the groupby (so nothing gained there…). We’re on-prem, if that matters.
What can I do to speed it back up to what we’re seeing in classic?
Just to be sure you are using Kinetic in the browser, not in the desktop client, right? I heard somewhere that the desktop client is slow, because it is designed for the browser.
We are seeing the same issue. It got really bad on the 2024.2 release. We pretty much rebuilt all our classics in app studio from scratch so not a conversion issue. A grouping of any size is painfully slow. Browser will even do the “Wait or Cancel” dialog at times. We reported it and got added to PRB0268342.
Grid model > Provider Model, link existing BAQ from classic dashboard, auto load, auto fill, resizable, sortable, filterable, advanced filter.
Forced column order by going to metafx-panel-card-grid > Data > Grid Model > Columns, and clicking + to add each BAQ column I needed.
I did not add columns (like Supplier Number from the BAQ) that the users didn’t need to see. Would it be better to add them, and then hide?
@NateS - This is using the browser. Client behaves the same way. Separate issue is export to excel doesn’t work either (although export selected to excel does work). I have an EpiCare case for that.
@cmulford Thanks for sharing. I just created an EpiCare case, and mentioned your PRB. We’ve gotten the Wait or Cancel message in the browser as well. Seems to happen after 10 seconds.
@askulte We also experience this. Large DBs like our Physical Inventory DB in the best circumstances take 13 seconds to expand one row. Put a ticket in, also tagged to the PRB0268342 problem. Entered in 2023 with no resolution date. We’re currently in talks about how to handle a workaround. Not that it will help, but have you tried to load your grouped dashboards on an iPad in Mobile View? (Microsoft Edge from the App Store is set this way by default). For some reason they work flawlessly on Mobile. Added that to my tickets in hope that EpicCare support can compare the data delivery to hopefully get it resolved.
Billy - Interesting. We don’t run tablets - this dashboard was to migrate the purchasing department of the classic client to the browser. We’ve been on Epicor since 2015, and our db is nearly 300GB…
Why does it feel like Kinetic is two steps forward and two steps back. It’s like I’m trying to run in quicksand, lol!
Our DB was around 80gb, we did a re-implementation in 2018 or I bet ours would be just like yours! The company has been on it since 6.10. I agree though, we are constantly moving goal posts with Kinetic. We just put a pause on rolling out our Kinetic screens until we can figure out answers to a few problems:
Grouping Issue is a major one
Unable to pass values to Data Discovery widgets stops us from converting our DBs with Crystal graphs to Kinetic (which we currently use for Scheduling, here’s to hoping our users accept Advanced Planning and Scheduling to get away from all of these Custom DBs)
Users in our Kinetic Beta receive Lifetime Validation Errors kicking them out of their session, requiring them to close all browser windows and reopen. Happens multiple times throughout the day.
Users who utilize the Edge Agent for printing are having an issue where the reports won’t print and will print preview as a fail-safe
With all of these issues combined (and a few more little ones), we’re pausing the roll out and continuing in classic until we can talk with EpicCare (and hopefully someone at Insights) to figure out when we can use Kinetic a little more efficiently. I got phone calls from a few of our beta users who straight up told me they are going back to Classic until Epicor fixes some of these issues because it takes longer to do their job. It can be a little demoralizing.
