Menu Maint Read Only

I can’t understand what in the name of sweet Jesus is going on with Menu Maint. When I restore my production to pilot menu maintenance is 100% read only with the exception of anything new I add. It’s a direct copy of our production, no post migration scripts run, same patch level everything is tit for tat with production. Has anyone ever seen this?

Production on the left, restored production on the right

What’s with the extra checkbox in there? You are running base right?

Menu maint doesn’t have any customizations in our system but that’s a great question wtf is that other checkbox about?

Even though they are gray, did you try messing with it to make sure it actually is read only?

That is the “CRM Enabled” checkbox. Not sure where it’s label is but it’s programmatically shown and hidden as you click through the menu so maybe a show hide glitch.

It is truly read only.

Turn it off and turn it back on again?

the it crowd chris odowd GIF

Check your permissions in User Account Maintenance.

Sadly yes. @EarlGrei just did a fresh restore of the DB again.

Looked at them for me, tried as security manager, disabled and enabled global security manager as well.

A restore of the same backup?

Maybe there were some locks on the DB table when the backup was made.
(Not a DB guy so I’m probably talking out my …)

Set tracing on, full dataset, and return data, before opening menu maintenance,
and post it up.

I’d also go try the Kinetic version and see if you have similar problems.

It is also read only in kinetic, and no I’m not posting a trace of my entire menu structure, I’m not even sure notepad could open that without locking up lol.

I take that back in the Kinetic UI it’s a mix of both. Some are read only and some are not. Classic all are read only. Production none are read only.

You could give us a slice you know. Or at least look at it yourself :slight_smile:

Well… I know the solution no idea what the problem is. It’s something with the client install itself. I pointed my shortcut to my production client install folder and moved the config over and it works fine. I have no earthly idea how the client install could impact this or how two client folders that were setup at the same time in Nov with the same patch level are behaving differently.

Eff it i’m going to roll with it, it works.

2 Likes

I had some wild times with menu maintenance this past week copying from test to another environment.

The whole program type and Form to Use thing for a kinetic app is not working as I would expect it and I logged it with support. It got a PRB.

The menu maintenance part of kinetic has obviously been changing and quite rapidly at that.

I have a SaaS customer determined to use Classic screens, so we created a DMT upload to change all the Menu table values. It was originally done on 2021.2, so when we had to redo it for 2022.1 it was quite a painful discovery to find out there were at least three changes in how Epicor used various fields in that table between versions.

I shared some of your wild times. The wildness was not desired.

1 Like

Ernie, you are describing exactly what I was trying to deal with last week…

Has anyone had their kinetic layer references disappear after upgrading? We just upgraded from 2021.2 to 2022.2 and for the kinetic app menu items all the kinetic layers are gone from menu maintenance. I DMTd them back in again, but what the heck?? So far support has asked me if I tried removing personalizations. :man_facepalming: