Powerbuilder xml import template

An XML template has a Header section and a Detail section, separated graphically by a line across the tree view. For group DataWindow objects, you can choose to generate the contents of the header section iteratively for each group. For more information, see Generating group headers. The Detail section contains the row data, and is generated iteratively for each row in the DataWindow object.

The Detail Start element. There can be only one Detail Start element, and it must be inside the document's root element. By default, the first child of the root element is the Detail Start element.

It usually wraps a whole row, separating columns across rows. Any elements in the root element above the separator line are generated only once, unless the DataWindow is a group DataWindow and the Iterate Group Headers check box has been selected.

The Detail Start element can be a nested or multiply-nested child of an element from the Header section, permitting a nested detail. You can change the location of the separator line by selecting the element that you want as the Detail Start element and selecting Starts Detail from its pop-up menu. The separator line is redrawn above the new Detail Start element. When you export the data, the Detail Start element and the children and siblings after it are generated iteratively for each row.

If no Detail Start element is specified that is, if the Starts Detail option has been deselected , the template has only a Header section. When you export the data, only one iteration of row data is generated. The Header section can contain the items listed in the following table. Only the root element is required:. This must be the first item in the tree view if it exists. See XML declaration. If there is an XML declaration, the document type declaration must appear after the XML declaration and any optional processing instructions and comments, and before the root element.

Otherwise, this must be the first item in the tree view. See Document type declaration. See Processing instructions. See Root element. The template used in this example includes only these columns. Any other columns in the DataWindow remain empty when you import using this template. It also has three children:. The following shows the beginning of the XML exported using this template:. Before importing, you must set the import template on the Data Import page in the Properties view or in a script using the DataWindow object's Import.

When there is no import template assigned to a DataWindow object with the UseTemplate property, PowerBuilder 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 DataWindow column definition. The same restriction applies when you import data from a text file with the ImportFile method.

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. Empty elements elements that have no content between the start and end tags are imported as empty values into the DataWindow column. If the element text contains only white space, carriage returns, and new line or tab characters, the element is treated as an empty element.

Elements with non-text content. If the element has no text content, but does contain comments, processing instructions, or any other content, it is not regarded as an empty element and is skipped for import. This example contains two rows, each with five elements that match the column order, type, and validation requirements for the DataWindow object.

In this example, the elements are not contained in rows, but they still match the DataWindow object. The comments and processing instructions in this example are not imported.

The first has no content, and the second has an attribute but no content. Both are imported as empty elements. When you import data from XML with or without a template, you can create a trace log to verify that the import process worked correctly. The trace log shows whether a template was used and if so which template, and it shows which elements and rows were imported. If you do not specify a name for the trace file, PowerBuilder generates a trace file with the name pbxmtrc.

You can also use the Import. Trace and Import. TraceFile DataWindow object properties. The result is 29 rows added to the DataWindow with data in columns 5 through JavaScript is disabled on your browser.

Please enable JavaScript to enjoy all the features of this site. Valid type arguments for ImportFile are: Text! This argument has no effect on template XML import. Specifying a null string for filename If you specify a null string for filename, the remaining arguments are ignored. Count ContentsAllowed Criteria Criteria.

HTML obsolete Data. XML Data. XMLSchema Data. XMLWeb obsolete Data. CustomPostScript Export. Method Export. CustomOrientation Export. CustomSize Export. ImageFormat Export. MasterPassword Export.

PDFStandard Export. Restrictions Export. UserPassword Export. UsePrintSpec Export. Print Export. TemplateCount Export. All developers, even novices and hobbyists, must be a XML import in powerbuilder I am running into a weird problem. I am trying to call a webservice method that returns an XML string.

Then I import it into a datawindow using importstring method. This is a customer query. When I query for a single record, it sends me valid XML that I can import, but when queried on multiple records, the xml generated is not being imported. Then I tried to craete a template for import process. When I do that, import returns me I have compared the datatypes and order of fields with the XML elements, they all match. I have to import a XML file containing order headers and order items.

So I thought I can achieve that using a grouped DataWindow but that seems to be wrong. It has been in use since , peaking around