Specifications

CHAPTER 12 Exporting and Importing XML Data
Users Guide 395
</name>
</employee>
<employee dept_id="100">
<emp_id>105</emp_id>
<emp_fname>static text content</emp_fname>
<name>
<emp_fname>Matthew</emp_fname>
<emp_lname>Cobb</emp_lname>
</name>
</employee>
...
The exported XML can be reimported into the report columns dept_id, emp_id,
emp_fname, and emp_lname. Before importing, you must set the import
template on the Data Import page in the Properties view.
The following items are exported, but ignored on import:
• The before_detail_marker element is ignored because it is in the header
section.
• The first occurrence of the element tag name emp_fname is ignored
because it does not contain a mapping to a report column name.
If you change the nesting of the emp_fname and emp_lname elements inside
the name element, the import fails because the order of the elements and the
nesting in the XML and the template must match.
Default data import
When there is no import template assigned to a report with the UseTemplate
property, InfoMaker attempts to import the data using the default mechanism
described in this section.
Elements that contain
text
The text between the start and end tags for each element can be imported if the
XML document data corresponds to the report column definition. For example,
this is the case if the XML was exported from InfoMaker using the default
XML export template.
The text content of the XML elements must match the column order, column
type, and validation requirements of the report columns.
All element text contents are imported in order of occurrence. Any possible
nesting is disregarded. The import process ignores tag names of the elements,
attributes, and any other content of the XML document.