Skip to main content Skip to complementary content

tFileOutputXML Standard properties

These properties are used to configure tFileOutputXML running in the Standard Job framework.

The Standard tFileOutputXML component belongs to the File and the XML families.

The component in this framework is available in all Talend products.

Basic settings

File Name

Name or path to the output file or the variable to be used.

Related topic: see Defining variables from the Component view.

Information noteWarning: Use absolute path (instead of relative path) for this field to avoid possible errors.
Incoming record is a document

Select this check box if the data from the preceding component is in XML format.

When this check box is selected, a Column list appears allowing you to select a Document type column of the schema that holds the data, and the Row tag field disappears.

When this check box is selected, in the Advanced settings view, only the check boxes Create directory if not exists, Don't generate empty file, Trim data, tStatCatcher Statistics and the list Encoding are available.

Row tag

Specify the tag that will wrap data and structure per row.

Schema and Edit Schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

    If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.


Built-In: You create and store the schema locally for this component only.


Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Sync columns Click to synchronize the output file schema with the input file schema. The Sync function only displays once the Row connection is linked with the input component.

Advanced settings

Split output in several files

If the output is big, you can split the output into several files, each containing the specified number of rows.

Rows in each output file: Specify the number of rows in each output file.

Create directory if not exists This check box is selected by default. It creates a directory to hold the output XML files if required.
Root tags

Specify one or more root tags to wrap the whole output file structure and data. The default root tag is root.

Output format

Define the output format.

  • Column: The columns retrieved from the input schema.

  • As attribute: select check box for the column(s) you want to use as attribute(s) of the parent element in the XML output.

Information noteNote:

If the same column is selected in both the Output format table as an attribute and in the Use dynamic grouping setting as the criterion for dynamic grouping, only the dynamic group setting will take effect for that column.

Use schema column name: By default, this check box is selected for all columns so that the column labels from the input schema are used as data wrapping tags. If you want to use a different tag than from the input schema for any column, clear this check box for that column and specify a tag label between quotation marks in the Label field.

Use dynamic grouping

Select this check box if you want to dynamically group the output columns. Click the plus button to add one ore more grouping criteria in the Group by table.

Column: Select a column you want to use as a wrapping element for the grouped output rows.

Attribute label: Enter an attribute label for the group wrapping element, between quotation marks.

Custom the flush buffer size

Select this check box to define the number of rows to buffer before the data is written into the target file and the buffer is emptied.

Row Number: Specify the number of rows to buffer.

Advanced separator (for numbers)

Select this check box to change the separator used for numbers. By default, the thousands separator is a comma (,) and the decimal separator is a period (.).

Thousands separator: define separators for thousands.

Decimal separator: define separators for decimals.


Select the encoding from the list or select Custom and define it manually. This field is compulsory for database data handling. The supported encodings depend on the JVM that you are using. For more information, see

Don't generate empty file Select the check box to avoid the generation of an empty file.

Trim data

Select this check box to remove the spaces at the beginning and at the end of the text, and merge multiple consecutive spaces into one within the text.

tStatCatcher Statistics Select this check box to gather the Job processing metadata at a Job level as well as at each component level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.


Usage rule

Use this component to write an XML file with data passed on from other components using a Row link.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!