Range validation checks whether a value sits inside acceptable limits.Advanced ETL Processor Enterprise validates numeric, date, and business ranges inside a visual ETL workflow, rejects or routes failed rows, logs the failure reason, and keeps the original source data unchanged. It catches negative quantities, impossible ages, strange percentages, and prices that look like someone leaned on the keyboard during lunch.
Ranges turn common sense into a rule
Some values are valid by type but wrong in practice. A discount of 500 is numeric. It is also probably not what the business intended unless the sales team has become unusually generous.
Advanced ETL Processor runs range checks inside the workflow, so suspicious values are caught before loading or downstream automation.
Typical range checks
Quantities must be greater than zero.
Percentages must sit between 0 and 100.
Dates must fall inside the reporting period.
Prices, weights, and measurements must stay within expected limits.
Use ranges carefully
A rule that is too narrow blocks legitimate exceptions. Start with limits the business can defend, then review the rejected rows. Validation protects the process; it does not argue with reality for sport.
If this validation rule belongs in a repeatable ETL process, configure it in the Validator object, test it on a sample file, then decide whether failed rows should be rejected, logged, or routed for review.
