Description:

The Transform Number to String step is an ETL transformation component that converts one or more numeric fields into string values.

Many enterprise integrations require numeric information to be transmitted as text. Examples include CSV exports, fixed-width files, XML documents, JSON payloads, legacy applications, reporting systems, and third-party integrations where numeric values must be represented as strings to satisfy interface or formatting requirements.

The step is configured through a transformation list that specifies which numeric columns to convert to string values.

During execution, the ETL engine processes each incoming record, evaluates the configured transformation mappings, converts the selected numeric fields into strings, and forwards the transformed dataset to the next ETL component.

Only the configured columns are converted. All remaining columns continue through the ETL pipeline unchanged.

The step supports:

• Number-to-string conversion
• Multiple column transformations
• Configurable transformation mappings
• Data formatting for exports
• Enterprise ETL workflows
• Integration with FlowWright ETL pipelines

Typical business uses include:

• CSV exports
• XML generation
• JSON generation
• Legacy system integrations
• Financial reporting
• ERP data exchange
• Business intelligence exports

Usage:

The Transform Number to String step is typically positioned after calculations, aggregations, or other numeric processing and before file generation or data export components.

During execution:

1. The incoming ETL dataset is received.
2. The configured transformation list is evaluated.
3. Selected numeric columns are converted into string values.
4. All remaining columns pass through unchanged.
5. The transformed dataset continues to downstream ETL components.

A typical ETL pipeline might look like this:

Typical usage scenarios include:

• Preparing sales totals for CSV export
• Formatting invoice amounts for XML generation
• Converting inventory quantities for legacy applications
• Creating text-based data exchange files
• Preparing financial reports
• Exporting datasets for third-party integrations
• Generating formatted business reports

After conversion, the transformed values can be exported to text-based formats or consumed by systems that expect character data.

Prerequisite:

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

Example:

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

• Create a new ETL definition called “clsTransformFormatNumberToStringDef” and open the definition in designer mode. 
• Drag “clsInputCSV, clsTransformFormatNumberToString, and clsOutputCSV” steps to the canvas. 
• Connect the dots between the “clsInputCSV” step and other steps, as shown above.
• Define a variable or a global variable to hold the virtual path.
• Click the "clsInputCSV" step to configure its "Required" properties. Provide a name for the step. Specify the path to the input CSV file on the application server. Select the ETL data schema from the drop-down list. Note: The schema's column names should match those in the input file. Click the Save button. Click here to learn about the ETL Data Schema Designer.

• Click the "clsTransformFormatNumberToString" step to configure its "Required" properties. Provide a name for the step. Click the button to configure the transform list, then click the Save button. 

• Click the "clsTransformFormatNumberToString" step to configure the transform list. The configuration pop-up window appears. Click the Add Row (+) button to insert an empty row. Select the number as the input source column and the string as the output target column. Click the Save button. You may add multiple transformation rows using the Add Row button. 

• Click the "clsOutputCSV" step to configure its "Required" properties. Enter a name for the step. Enter the path to the output CSV file on the application server. Click the Save button. 

• Click the "clsOutputCSV" step to configure its "Optional" properties. Provide a name for the step. Provide a variable or global reference to store the virtual output path. Click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved 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 ETL instance, and execute. Render the ETL instance. Click the ETL step to view its properties. The “clsTransformFormatNumberToString” step should transform the value to a string and store it in the output file. The variable or global holds the output file’s virtual path as shown below. 

Tips:

• Configure transformations only for numeric columns that need to be exported as text.
• Perform all calculations and aggregations before converting numbers to strings.
• Keep transformation mappings synchronized with the incoming dataset schema.
• Validate numeric values before conversion to ensure consistent output.
• Test exported files with downstream systems to verify formatting compatibility.
• Convert only the required columns to reduce unnecessary processing.
• Combine this step with MSSQL Input File, Aggregate Transform, Group By Transform, CSV Output File, Excel Output File, XML Output File, JSON Output File, or Transform String to Number to build complete enterprise ETL workflows.

Notes:

• Only the columns defined in the transformation list are converted into string values.
• All other columns remain unchanged.
• The transformation list should match the incoming dataset schema.
• Because this is an ETL transformation component, it requires both an incoming and an outgoing connection.
• Conversion errors and processing statistics are recorded in the ETL execution log.
• This step is commonly used for enterprise reporting, ERP integrations, financial exports, XML and JSON generation, business intelligence publishing, and data exchange with legacy systems.

Transform Number to String vs. Transform String to Number:

Both components perform format conversions, but they are designed for opposite conversion directions.

As a general guideline:

• Use Transform Number to String when numeric values must be exported as text for reports, CSV files, XML documents, JSON payloads, or legacy integrations.
• Use Transform String to Number when imported string values must be converted into numeric data types before calculations, validation, aggregation, or storage.

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:

• Transformation mappings
• Source column names
• Number-to-string conversion requirements
• Upstream processing configuration
• Downstream output configuration
• Export formatting requirements

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

Click here to download the sample file.