Reltio Connect

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?

Hi Chetan,

Please try switching to partial override for nested attributes, and do not pass the address reference attribute in the payload unless address is updated

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?

Hello, Need a small clarification.

Do you mean - Do the Dataload with Partial Update with Partial Override for nested attributes option @Snehil Kamal ? 

Hi Chetan,

Please try switching to partial override for nested attributes, and do not pass the address reference attribute in the payload unless address is updated

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?

That's right Chetan

------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore

Original Message:
Sent: 02-12-2026 01:52
From: Chetan P
Subject: Optimised way to Update Nested Attribute

Hello, Need a small clarification.

Do you mean - Do the Dataload with Partial Update with Partial Override for nested attributes option @Snehil Kamal ? 

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai

Original Message:
Sent: 02-12-2026 01:43
From: Snehil Kamal
Subject: Optimised way to Update Nested Attribute

Hi Chetan,

Please try switching to partial override for nested attributes, and do not pass the address reference attribute in the payload unless address is updated

------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore

Original Message:
Sent: 02-11-2026 23:30
From: Chetan P
Subject: Optimised way to Update Nested Attribute

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?

------------------------------
Chetan
------------------------------

In That case @Snehil Kamal , For below example using partial update with partialoverride for nestedattributes - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address

Today, again same record comes in with 3 emails, 1 phone number + Address 

Question - Does it remove that 1 email, 4 phone numbers that were not present in today's file when i load it with the above-mentioned property?

------------------------------
Chetan 

Original Message:
Sent: 02-12-2026 02:10
From: Snehil Kamal
Subject: Optimised way to Update Nested Attribute

That's right Chetan

------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore

Original Message:
Sent: 02-12-2026 01:52
From: Chetan P
Subject: Optimised way to Update Nested Attribute

Hello, Need a small clarification.

Do you mean - Do the Dataload with Partial Update with Partial Override for nested attributes option @Snehil Kamal ? 

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai

Original Message:
Sent: 02-12-2026 01:43
From: Snehil Kamal
Subject: Optimised way to Update Nested Attribute

Hi Chetan,

Please try switching to partial override for nested attributes, and do not pass the address reference attribute in the payload unless address is updated

------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore

Original Message:
Sent: 02-11-2026 23:30
From: Chetan P
Subject: Optimised way to Update Nested Attribute

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?

------------------------------
Chetan
------------------------------

Hi Team,

Posting this message to know the optimised approach to perform operation on Nested attributes.

I have an entity where we load the data through dataloader which has "Entity + Address" Information and the Refentity value is "SURROGATE". In the file i have 8 nested attributes such as (Email, Phone, Url, etc.,). For me to load a record and have all the nested attributes updating i am using Full Update which in turn every time is deleting and creating relationships again for Address entity.

For me to switch from Full Update to Partial Update, i am thinking of a solution that takes care of Nested attribute handling so that the no.of eevnts which is getting triggered to Address entity will get reduced.

 Example - 

Yesterday a record had full information of a person with 4 emails, 5 phones + Address = Full Update -> All information is flown + Multiple events are triggered to Address entity such as Relationship Created and Updated even though there is not change in Address

Today, again same record comes in with 3 emails, 1 phone number + Address (No Update) -> All the nested attributes are updated by removing un-necessary ones + Multiple events are triggered to Address entity such as Relationship Created and Updated eventhough there is not change in Address

Need - If i have a way to handle the nested attributes updates -> i can switch to Partial Update and decrease no.of events that are getting triggered

Any thoughts Experts?