An unsupported mapping
transform {0} was found in mapping routine
{1} during flow playback or HATS macro generation.
The transform was changed to a simple Move.
Explanation
User response
To resolve this problem:
- If you plan to generate runtime code for the Service Flow Runtime
environment, you might not need to make any changes in the mapping
routine at all, because all mapping transforms are supported in the
Service Flow Runtime context (see ESQL reference).
- However, if you are required to use flow playback or HATS macro
generation, and the macro routine is an essential component, then
modify the mapping routine to fix the problem:
- Remove the unsupported mapping transform.
- Modify the mapping routine or the flow so that the unsupported
mapping transform is not required.