Mass Customization Deployment Using DMT - Help Needed

@hkeric.wci @josecgomez,

I’m in the process of rolling out a customization on the Part Entry module. There are several menu entries for the Part module listed. I would like a way of quickly setting the same customization to all menu items for the Part module.

Does anyone know how to do this through DMT, or some other similar way?

Process calling maintenance lets you do that, you can also just use a BAQ to find all the Menu’s and Update them.

2 Likes

@dgreenEA Here are the fields I use for menu DMT. I usually will set the customization on one menu and then query for that to be sure I use the Arguments that Epicor set.

MenuID MenuDesc ParentMenuID Sequence OptionType OptionSubType Program SecCode Arguments
IMMT1102 Part IMMN1000 20 I M Epicor.Mfg.UI.PartEntry.dll SEC159 -c Compulink_Info
3 Likes

Usually you can just include the Menu in a Solution and it will make a .cab and then update your PRD Environment.

The way we do it is via direct-sql only for Arguments and Personalizations those are our only SQL Exceptions (on-prem) because Solution Workbench has errored out before when the Menu Existed, instead of an Update it tried an Add and im not sure if Epicor fixed the bug in 10.2.700.

What we do currently on-prem:
image


You can also include the SQL in your .cab and then it will be available via Admin Console to be executed.

But for non-system Menu’s we for sure use Solution Workbench, it works fine for those.

1 Like

If DMT works, perhaps even better :slight_smile: If I had to pick SQL vs DMT id go with DMT… If I had to pick DMT vs Solution Workbench I would use Solution Workbench (but be warry of errors, due to some bug unsure if fixed in 10.2.700+)