MenuID field character limit needs to be expanded

https://epicor-manufacturing.ideas.aha.io/ideas/KIN-I-5226

The current MenuID field is 8 characters and if you have to add a menu item you have to prefix it with UD leaving 6 characters for your menu id name. It would be nice to expand this field to 12 or 15 characters so you can add a more elegant MenuID perhaps matching the Dashboard name or BAQ Report ID which can be larger than 6 characters.
Otherwise you need to use the lowest common denominator of 6 if you want them to match.

3 Likes

Not that I don’t agree it would be nice to have more than 8-characters… but you don’t HAVE to preface it with “UD”.

You just have to make sure it is in the “UD” module.

image

Again, that only gets you back to (8) but… its better than (6)!

4 Likes

I hate the menu ID thing! When I name my menu ID, I type UD, then I just mash a bunch of number keys and hope it is unique. If not, I try again. I wouldn’t mind if Epicor automatically just named the menu ID something unique and then told me what it was.

3 Likes

What I’m seeing in 2024.1.5 is now the UD prefix is being enforced.
I never prefixed any of my menu additions with UD and never saw an issue.
Now testing in my PILOT on 2024.1.5 I switch menu items such as Classic BAQ Report to a Kinetic BAQ report I get an error message "Program can only be updated on user-defined menu items. "
Yes I have the module set to UD but only items with the MenuID prefix of UD would switch. So test and confirm my findings, I would appreciate it.

3 Likes

1 Like

Sounds like a bug you should report.

@olga ?

2 Likes

I assume this is not a system menu item that needs to be copied to the current company?

You bring up a good point now when I copy a menu item to the current company it switches it to the UD module, I’m not sure if it did this in the past. Epicor keeps changing little things and it’s getting hard to track.

1 Like

No idea, better ask @pferrington

2 Likes

I have a similar but more disconcerting issue: A new menu item that was added in PROD shortly before we took a copy into TEST and upgraded TEST to 2024.1.5 is completely missing from the database. I have a ticket open, but I was wondering if anyone else has seen this?

2 Likes

Yes, I have had similar issues. I had a menu item get switch to a different parent.
Try a BAQ listing all menu items and see if QAGO0045 is listed somewhere else.

or Just try a menu search that may be the easy way.

For dashboards I have been using D240710A which is unique.
I’ll take the short field
Just get Security maintenance back into the same screen as it has been since Vantage

2 Likes

It is completely missing from the database. I ran a data compare on ice.Menu between TEST and PROD.

I thought I had a good fix, in Kinetic Menu Maintenance personalize the “Menu Items” browse by adding the “Security ID” field. Then create a context menu customization adding Menu.SecCode to open with SUUT7002 the Menu Security Maintenance program. Then you could right click open with and let publish and subscribe work just like the Classic Version. Of course it didn’t work, not sure why. I will turn it in as a bug or suggestion when I have time.

I just came across this same error message so I opened a ticket to see if it was something on my end. Looks like its a known issue on:

PRB0284041 - Menu Maintenance error when making a change on existing UD menu and saving – Error: Program can only be updated on user-defined menu items.

Epicor supports response was to take note of menu settings, delete menu and recreate from scratch.

Anyone have an update on this issue? Hoping to edit the existing menus and point to Kinetic app as we move along.

I really hope this is merely a bug @pferrington the last thing we need is for users to double(recreate) 50-100 menus just so they can change an Icon or Description which we do sometimes post-upgrades.

I only create new Menu’s for New Dashboards or Reports. Everything else I modify existing.

EDIT:

I do see Epicor marked the PRB as resolved and stated its a defect, but they didnt specify which version its fixed in.

4 Likes

Good old menus… I’ve always just prefixed them a standard unique value and used a numbering system. Not ideal, but at least you can just have a BAQ or a SQL script to filter on all of those menu items “LIKE”

I also like to denote menu items with a customization attached by putting an * at the end of the description (I know potential reserved character yada yada). I go through and update all the system menus as well where we have applied the custom also.

The one big thing I really dislike and I have not tested in 2024 yet is if you copy those menu items with a solution the * gets dropped or just doesn’t update. This used to work in 9 and I am pretty sure 10.2 also.

Looks like it is still an issue in 2024.1.16.

image

1 Like