Why is data matching between DT and CT not being triggered in DTSS?

Problem

DTSS is not triggering data matching b/w DT and CT using the below ID type for HCP and HCO

HCO ID type :

"ACNE.REX.E0-Workplace key of Acne Health",
"ACNE.REX.E0-Workplace key of Acne Health"

HCP ID type :

"ACNE.REX.I0-Individual key of Acne Health",
"ACNE.REX.I0-Individual key of Acne Health"

Troubleshooting/Solution

• Has there been any changes made to match rules?
• If changes have been made to the match rules, then make sure that the match tables have been rebuilt.

POST https://<environment>.reltio.com/dtss/tasks/manual_match

Request body:

{
 "dataTenant": "<dataTenantId>",
 "customerTenant": "<customerTenantId>"
}

Response body:

"@type": "manual_match",
 "entitiesFilterInDtMetadata": {},
 "id": "9b695c75-3d56-498c-a9bf-d9141e1e2897",
 "createdBy": "gloria.faley@reltio.com",
 "updatedBy": "",
 "deletedBy": "",
 "createDate": "2020-12-15T16:30:39.254Z",
 "startDate": "2020-12-15T16:30:49.994Z",
 "endDate": "2020-12-16T00:06:25.817Z",
 "status": "FINISHED",
 "clusterNode": "ip-3-248-249-51",
 "startupType": "MANUAL",
 "type": "MATCH",
 "emails": [
 "gloria.faley@reltio.com"
        ],

• Verify if the two entities are able to match.

POST  https://<environment>.reltio.com/dtss/entities/_verifyMatches

--header 'DataTenant: <dataTenantID>' 
--header 'CustomerTenant: <customerTenantID>' 

Request body

{
"dtEntity": "entities/<entityId>",
"ctEntity": "entities/<entityId>"
}

The results show that a match by Identifiers.ID is set to true and Identifiers.Type is set to true.

"rule": {
 "and": [
                    {
 "equals": [
                            {
 "attribute": "Identifiers.Type",
 "first": true,
 "second": true,
....
 "exact": {
 "Identifiers.ID": {
 "match": true
                            }
                        }
                    }
                ]
            },

The foundInMatchTables appears to be returning false for the DT entity

 "first": {
 "foundInMatchTables": false,
 "tokens": [
 "waue00015028:waurexe0workplace key of ims health db2"
                    ]
                },
 "second": {
 "foundInMatchTables": true,
 "tokens": [
 "ancme00015028:ancme0workplace key of ims health db2"
                    ]
                },
 "intersection": {
 "tokens": [
 "ancme00015028:ancme0workplace key of ims health db2"
                    ]
                }

However, this is expected because the 'foundInMatchTables' shows that all the listed tokens exist in the match tables. The first entity 'entities/vVib6xL' belongs to the customer tenant, the second entity belongs to the data tenant 'entities/15uZOdiY'. 

The explanation of the matches is built with the data tenant context. That is why the foundInMatchTables=false for the first entity, its matching information does not exist in the data tenant tables. 

We recommend that you perform the following at the end of the troubleshooting and solution.

POST {DTSSURL}/tasks/manual_sync

Response body:

{
 "dataTenant": "<dataTenantID>",
 "customerTenant": "<customerTenantID>"
}

This will perform a full reupload of slices for subscribed CT entities and relations.