Skip to content

Not Exists In single field

The NotExistIn rule type serves to validate data integrity by ensuring that values assigned to a specific field in a table do not exist as values in another field. This type of rule is useful in scenarios where you want to enforce uniqueness or exclusion constraints between two tables.

Asserts that values assigned to this field do not exist as values in another field.

Accepted Field Types
Date
Timestamp
Integral
Fractional
String
Boolean

Screenshot Screenshot

Example

Account_fk not exists in Account_id.

You can select the same or a different datastore to assert that the compared table/file not exists in the source table/file.

The [field_name] value of '[x value]' does exist in [compared_field_name].

In [field_names], [x]% of the filtered values do exist in [compared_field_name].

Last update: September 29, 2023