Splitter FAQ

What kind of problem is Splitter best for?

Splitter is best when one dataset needs to become multiple outputs based on clear routing rules.

If the main question is "which output should each Record go to?", Splitter is usually a strong fit.

How is Splitter different from Filterer?

Filterer usually produces one targeted subset.

Splitter produces multiple outputs from the same input.

Should I clean data before splitting?

Clean first if the routing values are inconsistent.

For example, region values like East, EAST, and E. may need standardization before routing will be reliable.

What should happen to Records that do not match any output?

Plan for them explicitly.

Many teams create an exception or unmatched output so unexpected records can be reviewed instead of silently disappearing from the workflow.

Can a Record belong to more than one output?

That depends on the configuration and business rule.

Before building the setup, decide whether outputs should be mutually exclusive or whether overlapping outputs are acceptable.

What should I review after a run?

Review Record counts, known sample Records in each output, boundary cases, and any exception or unmatched output.

What if an output is empty?

An empty output may be correct, but it should be checked.

Confirm that the input contained records for that group and that the routing rule still matches the source values.

When should I use another Tool first?

Use another Tool first when source values need cleaning, duplicates need resolution, Files need joining, or the main need is a single filtered subset.