IBM Support

Automapper will only map parent elements, if input and output cards use the same type tree resource

Troubleshooting


Problem

The IBM WebSphere Transformation Extender (WTX) Design Studio Automapper feature will appear to fail to create the child elements if the type tree resource for the input and output cards are the same.

Symptom

A single Automapper rule at the parent or group level is created instead of the expected multiple rules at the child level.

Cause

The product is working as designed. If the automap tools finds the input and output objects are the same type (defined as types coming from the same type tree and having the same type path) then it will map them directly and it will not try to automap their child components.

Environment

WTX Eclipse based Design Studio on Windows

Resolving The Problem

If both input and output cards need the same type tree resource, then a copy of the type tree resource should be used with the Automapper. After the Automapper has completed the automapping, the input and output cards can be changed to use the same type tree before saving and compiling the map.

[{"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Design Studio","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.4.1;9.0","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

More support for:
IBM Transformation Extender

Software version:
8.4.1, 9.0

Operating system(s):
Windows

Document number:
545931

Modified date:
29 September 2018

UID

swg21979687