1.7

instance of that node. For example, if a client node contains multiple invoice nodes, the
information for the client node can be duplicated for each invoice.
The DataMapper only extracts elements for which at least one value or attribute value is
defined in the file.
Boundaries
Boundaries are the division between records: they define where one record ends and the next
record begins; for an explanation see "Record boundaries" on page94.
CSV or Database file boundaries
Since database data sources are structured the same way as CSV files, the options for these
file types are identical.
l
Record limit: Defines how many records are displayed in the Data Viewer. This does not
affect output production; when generating output, this option is ignored. To disable the
limit, use the value 0 (zero).
l
Line limit: Defines the limit of detail lines in any detail table. This is useful for files with a
high number of detail lines, which in the DataMapper interface can slow down things.
This does not affect output production; when generating output, this option is ignored. To
disable the limit, use the value 0 (zero).
l
Trigger: Defines the type of rule that controls when a boundary is set, creating a new
record.
l
Record(s) per page: Defines a fixed number of lines in the file that go in each
record.
l
Records: The number of records (lines, rows) to put in each record.
l
On change: Defines a new record when a specific field (Field name) has a new
value.
l
Field name: Displays the fields in the top line. The boundaries are set on the
selected field name.
l
On script: Defines the boundaries using a custom JavaScript. For more information
see "Setting boundaries using JavaScript" on page233.
Page 181