Build a Simple Data Preparation Flow
Overview
This case shows how to use Smart ETL to perform data preparation efficiently. You will learn how to combine product data, store data, and retail transaction data into a single sales detail table that is ready for further analysis.
The sample datasets used in this case are available in ETL Sample Data.
Prerequisites
- Create folders in
Data Preparation > DatasetandSmart ETLto store the input datasets and Output Datasets for this example. You can name the folderStore Sales Statistics. - Under
Data Preparation > Dataset, ingest the three file datasets used as the raw source data.
Steps
- Open
Smart ETL, create a new ETL task in the folder, and name the task. - Drag the
Input Datasetoperator into the canvas three times and select the product table, store table, and retail table. - Use multiple ETL operators to merge the three source tables, remove dirty data, and add calculated columns to create a sales detail table suitable for visual analysis.
- Drag the
Output Datasetoperator into the canvas, preview the data flow and result, confirm the logic, and then save and run the ETL task. - After the task runs successfully, review the result or adjust the task configuration if needed.
Create a New ETL Task
-
In the target folder under
Smart ETL, clickAdd ETL.
-
After the task is created, the system opens the ETL editor directly.

-
Rename the task to
ETL_Store Sales Statisticsand choose the storage path.
Build the ETL Flow
Add Input Datasets
Drag the Input Dataset operator into the canvas and select datasets:
- 1.0 Product Information
- 2.0 Store Information
- 3.0 Retail Details

Configure Table Joins
Use Join Data to combine the three datasets into one so that you can produce product sales details for each store.
- Drag the
Join Dataoperator into the canvas and connect the three Input Datasets. - Configure the joins using the following Left Join rules:
3.0 Retail Details / Product ID = 1.0 Product Information / Product ID3.0 Retail Details / Store ID = 2.0 Store Information / Store ID
- Select the columns to output. Since
3.0 Retail Detailsis the main table, avoid selecting duplicate join fields from the secondary tables.

Remove Invalid Dirty Data
When the source data contains large amounts of dirty data, or only part of the data is needed, use Filter Data Rows.
In this example, rows related to Coffee are excluded because they are not included in store consumption analysis.
- Drag the
Filter Data Rowsoperator into the ETL canvas. - Add the filter conditions: Category
!= Coffee
