1.7

Note
If you stop processing any record after you’ve already extracted some data from it, then
the record will still be stored in the database, with un-extracted fields being assigned
whatever default value (if any) you defined for them. So if your goal is to completely
prevent unwanted records from being stored in the database, you should make sure to
implement your filtering conditions early in the data mapping process.
Improved naming of default fields
The default field naming scheme has been enhanced to allow duplicate field names to be
generated automatically as long as they are on different levels (or in different detail tables).
This is especially useful with XML data sources where field names (e.g., ID, NAME) are often
re-used through different levels of the structure.
With the new, more flexible naming scheme, the DataMapper checks for duplicates at the same
level before deciding whether or not to create or increment a numeric suffix that is appended to
the field name. (SHARED-42645)
Improvements made to XMLFile Processing
Issues were encountered with repeated nodes in XML datasets. In XML when adding an
Extraction step, the XPath was not generated with an index, which resulted in only the first
node being returned. This has been fixed, and repeated nodes are now catered for. (SHARED-
28107/32238)
Improved support for Multi-Byte Encoding
Added support for byte based positioning in addition to the existing character based positioning
for MultiByte (Big5, GB18030, UTF-8 and Shift-JIS) text files. (SHARED-53174)
Page 907