A Cust-layer Overtake procedure combining several $SEARCH/$REPLACE blocks together with a $SEARCH/$APPEND block in the same method fails during code generation with 'Could not replace text ...' for one specific $SEARCH block, even though the referenced source text visibly exists in the Ext-layer method being overtaken. What's commonly wrong?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This is very often a whitespace mismatch between the $SEARCH block's text and the actual original source — extra or missing spaces/indentation that aren't visually obvious can still cause an exact-text-match $SEARCH to fail to locate its target. Copy the original code block verbatim (including its exact whitespace/indentation) directly from the Ext-layer source into the $SEARCH section, rather than retyping or reformatting it, when combining multiple $SEARCH/$REPLACE/$APPEND blocks within the same overtaken method.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions