Description

The Filter Rows step allows you to filter rows based on conditions and comparisons. Once this step is connected to a previous step (one or more and receiving input), you can click on the "<field>", "=" and "<value>" areas to construct a condition.

To enter an IN LIST operator, use a string value separated by semicolons. This also works on numeric values like integers. The list of values must be entered with a string type, e.g.: 2;3;7;8

Options

Click the NOT to negate the condition.

Click <Field> to select from a list of fields from the input stream(s) to build your condition(s). <value> to enter a specific value into your condition(s).

To delete a condition, right-click and select Delete Condition.
|

Filtering

Filtering Rows Based on Values from Variables

The filter rows step detects only fields in the input stream. If you want to filter rows based on a variable value, you must modify the previous step (a table input for example) and include the variable as another field, for example:

${myvar}=5

A query:

SELECT field1,
field2,
${myvar} AS field3 
FROM table
WHERE field1=xxxx

Then in the filter row condition, you can have

field1 = field3

FYI - instead of the Table Input trick above you can use the simple "Get Variables" step to set parameters in fields.

Filtering Special Characters

To filter special characters like explicit EOF (e.g. from old cobol files) Use a REGEX expression in the "filter row" step with the syntax: "\x{1A}" where \x mean HEX representation and 1A into parenthesis is the EOF char to match in HEX.

Metadata Injection Support (7.x and later)

All fields of this step support metadata injection. You can use this step with ETL Metadata Injection to pass metadata to your transformation at runtime.

Special Considerations for the Condition Field:

The Filter Rows step is a special MDI scenario, since it has a nested structure of filter conditions. The condition is given in XML format. The condition XML has the same format as we store the transformation metadata in a .KTR file in XML format. We do not have a DTD (Document Type Definition) for the .KTR XML format, nor the condition.

It is easy to get to an XML condition:

1. Create a sample Filter step with the different conditions you need. This sample step gives you all the information, such as the values for the functions you use.
2. Select the step, copy it to the clipboard, and then paste it into a text editor. Alternatively, you can store the .KTR, and then open the .KTR in a text editor.
3. Find the <condition> element and its nested elements and modify it accordingly to use it in your MDI scenario.