Merging custom mods

Hi List

We have just applied an ESU into our DV environment. We knew that 7 of the objects included in the ESU contained custom mods. We set the selection to merge and ran through the update installation. They all finished succesfully however the spec merge seems to have merged some but not all of our custom code. Is this always unreliable or are there certain circumstances where it will not merge custom code? Should I tell it not to merge and retrofit the code manually?
Thanks in advance for any help on this.

I have seen a JDE document, stating that there's no more "merge" and the target specs are now always replaced.

This was published at around XE U7 timeframe.

Whatever it's doing now, it's not likely to be very consistent or reliable and retrofitting seems like the best (only?) remaining option...

The Merge option still exists as late as E811 but as Alex says, unless your customisations are very straight forward retrofitting the objects is really the only sensible approach. Have a look at the Software Updates guide to see what will get merge and what won't.

Thanks, one question though regarding the retrofitting. How do you retrofit form changes? Like when we have hidden, moved or added fields on the form, do we have to go through and re-apply the changes, if so is there a quick way of identifying them or do we have to revert to our change documentation?

Don't take this as gospel, check everything.

Supposedly preserved are:
New hyper items, controls and grid columns
Vocab Overrides
Custom indices (this is unpredictable)

All ER changes need to be reapplied with Event Rule Compare - compare against PY or something. They used to put ER at the bottom commented out which was not useful at all.

If you have renamed any hyper exits or other controls, the merge will corrupt your object.

Basically you have to review, retrofit and retest any time you put an ESU on top of a mod. You should test ESUs thoroughly regardless of mods.

Hope this helps.

Sue Shaw
Xe Coexistent SP23J1 iSeries V5R3
(highly modified)

It doesn't always work but why not use the Form Compare tool in FDA