Description:

The XML Input File step is an ETL source component that loads data from an XML file and converts XML elements into a tabular dataset that FlowWright ETL components can process.

The step is configured by specifying:

• The XML file location
• The XML element that represents individual records
• The column schema used to map XML elements into ETL columns
• The schema viewer for validating the imported structure

During execution, the ETL engine opens the specified XML document, identifies the configured repeating XML element, maps each XML node according to the selected schema, and creates an in-memory dataset that becomes the source for the remainder of the ETL pipeline.

XML is widely used for enterprise system integration because it provides a structured, self-describing format suitable for exchanging business data between ERP systems, CRM platforms, accounting software, government portals, web services, and legacy applications.

The XML Input File step eliminates the need for custom XML parsing logic by providing a configurable XML reader that integrates directly with FlowWright ETL.

The step supports:

• XML file import
• Configurable record element selection
• Column schema mapping
• XML schema validation
• Enterprise ETL workflows
• Integration with FlowWright ETL pipelines

Typical business uses include:

• ERP data imports
• CRM data migration
• Product catalog imports
• Customer master synchronization
• Financial transaction imports
• Government XML reporting
• Enterprise application integration

Usage:

The XML Input File step is typically the first component in an ETL pipeline because it serves as the source of the dataset.

During execution, the XML file is opened, the specified repeating element is identified, the configured schema is applied, and each XML record is converted into an ETL row.

A typical ETL pipeline might look like this:

Typical usage scenarios include:

• Importing customer master data
• Processing XML invoices
• Migrating ERP records
• Synchronizing inventory information
• Importing purchase orders
• Processing government XML submissions
• Loading XML data into reporting databases

The imported dataset can immediately be validated, transformed, filtered, grouped, aggregated, or exported using subsequent ETL components.

Prerequisite:

The ETL process engine service should be running to execute the ETL definitions.

Tips:

• Use absolute or environment-specific file paths that are accessible to the ETL server.
• Ensure the configured element name matches the repeating record element within the XML document.
• Verify the column schema before executing the ETL definition.
• Use the Show Schema option to validate imported fields during ETL design.
• Validate imported datasets immediately after reading the XML file to detect missing or malformed values.
• Preserve consistent XML structures across integration partners to simplify maintenance.
• Combine this step with Validate Data, Transform Date by Format, Transform Text Trim, Filter with Conditions, Group By Transform, JSON Output File, SQL Output, or CSV Output File to build complete enterprise ETL workflows.

Notes:

• The XML file must be accessible to the FlowWright ETL server.
• The configured element name determines which XML nodes become ETL records.
• The selected column schema defines the dataset structure used throughout the ETL pipeline.
• The Show Schema property helps verify imported fields during ETL design.
• XML parsing errors, invalid schemas, or inaccessible files may cause ETL execution errors.
• Because this is an ETL source component, it has no incoming connections and serves as the starting point of the ETL pipeline.
• This step is commonly used for enterprise integrations, ERP migrations, CRM synchronization, financial imports, regulatory reporting, data warehouse loading, and business intelligence solutions.

XML Input File vs. JSON Input File:

Both components import structured data into FlowWright ETL, but they are designed for different source formats.

As a general guideline:

• Use XML Input File when importing XML documents from enterprise systems or legacy applications.
• Use JSON Input File when importing data from REST APIs, cloud platforms, or JSON-based services.

Example:

Let’s build and execute the “clsInputXMLDef” example.          

• Create a new ETL definition named “clsInputXMLDef” and open it in designer mode. 
• Drag “clsInputXML, clsTransformCase, and clsOutputXML” steps to the canvas. 
• Connect the dots between the “clsInputXML” step and other steps, as shown above.
• Define a variable or global to hold the virtual path. 
• Click the "clsInputXML" step to configure its "Required" properties. Provide a name for the step. Specify the path to the input XML file on the application server. Specify the XML node element name that contains all the data. Select the ETL data schema from the drop-down list. Note: The schema's column names should match those in the input file. Click Save. Click here to learn about the ETL Data Schema Designer.

• Click the "clsInputXML" step to view its "Optional" properties. Select the Show Schema button. The pop-up window displays the schema columns as shown below. This function helps you understand the schema at a glance.  

• Click the "clsTransformCase" step to configure its "Required" properties. Enter the step name. Click the button to configure the transform list, then click Save. 

• Click the "clsTransformCase" step to configure the transform list. The configuration pop-up window opens. Click the Add Row (+) button to insert an empty row. Select the column name (string type) from the drop-down list. Select the case transformation type from the drop-down list. Click the Save button. You can add multiple rows to the transformation using the Add Row button. 

• Click the "clsOutputXML" step to configure its "Required" properties. Enter a name for the step. Enter the path to the output XML file on the application server. Then click the Save button. 

• Click the "clsOutputXML" step to configure its "Optional" properties. Enter the XML root element name, XML node name, and the variable/global reference for the virtual output path. Click the Save button. 

• The “Logging” configuration is necessary for documentation and to measure workflow progress and percent complete. This is done by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the ETL definition, create a new instance, and execute it. Render the ETL instance. Click Items > Variables to view the variable values. The “clsInputXML” step performs the transformation of the input file. The variable or global holds the output file’s virtual path, as shown below. 

• The input XML image is provided for reference. 

• The output XML image is provided for reference. 

Definition Sample:

You may download the sample ETL definition(s) from the link provided and later import them into your FlowWright ETL Designer.

Note: Verify and complete any missing configuration after importing the sample, including:

• XML file location
• Record element name
• Column schema selection
• Schema validation
• Downstream transformation mappings
• Destination component configuration
• Environment-specific file paths

After verifying the configuration, save the ETL Definition before execution.

Click here to download the sample file.