Wow, the same guy as my previous support call looked into this issue… which of course, because he connected to my computer … all was working as expected…
Yes Simon… When checkbox is set, the context menu is available to all users. And it is how I set it up.
We do not give such access to our users (modify themselves the menu context… ) … not sure how efficient the checkbox is then. I would have liked maybe a selection box of users where we could set a sublist of users that would allow access, (like the menu access) that would, in my opinion, have been a better implementation…
New development !
I did not close and open Epicor when support left me yesterday. As soon as I did , it was not working again.
Another Epicor case neede to be created…
Support calling back and here is the source of the issue: A personalization of the list.
When you create a new context item, without the Customization Mode checkbox set, it is an item only available to you. Doing so creates a personalisation. (Unfortunatly, it does not show it as for Forms, where you can see the user id.)
So when a perso exists, it has precedence over the other list (where the Customization Mode checkbox is checked).
So in order to make it all work again, You have to show the list with Customization Mode unchecked, select the menuID (in my case OrderHead.OrderNum) and select delete.
What will now show is the same list as the one with the Customization Mode checked.
Close and open Epicor and all is now working as expected!
Now a happy camper!
Pierre
NOTE: I wander why this checkbox exists then, as soon as a perso menu item is added, any subsequent general menu item will not be available to that user! because of the perso…
Maybe be a bug?