TIBCO MDM Customization Guide - TIBCO Product Documentation

Record Duplicate Detection Process| 207While specifying index entity attributes in the rulebase:• Ensure that the number of attributes specified in MatchAttributeArray andIndexEntityAttributes must match, else the IndexEntityAttributes areignored.• Specify the IndexEntity name followed by the attribute name. Entity namespecified for a target repository is the target repository name specified in theIndexerConfig.xml file.• Specify the MatchingAttributes and IndexEntityAttributes in thehierarchy level because the MatchRecord activity uses theMatchAttributesArray and IndexEntityAttributes in the exact specifiedorder. For example, if CustomerStaging:FIRSTNAME is the first attributespecified under MatchAttributesArray, and CustomerReferenceEntity:FNAME isthe first attribute specified under IndexEntityAttributes, the MatchRecordactivity accesses the FIRSTNAME attribute’s value (For example, JOHN) fromthe CustomerStaging record and uses this value to query theCustomerReference index entity using the FName attribute.Specifying Non-matching AttributesIf you want to display non-matching attributes of two different repositories in thework item, specify those in the catalogvalidation.xml file of the sourcerepsitory. The file is located in the $MQ_COMMON_DIR//catalog/master/ directory.For example,AttributeRRMMappingAttributesmatch attribute List RRMMappingAttributes.Each attribute must be qualified by EntityName.RRMMappingAttributesCustomerStaging:CITY=CustomerReference:BANKNAMEThe Array name must be RRMMappingAttributes.TIBCO MDM Customization Guide