Use SemQL at run-time


Every data view within an application supports filtering capabilities in the form of conditions.

A condition can utilize all entity attributes, related entities, and relevant built-in attributes depending on the accessed view. For example, when viewing a golden record, attributes such as BatchID, ClassName, CreationDate, UpdateDate, Creator, and Updator are available.

Duplicate filtering

When filtering duplicates (e.g., to filter records to check out during a duplicate management operation), it is possible to use Record1 and Record2 as in a matcher, except that the comparison is conducted between pairs of matched records.


To show matching records with CustomerName fields that are less than 95% similar:

SEM_EDIT_DISTANCE_SIMILARITY(Record1.CustomerName, Record2.CustomerName) < 95