Trillium Quality for Dynamics adds several fields to your contact, account, lead, customer address, and custom entities. After a record is cleansed and matched, Trillium Fields are populated, which contain metadata about the record. Examples of the metadata contained in Trillium fields include:
Extra information about the record’s addresses, such as latitude and longitude coordinates, if available (tss_latitude and tss_longitude).
The level at which an address matched a GAV (postal) table:
-
tss_postalmatchlevel
-
tss_postalmatchlevel_2
-
tss_postalmatchlevel_3
-
tss_postal_match_level_text
-
tss_postal_match_level_text_2
-
tss_postal_match_level_text_3
-
Information about the cleansing or matching process, such as success or failure of the process (tss_cleanseresponse, tss_matchresponse, tss_errormessage).
The date on which the record was last cleansed or matched (tss_last_cleanse_date and tss_last_match_date).
Constructed information, such as window keys (tss_windowkey).
For a complete list of all Trillium fields added to entities, see the file DeploymentConfiguration.xml, located in the Trillium Quality for Dynamics’ install_dir\Deployment directory.
Trillium Quality for Dynamics does not add Trillium fields to forms or views. If you would like to view the content of Trillium fields in your forms or views, add them through 365’s Customization options.