Hierarchy tree mismatch (See the log for details) error

If a source and target response list have the same System of Record (SOR), all their children must also have the same SOR and same position in the hierarchy tree. If these do not meet, the Hierarchy tree mismatch (see the log for details) error appears. To resolve the error, you must manually resolve the mismatch before the Site Merge utility can continue.

To resolve the issue, do the following:

1. Open the the log (in Logs folder), find the lines starting with SiteMerge.Data.DedicateRepository.ResponseListRepository|[HierarchyIntegrityCheck].

   These carry the primary keys of error response lists in the source and target.

2. Use the key in the below script:

   ;WITH cte AS

   (

   SELECT *, 0 as TreeLevel

   FROM SAT_Response_Lists WITH (NOLOCK)

   WHERE ResponseList_PK = '<primary key>'

   UNION ALL

   SELECT a.*, TreeLevel + 1 as treelevel

   FROM SAT_Response_Lists a WITH (NOLOCK)

   INNER JOIN cte b on a.ResponseList_Owner_FK = b.ResponseList_PK

   )

   select * from cte

3. Run the script to get the hierarchy from source and target database.

   This tree needs to be inspected manually to find differences. The differences must be resolved before Site Merge utility can resume.

4. There are two approaches to resolve the differences:

   1. Remove different response lists from the source and target hierarchy (For example, make those root).

   2. Make the source response lists' Application Item ID the same as those in the target so that the source response list locates the same position as the one on the target tree.

5. Resume Site Merge utility.

   If the error is still seen, repeat the step until Import and Export button are enabled. Follow the steps in the "Response List" section to export and select appropriate resolutions.