A custom Object Connection Transformation rule, with its own custom transformation method, tests successfully via the 'Test transformation' option, but doesn't actually take effect on the real target Logical Unit, and the Debug Console shows nothing useful to explain why. What's a good way to debug this?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Directly query what the Object Connection Transformation framework itself currently resolves for your specific objects: SELECT * FROM TABLE(Doc_Reference_Object_API.Get_Key_Refs('<TargetLuName>', '<KeyRefString>')), substituting your actual target LU name and key-reference string. This reveals exactly which source LUs and key references the framework currently associates with that target object, telling you whether your custom transformation rule is genuinely being recognized at all. If the query does return data confirming the rule is recognized, add debug/trace output statements directly inside your transformation method itself, with server output enabled, to confirm whether your custom code is actually executing when expected — this narrows down whether the problem is in rule recognition or in the transformation method's own logic.

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