Why are we see a relationship deleted and then re-created during the DnB match and enrichment?

Question

We are having this issue when the organization is enriched from DnB using the DnB API (https://361-dnbconnector.reltio.com/b2bIntegration/dnb/getDetailedProfile?plus=true&entityURI=); it deletes the existing DnBHierarchy relation and then same is later created by the custom recipe. We want to enrich the profile without removing the existing relation. Is there any option while calling the DnB integration getDetailedProfile API? 

{
"id": "00000-5m6RadJ",
"user": "dnb_connector",
"method": "DELETE",
"url": "/reltio/api/bn6cGVUthu9faUd/relations/2dgmPI3",
"clientType": "UNKNOWN",
"timestamp": 1725475396518,
"objectUri": "relations/2dgmPI3",
"objectType": "configuration/relationTypes/DnBHierarchy",
"startObjectUri": "entities/23giU0Z",
"startObjectLabel": "CABLE BAHAMAS LTDA",
"endObjectUri": "entities/2UM3aOD",
"endObjectLabel": "CABLE BAHAMAS LTD, (Client)",
"data": {
"type": "RELATIONSHIP_REMOVED",
"object": "{\"uri\":\"relations/2dgmPI3\",\"type\":\"configuration/relationTypes/DnBHierarchy\",\"createdBy\":\"prod.reltio.user\",\"createdTime\":1722864496783,\"updatedBy\":\"dnb_connector\",\"updatedTime\":1725475396518,\"startRefPinned\":false,\"startRefIgnored\":false,\"endRefPinned\":false,\"endRefIgnored\":false,\"attributes\":{},\"analyticsAttributes\":{},\"crosswalks\":[{\"uri\":\"EdMEJugl\",\"type\":\"DnB\",\"value\":\"P875039141$$875039141\",\"reltioLoadDate\":\"2024-08-05T13:28:16.783Z\",\"createDate\":\"2024-08-05T13:28:16.783Z\",\"updateDate\":\"2024-08-05T13:28:16.783Z\",\"attributes\":[],\"singleAttributeUpdateDates\":{}}],\"startObject\":{\"objectURI\":\"entities/23giU0Z\",\"crosswalks\":[{\"uri\":\"Cf71UMbj\",\"type\":\"DnB\",\"value\":\"P875039141\"}]},\"endObject\":{\"objectURI\":\"entities/2UM3aOD\",\"crosswalks\":[{\"uri\":\"C9Pgy6Tm\",\"type\":\"DnB\",\"value\":\"875039141\"}]}}"
},

Answer

• According to the documentation below, a DNB enrichment could remove a relationship if the DNB data does not include certain attributes mapped to the relationship in the Reltio system. For example, if the DNB data lacks attributes like isStandalone or operatingStatus, mapped to the OrganizationDetail section, the enrichment process might remove these attributes, affecting the relationship.

• Mapping contains the following definition.

"isStandalone": "[4].attributes.OrganizationDetail[0].value.Standalone[].value",
"controlOwnershipDate": "[4].attributes.OrganizationDetail[0].value.OwnershipDate[].value",
"controlOwnershipType": {
"description": "[4].attributes.OrganizationDetail[0].value.OwnershipType[].value"
},

• The isStandalone attribute in the DnB mapping indicates whether an organization operates independently without parent or subsidiary relationships.

"dunsControlStatus": {
"isMarketable": "[4].attributes.MarketabilityIndicator[].value",
"lastUpdateDate": "[4].attributes.DnBLastUpdateDate[].value",
"operatingStatus": {
"description": [
"[4].attributes.OrganizationDetail[0].value.OperatingStatusComment[].value",
"[4].attributes.OrganizationDetail[0].value.OperatingStatus[].value"
]
}
},

The DnB connector automatically creates DnB hierarchy relations during enrichment (using the 'get company details' button). The resolution to this issue is to modify the enrichment mapping and remove the corporateLinkage block from there. As a result, hierarchy relations will not be created (and existing ones will not be deleted), and organizations will not be loaded to the tenant.