Migrating From Version 2.2 or later to Version 2.7 - trillium_quality - 2.7

Trillium Quality for Dynamics Installation and Developer Guide

Product type
Product family
Trillium > Trillium Quality
Product name
Trillium Quality
Trillium Quality for Dynamics Installation and Developer Guide
Topic type
How Do I
First publish date

When migrating from version 2.2 or later to version 2.7 of Trillium Quality for Dynamics, you can retain your match links; re-cleansing and re-matching records will not be required.

The Deployment Manager is specific to the version of Trillium Quality for Dynamics with which it was installed. To migrate, you must use the Deployment Manager installed with version 2.2 or later to remove components, then you will use the Deployment Manager installed with version 2.7 to deploy version 2.7.

Note: Backing up your database before migrating is a recommended best practice.

To migrate from Version 2.2 or later to Version 2.7 of Trillium Quality for Dynamics

  1. Log on to Dynamics 365 as a user with administrator privileges.

  2. Open the Trillium Quality for Dynamics solution:

    • If you used a separate solution for customizations, select Settings > Solutions and open the solution.

    • If you did not use a separate solution for customizations, select Settings > Customizations > Customize the System.

  3. If you have modified the web resource XML file and want to retain those modifications, copy the customized file by doing one of the following:

    • Select Web Resources, clicking TSS Web Resource, and clicking Text Editor. Copy the web resource content and paste it into a new file. You will use this new file to recreate your modifications in the new version. Close the text editor and Web Resource window, keeping the Solution window open.

    • In the Deployment Manager, on the Utilities tab click Backup to Disk. The backup file is named Backup.WebResource.Xml and added to the ...\TSCrmMSD\Deployment directory. If a backup copy already exists, it will be overwritten.

  4. Use the Solution window to remove solution libraries and other dependencies from all entities, forms, and views.

    For example, if Trillium Quality for Dynamics libraries have been added to the main form for the Contact entity:

    1. Select Entities > Contact > Forms and open the main form.

    2. Click Form Properties.

    3. Remove the tss_duplicatepopup_loader and tss_jquery_sdk_rest libraries and click OK. Removing the libraries will automatically remove all linkages.

    4. Click Save and Publish to save your changes, and close the form window.

    5. Repeat Step a through Step d for each entity and form modified for the previous version of Trillium Quality for Dynamics (v2.2 or later), including contact, account, lead, customer address, and custom entities. If you are using a different solution to manage customizations, additional dependencies may exist.

      Note: When modifying the TSS Match Display entity, in addition to removing the libraries be sure to remove the display setting. On the entity’s General tab, under Areas that display this entity, uncheck any selected options. If you have added any other Trillium entities to a display, remove those settings also.
    6. Click Publish All Customizations and close the Solution window.

  5. On the machine from which you deployed Trillium Quality for Dynamics version 2.2 or later, from the Start menu select Trillium Software > Trillium Quality for Dynamics n.n.n. Right-click Deployment Manager and select Run as administrator. The Deployment Manager window opens.

  6. Click the Removal Steps tab. Click Save to save your settings if prompted.

    Displaying Removal Steps
  7. Click Remove Plugin. This removes dependencies between Trillium Quality for Dynamics solutions, which allows them to be deleted. The output window displays progress messages. Click OK to dismiss the Completed message.

  8. Return to the Dynamics 365 window, select Settings > Solutions, select the Trillium_for_MSD solution, click Delete and click OK to confirm the deletion. (Do not delete the Trillium_MatchLink_For_MSD solution; this will remove all matching information from the system.)

    Note: If you have not deleted all Trillium libraries from forms and views, a Cannot Delete Component message displays. If details are available from CRM, click Details to see a list of the items that must be deleted prior to uninstalling. Click the form name in the message to display the form that has a dependency.

    It is also useful to go to Settings > Customizations > Customize the System > entityName > Fields, select the field, and from the More Actions menu select Show Dependencies.

  9. After deleting the solution, click Publish All Customizations.

  10. On the Deployment Manager window’s Removal Steps tab, click Remove Reports and click Yes to confirm the deletion. This deletes the reports added during deployment.

  11. Click Remove TrilliumRoles and click Yes to confirm the deletion.
    Note: To retain cleansing information and fields used for matching in your records, DO NOT click Remove Trillium Fields. If you want to delete Trillium fields, first remove them from all forms and views, then click Remove Trillium Fields. When you install the new version of Trillium Quality for Dynamics, you will have to re-cleanse and re-match your data.
  12. Select File > Exit to close the Deployment Manager.

  13. Ensure that DeploymentConfiguration.xml is removed from the ...\Deployment folder.

  14. Follow the installation steps beginning in Installing Trillium Quality for Dynamics to install and deploy the new version of Trillium Quality for Dynamics.

  15. After you have completed installation and deployment of the new version of Trillium Quality for Dynamics, compare the saved copy of your modified web resource XML file with the new web resource file and recreate your modifications. Do not use your old file to overwrite the file installed with the new version of the Trillium Quality for Dynamics.

    Note: You can automatically save a backup copy of the web resource XML.
  16. If you have created a solution for Trillium Quality for Dynamics customizations, as described in Creating a Solution for Trillium Quality for Dynamics Customizations, use that solution to migrate your customizations.