So I am working on an next version of our MES customization, so I saved a copy and now am trying to deploy in in pilot, but only the original customization that we had will show up. I tried our company since that’s what the current menu item is, and all companies. Neither of them will show up. Has anyone else had problems with this?
Are you working with a different version of Epicor in Pilot than you are when you created the first MESv1 Customization? Does it have something to do with the Program selected in Menu Maintenance? The “Erp.Menu.Mes.dll” ?
The first version of the customization was created in 10.0, we are now in 10.2. It’s come through on the upgrade. That’s interesting on the program selection. I see that when I search MES, that one doesn’t show.
So if I change that, they still don’t come in… and now MES goes back to default. How do I get that fixed?
Oh no. I’m not sure. I just noticed that we had some MES Customizations (possibly obsolete - I need to investigate) that came over from E9 after our upgrade and they still show as Epicor.Mfg.Menu.Mes.dll. Can you just manually type in Erp.Menu.Mes.dll into the Program field and look to see if at least the MESv1_Customizaton is back? It sounds like this might need a call to Epicor…
Can you export the MES customization from your Live environment and Import it into your Pilot?
I can open them in developer mode (they are still there), so I can still get to them. But none of them show up in the menu maintenance to actually deploy them. Not a big deal in Pilot (that’s why I mess around in Pilot right?) but I imagine I will have the same problem when I try to do the same thing when I need to import the new customization into production. Worst case I just have to work under the same customization instead of making a new version. (I know, bad practice…)
I tried that, but no joy…
I’m wondering if I can change something in the XML to get it to recognize it.
Did you set the MES custom to your custom name in sysconfig?
I did Chris. It was like that before. I didn’t change the Menu ID, I just want to change the customization applied to that MenuID.
Forgive me that I didnt read all of the thread, but did you clear cache?
no, I’ll give that a shot. (… grumbling about losing my hot keys…)
No help on the clear cache.
Can anyone tell my which program I am supposed to pick for this? Erp.UI.MESMenuMaintEntry.dll or Erp.UI.MESActivityEntry.dll ?? It seems like both are working (for the base form anyways)
I figured you would have tried that already. 
Yes, thank goodness for test environments. That is just very strange that the upgrade wouldn’t apply your original MES customization to the new .dll Program and it would keep the older Program name. It’s just interesting that you had that old Program name in there from 10.0 but you could still see the original Customization when you opened MES in 10.2? You can’t run those things through the Customization Verification process can you? 
This is for the base MES screen right, if so, neither of those DLLs are what you need. You need the Menu.MES as it shows in the calling msg box. I dont know if its related, but I have seen similar issues where from certain versions the base form name has changed. This means your original custom will have to have this name changed in the XML probably.
Alright, I found it again, I have to select “all files” to get to it. (annoying) but ok.
None of the customizations show up though. Not the original, not the copies, nothing.
I seem to remember engineering workbench having the same problem. 
I had to write a UBAQ to set the arguments for the menu item in a case like this. Because the form name changed, and they didnt update the filter, customs for it wont show. You can look at the format for setting a custom on a menu item, i am pretty sure its just -c custom name
1 Like
Brandon - Interesting… I may be late to the party, but did Epicor change something behind the scenes during the 10.0 > 10.2 upgrade, where it’s using a different form name (i.e. going from blahEntryForm to blahTrackerForm…), so there isn’t a 1:1 match? I’d suggest popping in an EpicCare ticket - We’ll all probably stumble on this one eventually, and the upgrade process should have caught and fixed it (or at least flagged it with a warning).
I’m in the process of making a ticket now.
@Chris_Conn do you have any more details about what you did? I’m not quite understanding what you needed to to with the Ubaq.
Here?
Because the menu maint screen isnt listing your customizations, you can force the menu arguments.
When you set a custom on a menu item, it sets arguments = -c CustomName
1 Like
So you set that in the UBAQ, there’s nothing that you can do to make it allow you to choose what’s actually there. Gotcha. Let’s see if I can make this work.
That was the ticket.
For those of you that are interested, you make a UBAQ on the the table Ice.Menu. Make Arguments updateable. Then you can type in -c YourCustomizationNameHere . This will force set the customization instead of using the drop down.
Here’s the Ubaq if you are on 10.2.200 or later.
MenuCustomizationSet.baq (23.0 KB)
4 Likes