The DEFAULT_RULE_MAX_COLUMN_VALUES rule selects the row that contains the highest value in the specified columns as the preferred record. To identify a preferred column value, the DEFAULT_RULE_MAX_COLUMN_VALUES rule selects the corresponding column value in the preferred record as the preferred column value.
You must configure weight for each column that you specify. The consolidation process uses the descending order of the column weights to determine the order of the execution of the columns. The DEFAULT_RULE_MAX_COLUMN_VALUES rule uses case-insensitive lexicographical ordering to find the highest value.
For example, set the weight for the EmployeeID column to 5 and weight for the City column to 2.
The following table displays a sample cluster and indicates the preferred record for the cluster based on the DEFAULT_RULE_MAX_COLUMN_VALUES rule:
||Row-level preferred record
||John Jr Smith
The DEFAULT_RULE_MAX_COLUMN_VALUES rule uses the EmployeeID column first because the EmployeeID column has the highest weight. The rule selects the second row as the preferred record because it contains the highest employee ID.
Use the following format to configure a DEFAULT_RULE_MAX_COLUMN_VALUES rule:
<DefaultRule name="<Rule name>" rule="DEFAULT_RULE_MAX_COLUMN_VALUES" order="<Execution order>">
<Value columnValue="<Column name 1>" weight="<Weight 1>" />
<Value columnValue="<Column name 2>" weight="<Weight 2>" />
<Value columnValue="<Column name N>" weight="<Weight N>" />
The format uses the following parameters:
- Rule name
- Unique name for the rule.
- Execution order
- Optional. Order of execution for the rule. Use an integer value for the order of execution. If you do not specify the execution order, the consolidation process runs the rule based on the sequence of rules listed in the consolidation rules file. If you specify the execution order for a rule, you must specify the execution order for other rules.
- Column name 1, 2,...N
- Name of the columns based on which you want to configure the rule.
- Weight 1, 2,...N
- Weight for the corresponding column. The descending order of the column weights determines the order of execution of the columns.
The following sample DEFAULT_RULE_MAX_COLUMN_VALUES rule is configured for the EmployeeID and City columns:
<DefaultRule name="defaultRule2" rule="DEFAULT_RULE_MAX_COLUMN_VALUES" order="1">
<Value columnValue="EmployeeID" weight="5" />
<Value columnValue="City" weight="2" />