It was moved to the related pages “On Hand”. Took me a little bit to find it too.
3 Likes
Wow , thank you! One issue down and 4 more to go
4 Likes
Now we are experiencing a handful of users ( someone regular users and security managers) they go to Part Transaction History Tracker , type in a part number once they hit enter, they are hit with this error:
( Troubleshooting I have tried so far and still no luck , awaiting Epic care to get back to me ) :
Tried logging with the affected users Epicor credentials on different computer same issue
restarted their computer
cleared cache
verified menu maintenance and menu security maintenance access
In 2025.1 (just released), there are several enhancements to the Edge Agent functionality. I haven’t tested them yet, but the Release Guide (requires EpicWeb login) has a section to peruse.
Specifically, you will need an Admin login to FIRST install the Edge Agent. After that, updates do not requrie an Admin login.
2 Likes
I see this PRB created yesterday:
PRB0300557
Created: 2025-06-23
Updated: 2025-06-24
State: Submitted to Development
Part Transaction History Tracker - Error message when sort Warehouse and selected another part
2 Likes
We had to run the FX_Del_XXXDef_KineticPersonalization data fix and wipe the personalization for affected users on PTHT.
2 Likes
We ran into the same thing yesterday and this worked for us!
2 Likes
I don’t know if this is unique to 2025.1.5, but most of our Classic dashboards would not load. While a few would recompile on-the-fly, with a brief “Please be patient..” popup the first item they were loaded, most would not load and would either hang for the user or display the error:
Resolved in all cases by opening the dashboard in Dashboard Entry, and re-deploying to Classic.
1 Like
This isn’t specific to this version I don’t think, its just if they do a crappy job upgrading you or the script fails as far as I can tell. Doesn’t happen every update, but happens more often than it used to
3 Likes
I know in the on-prem Upgrade Guide, redeploying directives and dashboards is definitely a step.
2 Likes
I should mention, this happened to us
1 Like
Part of the post-upgrade tasks us admins should do it redeploy all classic dashboards in Dashboard Maintenance. Also purge classic personalizations (optional) and directive recompile all BPMs in Directive Update.
3 Likes
We’ve only ever had to do this after we switched to public cloud. I wonder if we inherited additional responsibility without being told.
1 Like
I’ve had to do the three tasks I mentioned even when I was on-prem.
Well, that would make perfect sense, you are the one doing the upgrade in that case. If Epicor is upgrading us, I would think they would do all steps of the upgrade that doesn’t take customer input. So not testing, but running all upgrade processes.
4 Likes
You’d think but it’s probably in the fine print somewhere that they don’t do all the upgrade steps at least for classic UI stuff. 
Ugh, was not aware of this! Adding to my docs…
1 Like
We managed to get it installed, but now it’s giving us a security certificate missing error. Says to contact Microsoft and won’t load.
1 Like
We can’t find anything in these new menus. I’ve resorted to just using the search box to find what I was looking for.
Yes, Install an older version fixed it for me. Version=1.2.603.0