As Gino stated, when two records are created which do not merge, each receives a Reltio entity ID. If two records are created which trigger an on-the-fly merge then I believe the second crosswalks will just be added to the existing crosswalk without creating a new entity ID.
When a merge occurs on two existing entities, you can listen to the event queue where you will see an
ENTITY_LOST_MERGE event for the losing URI. If you are storing Reltio entityID in an external system, that loser URI will still be a valid identifier to get the consolidated record. See in the below GET that I use the legacy ID 0489VDg but that it returns uri 0489ZTw. Also note than when requesting an entity by a "lost" uri, it will return that in the payload as well in the property
"loserUri": "entities/0489VDg"
------------------------------
Dan Gage
Principal Solution Consultant
------------------------------
Original Message:
Sent: 11-08-2021 03:36
From: Ashish Rawat
Subject: Optimal method to fetch loser/contributor URI
Hi Gino,
Here value in the crosswalk section would always be crosswalk ID in your case it was entity uri that could be because source system didn't had crosswalk ID of its own. Please correct me if I am missing something here.
------------------------------
Ashish Rawat
Fresh Gravity
Bangalore
Original Message:
Sent: 10-28-2021 21:04
From: Gino Fortunato
Subject: Optimal method to fetch loser/contributor URI
you can do that via the entities API to get the data by entity.
In the crosswalk section of the response is the looser URI. For example:
"crosswalks": [
{
"uri": "entities/MOYFmuN/crosswalks/11gtNqYsI",
"type": "configuration/sources/DT_B2B",
"value": "entities/Sjic0RL",
"reltioLoadDate": "2019-01-08T09:50:04.903Z",
"createDate": "2017-06-28T16:06:40.149Z",
"updateDate": "2017-06-28T16:06:40.149Z",
"crosswalkExternalInfo": {
"dtssInfo": {
"tenantId": "XXXXXXXXXX",
"operationId": "37424fde-4bea-4f1d-b671-4ff804a3d0df",
"matchReasons": [
"configuration/entityTypes/Organization/matchGroups/ExactMatchByEntityURIConf9or10"
],
"updatedBy": "dtss",
"updatedTime": 1498678288010,
"status": "IMPORTED_BY_ENTITY_CHANGED_EVENT"
}
},
here the 'type' is the source and the 'value' is the URI of the looser record
--
Original Message:
Sent: 10/28/2021 10:13:00 AM
From: Ashish Rawat
Subject: RE: Optimal method to fetch loser/contributor URI
Use case is quite simple given a crosswalk ID, User wants to identify the entity URI that crosswalk had before merge. Now the entity URI of loser crosswalk can be used for unmerge process, data reconciliation etc.
------------------------------
Ashish Rawat
Fresh Gravity
Bangalore
Original Message:
Sent: 10-27-2021 10:52
From: Gino Fortunato
Subject: Optimal method to fetch loser/contributor URI
can you please expand on the use case?
------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio
Original Message:
Sent: 10-26-2021 08:26
From: Ashish Rawat
Subject: Optimal method to fetch loser/contributor URI
Is there any optimal method to get loser/contributor URI using loser/contributor crosswalk instead of parsing crosswalk tree?
------------------------------
Ashish Rawat
Fresh Gravity
Bangalore
------------------------------