All my kinetic dashboards are broken after this weekends update. Is there a kinetic dashboard specific regen process I need to run?
Ouch. Makes me want to move to cloud… ![]()
On Cloud: I had to redeploy one of my BAQ dashboards that has parameters. The parameter pop up didn’t show until I redeployed it. I would love to know of a routine we could run that would fix this. Then I would like to know why Epicor wouldn’t just run this routine after messing things up? ![]()
What do you mean by re-deploy? Publish the layer again? I tried that.
Kinetic dashboards aren’t deployed like the classic ones were
Sorry, yeah. Stupid terminology. First I open the Kinetic Application in Application Studio. Then Save, then Commit, then Publish, spin in your chair three times, and scratch the left side of your face… Bite your tongue for the blood sacrifice… ![]()
No go.. ugh
What happens when you try to open one of your dashboards? Anything in the Dev Tools?
Try deleting personalizations perhaps? I’ve seen this with dashboards before but not over an upgrade.
That didn’t help either. I can see in the network tab no calls to the baq are being made..
Nothing on the console tab? Maybe try adding in debug on form load will help too: Kinetic Debug Error Fun - #10 by cory.davis (I haven’t yet needed to do this but I have this kept for such cases)
What do you see in the Console tab?
Hey now, don’t you be stealing my questions!
![]()
No errors.
I think I did find a process that fixes them..
- Delete all personalizations
- Select the dashboard in application studio, and select upgrade selected layers
- Then open the dashboard in application studio, save, commit, deploy
- Hard refresh or have user log out.
This kinda stuff should not happen after updates.
Never make layers on a dashboard. Only ever modify base.
They are all base
Was this a minor upgrade or a major upgrade?
Minor 2025.2.7 to 2025.2.10
![]()
The sad thing is that it keeps happening. Every update is a mess for cloud customers. Such a waste of your time. Glad you figured out a workaround. Others will unfortunately be waiting for support to come up with a fix, again.
Im sure we would face same / similar issue on-prem. That is why @jgiese.wci and I are holding off on Kinetic Customizations and still riding the Classic pony. Because we kept getting burned by the framework changes, I thought by now the Kinetic UI would be mature enough and stable… Maybe 1 or 2 more major releases.