Description:
This step calculates and summarizes numeric data using the Pivot function.
Inputs
- pivotRows – select pivot rows
- column - select column
- pivotColumns - select pivot columns
- operation - select pivot operation
- outColumn - provide output column name
- pivotValues - select pivot value
- showRowGrandTotal - show row grand total
- showColumnGrandTotal - show column grand total
Returns
- None
Usage:
Prerequisite:
The ETL process engine service should be running to execute the ETL definitions.
Example:
Let’s build and execute the “clsPivotTransformDef” example.
- Create a new ETL definition named “clsPivotTransformDef” and open it in designer mode.
- Drag the “clsInputCSV, clsPivotTransform, and clsOutputCSV” steps to the canvas.
- Connect the dots between the “clsInputCSV” and other steps, as shown above.
- Define a variable or a global 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 "clsInputCSV" step to configure its "Optional" properties. Select the Show Schema button. The pop-up window displays the schema columns as shown below. This function helps to understand the schema at a glance.
- Click the "clsPivotTransform" step to configure its "Required" properties. Provide a name for the step. Click the button to configure the Pivot Columns. Then click the Save button.
- Click the button to configure the Pivot Columns. A pop-up window appears for configuration. Click the Add Row (+) button to insert an empty row. Select the column name from the drop-down list. Click the Save button. You may add multiple pivot columns for transformation by using the Add Row button.
- Click the button to configure the Pivot Values. A pop-up window appears for configuration. Click the Add Row (+) button to insert an empty row. Select the column name from the drop-down list. Select the pivot operation from the drop-down list below. Click the Save button. You may add multiple pivot values for transformation by using the Add Row button.
- Click the "clsPivotTransform" step to configure its "Optional" properties. A pop-up window appears for configuration. Click the button to select Pivot Rows. Click the Add Row (+) button to insert an empty row. Select the column name from the drop-down list. Click the Save button. You may add multiple pivot rows for transformation by using the Add Row button. Select “Yes” to include the total computation for the row and column.
- 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.
- 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.
- Save the ETL definition, create a new ETL instance, and execute. Render the ETL instance. The “clsPivotTransform” step should calculate and summarize numeric data using the Pivot function. The variable or global holds the output file’s virtual path as shown below.
- The ETL transform pivot output file is included for reference.
- A similar pivot function output from Excel is provided here for reference.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright ETL Definition (XML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.