Last week I updated a client from 10.2.400.34 to 2025.2.10 (yes, big jump!). Overall it went well, still fixing small things here and there, but nothing major — except for one thing.
I have an updatable dashboard that on the old system opens normally, but on the upgraded one it takes up to 2 min to load from the menu, and while it’s open the whole client slows down noticeably.
Memory-wise, I can see the Epicor process eating up to 3GB of ram just for that dashboard (on 10.2.400 the same dashboard was around 500mb).
I noticed that very time I open the dashboard on the upgraded system, I get the popup saying it’s being deployed for the first time, even though I’ve already deployed it several times.
The dashboard is quite complex, but I wasn’t expecting this level of slowness. Has anyone seen something similar after a big version jump? Any idea where to start looking?
It’s a 5 queries dashboard, each with published columns. Then queries 2-5 are filtered by the published columns of the previous one.
It’s not a simple dashboard, but it worked perfectly fine before so I wasn’t expecting this level of degradation.
That said the queries are not the problem because after the dashboard finally loads then the usage is ok.
First thing I would try is to create a new menu item linked to the same dashboard, and see if the new one also opens slowly. I’m assuming it’s a classic dashboard, is it set to Dashboard Assembly or Dashboard Runtime?
Next step I would take would be to disable each of the queries one at a time to see if disabling any particular one allows the dashboard to open in a reasonable time.
Yesterday i copied the dashboard and tried to run it with only 2 boxes (2 baqs). It’s still slow and tries to re-deploy every time.
Will try again tomorrow recreating the dashboard from scratch and adding testing adding baqs one to one.
Upgrading from Epicor 10.2 to Kinetic 2025.2 often results in BAQ performance drops due to changes in how the SQL engine handles older query plans and new security. You can typically resolve this by forcing a query recompile or adjusting new security settings.
Open the BAQ.
Go to Actions > Execution Settings.
Add a new setting: OptionRecompile (or use the provided checkbox in newer versions) and set it to True.
Check the Persist in Query flag and save
You can also reset the Query Timeout setting to zero. Updates can also reset the timeout. So just an additional place to check. (I think the default timeout is 30 seconds)
