Filter datasets

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2025

Filter dataset gives you the ability to create alerts based on specific filter conditions on the dataset. You can add single or multiple filter conditions. These conditions are applied to the table fields.You should be familiar with Observer creation steps and have a basic knowledge of filter operators before performing this task.

Observe filtered datasets

You can use filtered datasets to generate volume, data drift, and freshness alerts. Use these steps to filter selected datasets.

To filter selected datasets:
  1. On the main navigation menu, click Observability > Observers and select + Create Observer. The Create Observer page appears.
  2. Select the datasets and fields that you want to observe and click Next.
  3. Select the Filter Selected Datasets link.
  4. Select the dataset that you want to filter.
  5. Select the fields, operator, and type value. You can add more than one condition. You can choose Match All to match all conditions within the group (the logical AND), or you can choose Match Any to match any condition within the group (the logical OR).
  6. Complete remaining steps of Observer creation.

The Observer is saved with the selected filter conditions, and you are redirected to the Observers page

Considerations when using filter datasets

  • When you filter using datetime values, it is assumed that the values are in UTC timezone.
  • When dealing with float values, the values you provide are rounded to two decimal places. These rounded values are used for filtering. For example, if you enter a value like 100.2367, it will be rounded to 100.24 for filtering purposes.
  • The where clause may have a column that is not in the observed column list for the given table/dataset.
  • The column used in the where clause must be a cataloged column.
  • If the filter conditions are changed, it will be considered as a change in the data itself, resulting in an increase or decrease in volume, which will generate an alert.

Limitation with quoted database objects

Review your data assets for tables or columns with single or double quotes in their names, like ‘TableName’ or “ColumnName”. Quoted database objects can cause Observer runs to fail. Consider renaming affected objects without quotes.

Workaround

Consider renaming affected database objects without quotes or using naming conventions that avoid quotes.
Note: The filter dataset link is accessible only when you have at least one Data Integrity Suite asset. You cannot use the filter dataset link when the selected assets belong to datasets that are not part of the Data Integrity Suite.

For example, the condition, Firstname equal Joe, where Firstname is the field, equal is the filter condition, and Joe is the value, will generate alerts and profiling results for the table with fields that has a value equal to Joe.

The profiling statistics are also generated based on the filtered set only and not the entire dataset. For example, a table that has a total of 100 records (without filter) displays only 10 records, in this case, all statistics are calculated based on the filtered records (10 in this case).