Advanced ETL Processor can chain multiple Validator rules on one input field. A record is treated as validated only when every connected rule succeeds, so use chained validation when one field must pass type, range, format, or business-rule checks before it reaches the writer.
What You Will Learn
- Add more than one validation rule to the same input field.
- Join validation rules so all checks must pass.
- Debug validation results from the Validator screen.
- Understand reject and discard behavior when rules fail.
Before You Start
Use sample data with known good and bad rows. Validation rules are easier to trust when you have watched them fail for the right reasons first.
Validator Docs
The Validator documentation explains how Advanced ETL Processor checks incoming data against user-defined rules before the records continue through the transformation.
For chained validation, start with debugging validation. That section shows how to process test data, edit values in the grid, open validation rule properties, and apply several validation rules to one input field by joining them.
The important rule is simple: data is valid only when all connected validation rules succeed. The docs also note that if one rule rejects a record and another discards it, the record is discarded. That priority matters when you mix strict data-quality checks with rules that intentionally remove rows from the output.
Use the validation rules section to pick the right rule type, including strings, numbers, dates, times, miscellaneous checks, and regular expressions.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.