The entity elements in the Trillium Quality for Dynamics web resource XML file identify the fields used for cleansing and matching that entity’s data, and define field mapping for each entity. For each entity, the file identifies:
-
Input fields, which map fields in the CRM entity to fields used by the cleanser service. For example:
<MapField TrilliumFieldName="trillium_salutation" CrmFieldName="salutation"/>During processing, the value in “salutation” will be written to “trillium_salutation” to be passed to the cleanser.
-
Output fields, which map fields returned from the cleanser service to fields in the CRM entity. For example:
<MapField TrilliumFieldName="DR_MRMRS" CrmFieldName="salutation"/>During processing, the value returned from the cleanser in “DR_MRMRS” will be written to the CRM field “salutation.”
-
Match fields, which map fields in the entity to fields used by the matching service. For example:
<MapField CrmFieldName="salutation" TrilliumFieldName="DR_MRMRS" />During processing, the value in “salutation” will be written to “DR_MRMRS” to be passed to the matcher.
The match fields section also includes a MatchField Value, which determines the type of match to be performed. For example:<MatchField Value="1" TrilliumFieldName="PR_NAME_FORM_01" />If the MatchField Value is set to 1, a consumer match is performed, which is based on personal name fields. If the MatchField Value is set to 2, a business match is performed, which is based on a business name.
-
Window keys, which identify the field(s) containing the window key(s) to be used in the match process. For example:
<WindowKey CrmFieldName="tss_windowkey" />During the cleansing process, the cleanser creates window keys composed of characters from elements in the cleansed data. Records with the same window key are sent to the matcher for comparison.
Additional sections define auto merge fields, duplicate popup fields, and other field mappings, as described in this chapter and other chapters in this manual.