We did a big test today in our new environment. The biggest issue we saw was people not being able to load dashboards. If I run the dashboard I get the following:
I did the Deploy All UI Applications task in dashboard maintenance, but that’s all I’m used to doing. Is there something else in an upgrade that I’m supposed to do? I see a conversion task 196 and 197 for users to run, but I’m not sure what those do.
Are these Classic or Kinetic UI dashboards?
We just got 2025.1 on our Pilot over the weekend and we’ve not ran into this dashboard issue yet.
Classic.
We’re on prem, but the only way to get them to load them themselves is to make them dashboard developers in the user options. After I load it the first time, it works for everyone.
I know you said you have, but perhaps deploy them all again in Dashboard Maintenance. Seems like it didn’t properly deploy them. One-at-a-time is a PITA.
Going from 2023.2 to 2024.2, I had to go into each Dashboard and hit Modify Dashboard, then Generate Application for each one.
We did not get the same message about generating dashboard - just a MetaUI GetApp error after a couple of minutes of waiting.
Try it with one to see if it makes a difference 
Using the Deploy UI Application tool didn’t appear to make any difference in our case.
@Randy - I did. Just to make sure I didn’t make up the time it took on my cutover checklist.
@jwphillips - <sarcasm>sounds great</sarcasm>. So my only choice is to deny access to the dashboard designer and then make everybody have the ability to be a designer … or I have to manually do it all.
Look on the bright side, it’s at least one way to know what dashboards users actually use… 
So you opened Dashboard maintenance, and searched and selected all deployed?
Then ran Actions → Deploy All UI Applications ?
Twice!
I think @jwphillips was correct, I seem to recall we had to do each dashboard when we upgraded a few years ago. I thought it was e10 to Kinetic but maybe it wasn’t. 
Ok just making sure you did it right.
I had this happen with a few dashboards. Not sure how I fixed it. I don’t think I did each manually.
I am having the same issue except mine are for Kinetic Dashboards. If i redeploy then it overwrites the layer that i have and pretty much have to rebuild the dashbaord. I have tried bringing it over as export/import and had very little success also as a solution didnt work either. I noticed that conversion number 202 when upgrading the database completes with errors and says something about the MetaUIMigration conversion so i looked there and it said something about the KineticUseFileSystemNotDB flag needs to be set to ‘false’. Tried re-upgrading and setting the flag to false prior to running the conversion but that didnt help. I noticed in the MetaUI folder on the app server there is a folder for each dashboard, report and so on but in 2024.2 i dont see any of my custom stuff in there. I tried copying over from 2023 and that didnt seem to solve it. So i am stuck and my dashboards just sit greyed out.
I’m curious, as this could be more of an issue with Cache. Especially if you’re still using Smart Clients. When people launch applications, and especially if they created any personalizations, Epicor throws them into a cache folder so that they launch quicker. Thus, following an upgrade, the system may be trying to launch an outdated application, and thus needs to update it.
Try deleting the cache folder for users encountering the issue.
I also discovered (since we are using the browser UX) that it also creates cach files. Delete “Cookies and other site data” and “Cached images and files”) from the browser history.
Sometimes saving things to their favorites or home page can cause issues, as well. If they are launching an application that way, try having them launch from the menu location, and if that launches without issue, have them remove their shortcut and readd it.
Those are the only other possible root cause of that I can think of, off hand.
We’re in the middle of an acquisition/network turn over. We were running load tests on the new servers and had everybody in the test rooms using their new computers. There was no cache to clear.
I’m sure it’s an unintended feature.
Ok, so more data below. The first record is after re-deploying all dashboards, the second record is after running the dashboard for the first time:
| DefinitionID | DashBdVersion | DataBaseVersion | LastDeployedDate |
|---|---|---|---|
| dshBinTracker | 4.1.8810.659 | 40200 | 6/3/2025 7:55:55 AM |
| dshBinTracker | 4.3.9285.494 | 40500 | 6/3/2025 8:14:36 AM |
Doing another dashboard, I tried Deploying just a single dashboard. Nothing changed with the DB Version #. I also tried running it from the Dashboard Maintenance, it didn’t update. Only when I run it from the main menu does it put up the image:
and actually change the versioning information in the system
I finally got mine to work! I had to copy over the MetaUI folder from our current version app server to the test environment server. I believe it is due to a system flag that is checked true called KineticUseFileSystemNotDB. Maybe not. But after i copied this folder that contains all the custom reports and dashboards, everything started working again.
