After importing both of our solutions as Managed solutions, we observe that the solution import process removes the <clientincludes> section from both the Account and Contact forms. For reference, these sections of the customization are
under Microsoft control to load scripts it requires.
Specifically, we receive a dialog on lookups alerting us to a field's customized event related to the "parentcustomerid" field and the "setadditionalparams" event with an error "Object doesn't support property or method 'parentcustomerid_setadditionalparams'".
Naturally, this error would occur if the scripts are not present.
So, does anyone know why import removes this section when both solutions are Managed (ie no error when one is Unmanaged)? And is there a good way to either prevent the removal or hand hold the importer to keep this section?
(As a crude workaround, I've written 3 line script to add these fields back into the form during the onload event.)