Siebel Data Quality Administration Guide > Siebel Data Quality Concepts > Identification of Candidate Records >

Identification of Candidate Records with the Universal Connector

SDQ queries the database for candidate records by using a Dedup Query Expression specific to the current Business Component. A Dedup Query Expression is used rather than the related Dedup Token Expression, for the following reason: If a user does not specify a value for any of the fields that compose the Dedup Token Expression, then the token is constructed with an underscore (_) instead of a value in the part of the expression that corresponds to that field. If the token were to be used in a query, the effect would be for the query to seek records that had NULL values in corresponding fields. In contrast, the Dedup Query Expression replaces each underscore in the Dedup Token Expression with a '?' wildcard character that matches any single character, leading to the desired query results.

You can customize both the Dedup Token Expression and the Dedup Query Expression by using Siebel Tools to change the values of these Business Component user properties. The configuration of these expressions must be consistent with the internal matching logic of the vendor, which is different for each vendor. For optimal results therefore, change these values only after consulting the relevant vendor.

See Table 3 for information about how the default expressions differ for different business components. These values are applicable for Firstlogic.

The maximum number of candidate records that are sent to the third-party software at one time is determined by the value of the following user properties of the DeDuplication business service:

• Realtime Max Num of Records. Used in real time, the default value is 200.
• Batch Max Num of Records. Used in batch mode, the default is 200.