Testing Kinetic 2025.1.. this thing is killing me. OK, so ‘open with’ off a part number field, I would expect to see ability to open part programs like before in classic and like in some programs. OK, so maybe no, IDK why, but if you have suggestion please share.
Here on part tracker open with AT LEAST allows Where used? (where are the rest thought). Now on method tracker, no “where used”. Engineering will not be keen on this at all 
Thanks
Nancy
Method tracker has never been available in a right click from part num, its always been on revision. Not sure I understand your first screenshot. It might help if you show the whole screen for context.
Where Used is not a normal Context Menu option - it’s not available everywhere. If you want to add it, you have to add it to the PartNum field of the dataview as a custom context menu item. Emulate the existing values and event in the Part Tracker.
Thanks for reading and thinking about this too, I appreciate it!
My question is more about what “open withs” are showing or not showing on the part field throughout Kinetic 2025. I do have some custom layers that were developed for us and I want to ensure that what I am seeing is what others are seeing too…
Here is more pointed comparison of our current classic functionality and our new version. Is the list of programs you have to “Open With” in part tracker part field and method tracker bom part field the same as what you are seeing? Do we actually need to design all of the Part fields special in order to get back to the functionality we already have in classic?!
TY! Nancy
Hey Nancy,
More out of curiosity, are the Part Number components Text boxes or Part Rev Descriptions? Maybe the context menus are set properly on one but not the other? Just a shot in the dark.
Having said that, Part Tracker IN THE BROWSER for 2025.1 shows this:
And double-checking, Kinetic Part Tracker in the Client shows the same. 
2025.1.5
Oh boy, I am SOOO glad you guys are seeing them in your version. Thank you for looking! It’s much better to try and get them back to standard than to think that Epicor has designed 2025.1 without consideration for all of these. The Open With is such key functionality, literally and figuratively 
for our users in Epicor. I was having nightmares of getting tarred and feathered. 
(I still have them some, but not as much now 
)
I am using the part number field in Part Tracker. In application studio, the properties look like this below. I wonder if Key field should be checked. This was a layer done by a developer for us to get some ud fields in there and a tab for comments that get copied over to a PO for a part. It seems like the custom layer must have broken the normal behavior of the field or the developer added it without providing needed functionality. The field does look like it is called erp part rev desc.. I guess this is how it shows both in the one field area? I wonder what that symbol is in description too.. Boy change is hard!
Thanks so much,
Nancy
That all looks right
The majority of the Open With options (all the ones that you are missing) are handled in Context Menu Maintenance and key off of the Like property of the fields. In this case, Part.PartNum.
Looks like this:
That’s the translation lookup button
The plot thickens - So I went back and checked our test database, where development is getting done and solutions made and shipped out. I compared the behavior there and the Part open with context IS working in test. The version of test is the same as our other db with the error, EXCEPT Enterprise Search was turned on in our “simulated” prod database vs our test / dev database. Could the setup of the Enterprise search that was done (by another consultant / our IT) have bashed the Context menu for part in the sim prod database? Is it possible to have the enterprise search working and still have our nifty standard open with context menus?
Here’s the compare of the Part num menu items in test vs sim prod.
Thanks so much for your help Jonathan and Mark and Alisa too 
Nancy
Alrighty - I am going to leave it as IDK how or why the context menu went away for parts. Fortunately I haven’t seen it gone for other IDs so far, but I WAS able to take the context menu items from that Test db and paste into our sim Prod db, so hooray! Thanks again everyone! Nancy
