After you update the message map, you should review and amend the transforms in the graphical data map so that it behaves in the same way as the original message map.
The following image shows the converted graphical data map configuration for the map named MembersMFPFlow_Mapping.map:
The transforms are updated as part of the solution, so that even though the transforms are now of a different type, they behave in the same way as in the message map. You can test this by following the steps in Verifying the solution after you follow the steps for Implementing the solution.
Graphical data maps use all standard XPath 2.0 functions and allow user-written functions in Java™ and ESQL. Message maps used basic XPath 1.0, some proprietary built-in ESQL mapping functions, and user-written Java and ESQL functions.
Not all ESQL functions can be directly translated to XPath equivalents, but these functions are resolved in the scenario solution. In the screen capture, you can observe these changes to the following elements:
To avoid this warning, and the one on the PERSON_SURNAME mapping, you can add an If / Else check for MEMBER_NAME_PARTS or MEMBER_NAME_WHOLE.
You can now re-create these changes by using either your own files or the scenario files that are provided by following the steps as part of Implementing the solution.