Modifying the Web Resource XML File - trillium_quality - 2.7

Trillium Quality for Dynamics Installation and Developer Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Version
2.7
Language
English
Product name
Trillium Quality
Title
Trillium Quality for Dynamics Installation and Developer Guide
Topic type
Overview
Administration
Configuration
Installation
Reference
How Do I
First publish date
2008

The web resource XML file contains a sample custom entity node to assist you with configuring custom entities. Use this sample node to:

  • Map the name and address fields in your custom entity to Trillium fields.

  • Add the Match Display grid to your custom entity. The Match Display grid allows users to view and merge matching records. 

Note: The following procedure describes how to modify the options directly in the XML file. Use this procedure only if you do not have access to the Deployment Manager. To configure custom entities from the Deployment Manager, see Importing and Configuring Custom Entities.

To modify the Trillium Quality for Dynamics web resource XML file

  1. Open the web resource XML file.

    • If you have not yet deployed Trillium Quality for Dynamics, open WebResource.xml, found in the Trillium Quality for Dynamics \Deployment directory.

    • If you have already deployed Trillium Quality for Dynamics, log into CRM, click Settings > Customizations > Customize the System > Web Resources, double-click the resource TSS Web Resource, and in the Web Resource window’s Content group, next to the Type field, click Text Editor.

    Note: You may prefer to copy the XML content into Notepad or an XML editor to make the following edits. Be sure to copy the XML content back into the Dynamics Text Editor when edits are complete.
  2. Locate the sample custom entity node, loc_location, found near the bottom of the file. This sample illustrates configuration of an entity that contains location information.

  3. Uncomment the sample custom entity node and replace the sample entity name ”loc_location” with the name of your custom entity.

    Note: If you are configuring multiple custom entities, copy and paste the sample before making changes.
  4. Edit the Input fields, which map fields in your custom entity to fields used by the cleanser service. For example, the following element would cause the value in the CRM field “loc_country” to be written to “trillium_country” to be passed to the cleanser:

    <MapField CrmFieldName="loc_country" TrilliumFieldName="trillium_country"/>

  5. Edit the Output fields, which map fields returned from the cleanser service to fields in the CRM entity. For example, the following element would cause the value returned from the cleanser in “DR_CITY_NAME” to be written to the CRM field “loc_city”:

    <MapField CrmFieldName="loc_city" TrilliumFieldName="DR_CITY_NAME" />

  6. Edit the Match fields, which map fields in your custom entity to fields used by the matcher service. For example, the following element would cause the value in the CRM field “loc_postcode” to be written to “DR_POSTAL_CODE” to be passed to the matcher:

    <MapField CrmFieldName="loc_postcode" TrilliumFieldName="DR_POSTAL_CODE" />

    Note: Leave the AutoMerge section uncommented. Custom entities cannot be auto merged, but the section must be included in the custom entity.
  7. Copy the <MatchDisplay> node from the account, contact, or lead node. The MatchDisplay node displays as follows, depending on the entity type.

    For the account node:

    <MatchDisplay>
        <DisplayField FieldName="tss_name" LookupName="name"/
        <DisplayField FieldName="tss_filter1" LookupName="address1_composite"/>
        <DisplayField FieldName="tss_filter2" LookupName="address1_country"/>
    </MatchDisplay>

    For contact and lead nodes:

    <MatchDisplay>
    <DisplayField FieldName="tss_name" LookupName="fullname"/>
    <DisplayField FieldName="tss_filter1" LookupName="firstname"/>
    <DisplayField FieldName="tss_filter2" LookupName="lastname"/>
    <DisplayField FieldName="tss_filter3" LookupName="address1_composite">
    <DisplayField FieldName="tss_filter4" LookupName="address1_country"/>
    </MatchDisplay>
  8. In the <MatchDisplay> node, enter Lookup Names that are specific to your custom entity. These are the columns that will be displayed in the match display window. Do not change the FieldName=”tss_name” but you can change its lookup field. For more information on the MatchDisplay node, see Changing TSS Match Display List Fields.

  9. If configuring multiple custom entities, modify an additional custom node for each custom entity.

  10. Save and close the WebResource.xml file.

  11. If you have already deployed, in Dynamics 365 navigate to Settings > Customizations > Customize the System and click Publish All Customizations.