Reltio Connect

Hi All,

Am looking for best practices to follow when maintaining source specific audit attributes like source created date, updated date against Reltio's create data, update date and Reltio load date attributes at entity level as well as relationship levels. 

If we were to use source audit details for recency survivorship strategy and for any other custom requirements, what would be the best way to maintain the audit information from source systems in Reltio, either map it to Reltio audit attributes directly or maintain them separately. If we have to maintain them separately will there be any implications.
Appreciate your inputs. 

Hi Vinoth, 

Add your source specific create date and update dates under the crosswalk Create Date and Update Date as shown here. 

"crosswalks": [            {                "type": "Salesforce",                "value": "Org_123456789",                "createDate": "2025-07-22T17:48:36.866Z",                "updateDate": "2025-09-05T11:48:36.866Z"            }        ]

We always recommend following this approach as if you don't provide the source specific create date and update date under crosswalk, Reltio will map system timestamp to it. 

Reltio automatically maintains a reltioLoadDate attribute at the crosswalk level which is not editable and a record level createdTime and updatedTime  as well. Refer to the following Create Entity response for reference. 

[    {        "index": 0,        "object": {            "uri": "entities/16xLU7P",            "type": "configuration/entityTypes/Organization",            "createdBy": "diparnab.dey@reltio.com",            "createdTime": 1761832165477,            "updatedBy": "diparnab.dey@reltio.com",            "updatedTime": 1761832165477,            "attributes": {                "AutoGeneratorID": [                    {                        "type": "configuration/entityTypes/Organization/attributes/AutoGeneratorID",                        "ov": true,                        "value": "UUID_9f1256d6-2217-442e-9256-d62217842ed4",                        "uri": "entities/16xLU7P/attributes/AutoGeneratorID/6ljMjP1H"                    }                ],                "Name": [                    {                        "type": "configuration/entityTypes/Organization/attributes/Name",                        "ov": true,                        "value": "ABC Corporation",                        "uri": "entities/16xLU7P/attributes/Name/6ljMjCEV"                    }                ]            },            "isFavorite": false,            "crosswalks": [                {                    "uri": "entities/16xLU7P/crosswalks/6ljMjGUl",                    "type": "configuration/sources/Salesforce",                    "value": "Org_123456712",                    "reltioLoadDate": "2025-10-30T13:49:25.477Z",                    "createDate": "2024-07-22T17:48:36.866Z",                    "updateDate": "2024-09-05T11:48:36.866Z",                    "attributes": [                        "entities/16xLU7P/attributes/Name/6ljMjCEV",                        "entities/16xLU7P/attributes/AutoGeneratorID/6ljMjP1H"                    ],                    "singleAttributeUpdateDates": {}                }            ],            "analyticsAttributes": {},            "label": "ABC Corporation",            "secondaryLabel": ""        },        "successful": true    }]

These dates I mentioned above are automatically populated by Reltio based on when the records are actually being created or updated. So, you can't map your source dates to these attributes. 

And the recency i.e. LUD survivorship considers the latest date from 3 date fields - Crosswalk Level UpdateDate,  SingleAttributeUpdateDate (if available), SourcePublishDate (if provided). You can refer to this document for more clarity - https://docs.reltio.com/en/objectives/resolve-potential-matches/potential-matching-at-a-glance/potential-matching-navigation/design-survivorship-rules/survivorship-rules. 

Hi All,

Am looking for best practices to follow when maintaining source specific audit attributes like source created date, updated date against Reltio's create data, update date and Reltio load date attributes at entity level as well as relationship levels. 

If we were to use source audit details for recency survivorship strategy and for any other custom requirements, what would be the best way to maintain the audit information from source systems in Reltio, either map it to Reltio audit attributes directly or maintain them separately. If we have to maintain them separately will there be any implications.
Appreciate your inputs.