I have a dashboard that I converted to Kinetic, it is pretty simple.
I want to group by Job, but as soon as I drag the column up to the group by box, the dashboard seems to hang and take forever to refresh itself.
Is there something that I am missing or is this another bug that has not been fixed?
I also noticed performance issues when testing/reporting a bug for group-by on dashboards. So it might be the functionality as a whole.
In 2024.1 the ‘X’ is gone to remove a group-by. It still works if you click where it should be.
Thes seems to happen with large data sets. For example, data sets that involve labor transactions.
It seems like it tries to grab all the records in the dataset before it groups them.
Has anyone found a solution for this? I’m also running into issues when I attempt to group or un-group. Its getting hung up.
@Fernando this is something that we are also experiencing. We are trying to roll out Kinetic screens and run into this on a few of our dashboards. I have a few EpicCare tickets open, one has had a response recently stating there is a Problem in their repository since 2023 with no planned resolution date
EpicCare Record - EpicCare
Our current thought process is to workaround the grouping somehow, but it’s not going to be pretty for some people.
Something I’ve found and I am trying to scream it from the hilltops, IT WORKS IN MOBILE??
Get an iPad, browse to your Kinetic DB (make sure you turn on Mobile View) then try and expand the grouped columns that normally have issues. There is NO delay on the iPad, and I’m hoping I can get this info to someone in EpicCare to figure out what’s going on and get it fixed faster. They do something different with the data delivery in Mobile View and it is so much faster for us.
Example we are able to recreate: DB that has physical inventory, grouped by Warehouse, then Bin. Our largest Bin takes 13 seconds to expand in the best circumstances, up to 60 seconds on a terminal server that has shared resources and lower internet speeds. For those on the terminal server it will timeout and kill their entire Edge session until it catches up. Same DB on an iPad? Everything loads. Not like that tells us much, but there may be certain users that can use that until the actual issue gets resolved.
Thanks for the tip, we’re not currently using any mobile screens but I’ll test on my end and see if its something we use can use in the future. We’re also in the process of converting to kinetic and have a few more complex queries that are fine in Classic, but noticeably slower in Kinetic. And trying to group or ungroup causes the browser to crash. Same results in Chrome and Edge. Thanks again for the insight, much appreciated.
