Set Default Customization for Erp.UI.JobAddlInfoView.dll

If its a Sub-Form to the Main Form you will have to name the customization the same. However sometimes it is its own form and in that case you need to use Process Calling Maintenance and redirect it.

Thats where this comes into play:

Process Key: Erp.UI.JobAddlInfoView 
Calling App: Erp.UI.StartProductionActivityEntry 

I have the same info on this post (regards to process calling maint) check it out:

Make sure that your Customizations are both marked as “All Companies” and one isnt set as Company Specific, while the other is All Companies, it doesnt like mixing. Remember sometimes you have to restart the Epicor Client for Securities and Menus to Refresh.

For this guy the Companies didnt match between Parent and Sub-Form.

If you did it, can we just see screenshots of both the Start Activities Customization Selection Form and the Child forms (which you have above of course). Just for sanity :slight_smile: and clarity.

Also when you show up there that the Customization list is Blank. Wasn’t there an Epicor bug in a version where it didnt show Company Specific or maybe All Companies customizations… anyone remember @ckrusen @Banderson it might have been in Version: 10.2.200.xx which you may be using?

I quote @Rich

Menu Maintenance is broken for several DLLs where you cannot apply customization - versions 200.8 - 200.11. The issue has been fixed in 200.12 under ERPS-95829 and there is a HotFix available from support.

Some of the Epicor UI DLLs contain references for multiple different Forms. Some of those Forms are internally addressed (not available for adding to a menu) and some can be externally addressed as the Form to load when a menu option is selected. Since the Customizations are keyed by Form name and not DLL reference, Menu Maintenance needs to know which Forms are “Externally” available in order to show the Customizations in the dropdown Combo. A change made in 200.8 was designed to address a problem with displaying the appropriate customizations and while that update corrected the initial reported problem, it caused a new problem for a handful of other DLLs / Forms.

1 Like