Object filter with fixed values

You can define a fixed filter value at source level. You can define them for both sources or for one only). The filter value is used during the generation to create a hard-coded where clause.

Not visible in comparison instances. Filter is valid for all comparison instances of this comparison object, that is, each comparison instance automatically uses this filter as a fixed attribute.

Fetches data from generated extractor using the hard-coded where clause.

Instance filter with variable values

Instance Filter flag is selected in comparison object, either at mapping level (relevant for both sources) or at source level (relevant for one source only).

You can maintain the actual filter values in the comparison instance. They are used for all comparison runs of this comparison instance.

The comparison run passes the filters to the extractor which handles the filter values dynamically.

Object filter with relative dates

If a filter for a comparison object contains the syntax for relative dates (starting with $), it is not generated as a hard-coded filter in the extractor.

Not visible in comparison instances. Filter is valid for all comparison instances of this comparison object.

The comparison run translates the relative date syntax into an absolute time stamp and passes the filters to the extractor which handles the filter values dynamically.

Instance filter with relative dates

Instance Filter flag is selected in comparison object, either at mapping level (relevant for both sources) or at source level (relevant for one source only).

You can maintain the relative date syntax (starting with $) in the comparison instance. The filters are used for all comparison runs of this comparison instance.

The comparison run translates the relative date syntax into an absolute time stamp and passes the filters to the extractor which handles the filter values dynamically.