The objective is to convert 2 different recordsets(SINGER and SONG) under same message, to single nested recordset (SONG nested under SINGER). The message type: The mapping: For node SINGER, SINGERID and FULLNAME, is direct one-to-one mapping. For node SONG and
Below example to explain different between sort and sortByKey. Source and target message type: Source data is unsorted col1 and sorted col2. Both col1 and col2 is a pair of values. Target data should be sorted col1, and the col2 is
Previous post useOneAsMany explained in easy example used an example to convert tree structure into flat structure by using useOneAsMany. This post will do the reverse, convert flat structure back to tree structure. The source message type is flat structure.
useOneAsMany is a very useful function to repeat header level-like data, as many time as needed at detail-level data, and still follow desired context change pattern. It is difficult to explain this function using words and sentences only, let’s understand
mapWithDefault is useful to handle those cases where the source message field is expected, but might not be existed. Example in previous firstname lastname to fullname example, both firstname and lastname is expected to be concatenated. Before implement mapWithDefault:
The objective of this post to demonstrated all the relevant common ESR objects required to establish a simple PI mapping. This simple PI mapping will map source message with 2 fields (firstname and lastnam) to target message (fullname). Here are