To match and merge duplicate records, add declarative match rules to the match model. For example, to match duplicate individuals based on name and address, add a fuzzy rule with the Resident match criteria.
Before you add declarative match rules to a match model, review any rules that the match model might include for the business entity. You might want to edit or delete any existing rules.
You can't configure declarative match rules for dynamic fields.
To create a declarative rule, perform the following tasks:
When you configure declarative match rules, ensure that you select a suitable match strategy. If you select a fuzzy match strategy, ensure that you select the correct match criteria as well. After you save the rules, you can't change the match strategy and the match criteria.
1Open the business entity, and click the Match tab.
The Match Models page appears.
2Click the name of the match model to which you want to add the declarative match rules.
3On the Declarative Rules page, click Edit.
4Click the Add Declarative Rule icon.
The Add Declarative Rule wizard appears.
5On the Configure Properties and Thresholds page, select one of the following match strategies:
Option
Description
Exact
A deterministic match that includes records containing identical values.
Fuzzy
A probabilistic match that includes variations in data patterns, such as misspellings, omissions, and phonetic variations.
Add the required fields based on the match strategy that you selected. If you selected an exact or fuzzy match strategy, you can configure exact match fields. If you selected the fuzzy match strategy, you can configure fuzzy match fields only.
If the match field that you add belongs to a field group that has fields set as uniqueness criteria, Business 360 Console recommends adding the uniqueness criteria fields as exact match fields. If you delete an exact match field that triggered the recommendations, Business 360 Console recommends deleting previously recommended fields from the exact match fields list. If you delete a uniqueness criteria field of a field group, Business 360 Console might recommend deleting the previously recommended fields from the exact match fields list.
For example, the Address field group contains Address Line 1, Postal Code, and Country Code fields, and the Postal Code and Country Code fields are configured as uniqueness criteria. If you add the Address Line 1 field as a match field, Business 360 Console recommends adding the Postal Code and Country Code fields as exact match fields.
If you delete the Address Line 1 field from the declarative rule, Business 360 Console recommends deleting the Postal Code and Country Code fields from the exact match fields list.
1Click the Add Exact Match Field icon.
A row is added to the Exact Match Fields table with the Comparison Outcome value set to Identical.
Note: In the current release, Identical is the only comparison outcome that is available for exact match fields.
2Select a business entity field for matching identical data.
The field appears in the Exact Match Fields table. If the field belongs to a field group that has fields set as uniqueness criteria, recommendations to add the uniqueness criteria fields as exact match fields appear.
3If you want to add the recommended fields as exact match fields, click the recommended fields.
The fields appear in the Exact Match Fields table.
4To delete an exact match field, hover over a row and click Delete.
If you delete an exact match field that triggered the recommendations, a recommendation to delete the associated exact match fields appears.
5To add more exact match fields, repeat steps 1 through 2.
6If you set the declarative rule to perform exact matching, click Next.
The Configure Exact Match Field Properties page appears.
7If you set the declarative rule to perform fuzzy matching, perform the following steps:
aIn the Fuzzy Match - Required Fields table, select a field name for each field type for matching similar data.
The field appears in the Fuzzy Match - Required Fields table. If the field belongs to a field group that has fields set as uniqueness criteria, recommendations to add the uniqueness criteria fields as exact match fields appear.
bIf you want to add the recommended fields as exact match fields, click the recommended fields.
The fields appear in the Exact Match Fields section.
cIn the Fuzzy Match - Additional Required Fields table rows, click the Add Additional Required Field icon to add at least one of the additional required fields.
The additional required fields appear based on the match criteria that you select.
dSelect a field for the corresponding additional required field.
A row is added to the Fuzzy Match - Additional Required Fields table with the Comparison Outcome value set to Identical. If the field belongs to a field group that has fields set as uniqueness criteria, recommendations to add the uniqueness criteria fields as exact match fields appear.
Note: In the current release, Identical is the only comparison outcome that is available for fuzzy match fields.
eClick the recommended fields if you want to add them as exact match fields.
The fields appear in the Exact Match Fields table.
fTo delete an additional required field, hover over a row and click Delete.
If you delete an additional required field that triggered the recommendations, a recommendation to delete the associated exact match fields appears.
gClick Next.
The Add Optional Fields page appears.
Step 3. Add optional fields
If you set the declarative rule to perform fuzzy matching, you can add optional fields and configure comparison outcome for them.
1Click the Add Optional Field icon and select an optional field type.
The field types appear based on the match criteria that you select.
2Select a business entity field for the selected field type.
The field appears in the Fuzzy Match - Optional Fields table. If the field belongs to a field group that has fields set as uniqueness criteria, recommendations to add the uniqueness criteria fields as exact match fields appear.
3Click the recommended fields if you want to add them as exact match fields.
The fields appear in the Exact Match Fields table of the Add Required Fields tab.
4To delete an exact match field, hover over a row and click Delete.
If you delete an optional field that triggered the recommendations, a recommendation to delete the associated exact match fields appears.
5To add more optional fields, repeat steps 1 through 2.
6Click Next.
The Configure Exact Match Field Properties page appears.
Step 4. Configure exact match field properties
You can configure the properties of exact match fields that you add to a declarative rule. You can enable segment matching or null matching on exact match fields.
1Select an exact match field for which you want to configure properties.
2To configure segment matching, perform the following steps:
aOn the <field name> Properties section, select Segment matching.
bTo match segment data with the rest of the data, select Match segment data with other data.
If you select Match segment data with other data, the rules also match the segment data with the rest of the data, but the records in the rest of the data don't match with each other. If you do not select Match segment data with other data, the rules use only the records in the subset of data for matching.
cEnter one or more segment values to identify segment data for matching.
3 To configure null matching, perform the following steps:
aOn the <field name> Properties section, select Null matching.
bSelect one of the following options:
▪ Null matches null. Matches two null values.
▪ Null matches non-null. Matches a null value with a value that is not null.
4Click Add.
The rule appears on the Declarative Rules page.
5Click Save.
Configure declarative rules with relationship match criteria
You can configure declarative rules with the relationship match criteria, and match records based on relationships.
For example, If you want to match records based on relationships, you can configure a declarative rule to match employees of the same organization with similar names and postal addresses.
When you configure declarative rules with relationship match criteria, consider the following guidelines:
•In addition to declarative rules with relationship match criteria, create declarative rules using other match criteria. A match model that has declarative rules only with relationship match criteria might result in overmatching.
•Ensure that you run the match and merge job on the target business entity before you run the match and merge job on the source business entity.
Note: The Search Match API ignores declarative rules with the relationship match criteria.
1On the Configure Properties and Thresholds tab, select Relationship as the match criteria.
The Relationship field appears.
2Click the relationship asset picker.
The Select an Asset dialog box appears.
3Select a relationship, and click Select.
4Configure the match level, description, match threshold, and click Next.
The Add Exact Fields page appears.
5Add the exact match fields, and click Next. To know more about adding an exact match field, see Step 2. Add required fields.
The Add Fuzzy Fields page appears.
Note: Add at least one exact or fuzzy match field to the declarative rule.
6Click the Add Fuzzy Match Field icon and select a field type.
A row is added to the Fuzzy Match Fields table with the Comparison Outcome value set to Identical.
7Select a field name for each field type for matching similar data.
The field appears in the Fuzzy Match Fields table.
8Click Next.
The Configure Exact Match Field Properties page appears.
9If you added exact match fields, configure the exact match field properties, and click Add. To know more about configuring exact match field properties, see Step 4. Configure exact match field properties