This is such a basic function I’m almost embarrassed to ask why I can’t see where this has gone, or how to get it working again. Searching has come up with a few having issues with custom Context menu items, but nothing like what I’m having where I literally have no “Open With” available in the Client version or Browser version of 2024.2.28. This is all I see in any module when I right click… Desktop client or Web Browser.
Shouldn’t have to set anything up, there should be context menus out of the box.
Do you have an environment you can upgrade and see if the issue persists? (also your profile is out of date ) There have been some pretty major updates to kinetic. You could also try running kineticUI conversion process again (not during work hours)
I’m not trying to customize the context menus, I’m trying to see the base ones. Nothing shows when you right click on fields… I can’t “open with” anything.
There is a known bug with panel card grids and context menus sometimes, depending on set up and version. I think your version is probably affected.
Try to “Unexpand”/roll up the panel (so the grid doesnt display, by clicking on the header) - then expand it again. This should make context menus work.
If it does - open a ticket with Epicor about this bug. For a workaround, you can default the panel card grid to expanded = false, then set up a dashboard-timer-set for 50ms, in the timer event, property-set the panel to expanded=true and dashboard-timer-clear.
I think you’ll need to open a bug on this issue, maybe you can get a hotfix.
I remember having this issue around that version (i don’t remember which specifically) - but the workaround to rollup the panel and expand it again worked in my case. Maybe yours is a different problem, but certainly in the out of box job entry/tracker that right click context menu should work on job/part.
I appreciate the help, Ticket opened on EpicCare I’m interested to see where this one goes. This is a database that was upped from 10.2.700 to 11.2.4 and now 11.3.200 so I wonder if something happened along that route to cause this.
Tried getting traction for Kinetic upgrade back in 2023 and didn’t get anywhere. Now everyone wants to upgrade and get current so I just upped that 2023 testing DB to the latest version I can run on our hardware, aka 2024.2
Should have dug just a little deeper… not that this solves the problem… but it shows up for Order Numbers… That Context Maintenance item is listed as “Customize” and not “Base”
Just curious– what version were you on when you modified the ‘expanded’ property on a Panel Card Grid? Currently on 2023.1.21, modifying that property doesn’t do anything (will change in the component model when debugging but nothing updates in the UI).
I’ve only been able to close/open a normal Panel Card (not a ‘Panel Card Grid’ or ‘Grid’, neither have worked for me).
Good question - I wrote that dashboard around January, so it would have been 2024.1 or 2.
You could try dropping in a panel card, then a container, then a grid (i forgot if you need a container to hold a grid or if it can just go straight in a panel)
Try using f12 dev tools, in the browser with your app open and as the active window, ctrl-alt-8 to turn on debug mode, then ctrl-alt-l to load component model, then switch back to dev tools, find your panel card in the list of components, expand it, double click true in expanded: true and try to set it to false - then click back in the browser window, see if it expands on demand when you do it from dev tools - maybe it’s broken in that version.
For the sake of helping users who are unfamiliar or new avoid confusion/to help search results/stay consistent with Epicor terminology, they call this “collapse”. Or if setting properties, then it’s expanded=false.
This is a bug which was introduced in 2024.2. We didn’t have a problem with patch level 17 but when we upgraded to the highest release (34??) we lost context menu items. I raised a ticket with support and they said it has been addressed in release 2026.1 and there’s a hotfix for 2025.2. Unfortunately, it appears they aren’t going to hotfix for 2024.2 so we won’t have the functionality until we upgrade in Q1 to 2025.2.
That is absolutely insane… I have a ticket open with them and if that is their solution, I am unable to move to 2026.1, or 2025 for that matter due to server requirements so I will have to drop down to version 2024.2 at the patch level you described. This is just a Pilot environment to get people onboard with moving to Kinetic, so I can easily move back to .17 and re-upgrade the DB that I started with. I installed the latest patch as all install instructions indicate… I guess they just want you on the worst version possible… ugh…
Wow… I can confirm this is accurate… I don’t know when the problem starts but I brought an existing DB up to 2024.2.17 (same DB used for my previous 2024.2.28 upgrade) and the context menus are 100% there and working as they should.
If upgrading patch levels wasn’t such a pain to go backwards I would do them one at a time and see when they messed it all up. Maybe if I get some spare time I’ll do that but right now I’ll be sitting on .17 for testing purposes.
I can’t believe they won’t patch this version to fix a HUGE problem like this. Context menus are a huge part of the functionality of the software. It’s very useless without them.
Is there a chance you have a Case # or Problem case # that they referenced to you regarding this being an unfixable bug? The tech assigned to my support ticket said he can’t find anything regarding this, and is on 2024.2.26 and they have context menus visible.
Highest Patch level is .28 right now. I may try re-installing my .28 DB tomorrow under a different appserver… just so I can demonstrate this problem to them.
No, I have never customized context menus to my knowledge. If I did it would have been many many versions ago and I have forgotten about that LOL.
The ones that were not working, displayed above, in Context menu maintenance were listed as Base. As noted above too, the only context menu that I was seeing that worked, was on Order related items and that menu was categorized as “Customize” not Base. I’m not sure what was customized about it though.
I’ll check in my current install of 10.2.7 tomorrow to see if any menu’s are customized and see if I can figure out why. That’s where that now 2024 DB came from way back in 2023 when I was testing version 2023. Yes it’s really old data
Thanks for replying Jonathan. I have been following this thread from a distance as I am relying on our users to do the user acceptance testing and I would have expected someone to say something about this since it’s pretty big, but no one has said anything which makes me think it’s working fine, but I haven’t tested it myself.
I ask about the customization because this environment has none, so I was wondering if it’s only people who have a customization on the Kinetic app… not the context menu itself… like anything on the app, a label, a layout, etc.
) There have been some pretty major updates to kinetic. You could also try running kineticUI conversion process again (not during work hours)
