Reltio Connect

Hi Team,

1) Consider Matchfield uri is configured for an nested attributes (e.g., Identifier).

Merge if Exact on Type and value

Which value of Valid Till will be survived after Matching field?

2) Consider Override key uri is configured for an nested attributes (e.g., Identifier).

Override if Exact on Type and value

Which value of Valid Till will be survived in an initial data load?

And also please confirm is there any possibility of retaining the Oldest value of other non configured sub-attributes.

Hi Shweta,

For the first scenario, the surviving value of "Valid Till" would depend on the survivorship rule that you have configured for that sub-nested attribute.

For the second scenario, the value that's loaded last would be persisted.

Regarding the question, "please confirm is there any possibility of retaining the oldest value of other non configured sub-attributes", please confirm if its in context of scenario 1 or 2? If its scenario 1, then yes, it's possible by configuring the oldestValue survivorship rule for sub-nested attributes. If its scenario 2, then its not possible

Hi Team,

1) Consider Matchfield uri is configured for an nested attributes (e.g., Identifier).

Merge if Exact on Type and value

Which value of Valid Till will be survived after Matching field?

2) Consider Override key uri is configured for an nested attributes (e.g., Identifier).

Override if Exact on Type and value

Which value of Valid Till will be survived in an initial data load?

And also please confirm is there any possibility of retaining the Oldest value of other non configured sub-attributes.

Hi Snehil Kamal,

For the first scenario, Survivorship rules can be configured for Match rules. Here the scenario is for Match Field URI for same crosswalk. Is it possible to change/configure survivorship rule in Match field URI?

Hi Shweta,

For the first scenario, the surviving value of "Valid Till" would depend on the survivorship rule that you have configured for that sub-nested attribute.

For the second scenario, the value that's loaded last would be persisted.

Regarding the question, "please confirm is there any possibility of retaining the oldest value of other non configured sub-attributes", please confirm if its in context of scenario 1 or 2? If its scenario 1, then yes, it's possible by configuring the oldestValue survivorship rule for sub-nested attributes. If its scenario 2, then its not possible

Hi Team,

1) Consider Matchfield uri is configured for an nested attributes (e.g., Identifier).

Merge if Exact on Type and value

Which value of Valid Till will be survived after Matching field?

2) Consider Override key uri is configured for an nested attributes (e.g., Identifier).

Override if Exact on Type and value

Which value of Valid Till will be survived in an initial data load?

And also please confirm is there any possibility of retaining the Oldest value of other non configured sub-attributes.