Reltio Connect

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

There is also a Clear Attribute option, please try that.

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

Clear attribute option is only ignoring the value it is not deleting.

There is also a Clear Attribute option, please try that.

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

I have been thinking about this most of the day...

Why do you want to delete the attributes?  If the values are wrong, or they should not have come from the source, the data should be reloaded as if it was originally the new values in the source.  Doing that will automatically correct/overwrite the values as long as you do not use 'partialOverride' in the API call.

If it is just that they values should not be in the OV, then the 'ignore' should be good enough.  

Can you expand on the reason why they 'must' be deleted?

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

Hi Gina,

Yes, partialOverride is being used; however, we need to delete values because we will need to add new sub-attributes, and need to add new ones to keyAttributeURIs. Additionally, since three attributes are already included in this parameter, any newly loaded value will always be appended rather than override, and some sub-attributes need to have their values corrected.

I have been thinking about this most of the day...

Why do you want to delete the attributes?  If the values are wrong, or they should not have come from the source, the data should be reloaded as if it was originally the new values in the source.  Doing that will automatically correct/overwrite the values as long as you do not use 'partialOverride' in the API call.

If it is just that they values should not be in the OV, then the 'ignore' should be good enough.  

Can you expand on the reason why they 'must' be deleted?

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

I think you have missed my point:  If you do NOT use partial override, the attribute you want to remove will be removed.  When you update a crosswalk without partial override, the effect is to say that 'this is the new version'.  So if the attribute to be deleted is not in the payload, it will no longer be there.  Because you are using partialOverride, the attribute remains as part of the entity.

Hi Gina,

Yes, partialOverride is being used; however, we need to delete values because we will need to add new sub-attributes, and need to add new ones to keyAttributeURIs. Additionally, since three attributes are already included in this parameter, any newly loaded value will always be appended rather than override, and some sub-attributes need to have their values corrected.

I have been thinking about this most of the day...

Why do you want to delete the attributes?  If the values are wrong, or they should not have come from the source, the data should be reloaded as if it was originally the new values in the source.  Doing that will automatically correct/overwrite the values as long as you do not use 'partialOverride' in the API call.

If it is just that they values should not be in the OV, then the 'ignore' should be good enough.  

Can you expand on the reason why they 'must' be deleted?

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.

Thanks Gina for sharing your input, it works.

I think you have missed my point:  If you do NOT use partial override, the attribute you want to remove will be removed.  When you update a crosswalk without partial override, the effect is to say that 'this is the new version'.  So if the attribute to be deleted is not in the payload, it will no longer be there.  Because you are using partialOverride, the attribute remains as part of the entity.

Hi Gina,

Yes, partialOverride is being used; however, we need to delete values because we will need to add new sub-attributes, and need to add new ones to keyAttributeURIs. Additionally, since three attributes are already included in this parameter, any newly loaded value will always be appended rather than override, and some sub-attributes need to have their values corrected.

I have been thinking about this most of the day...

Why do you want to delete the attributes?  If the values are wrong, or they should not have come from the source, the data should be reloaded as if it was originally the new values in the source.  Doing that will automatically correct/overwrite the values as long as you do not use 'partialOverride' in the API call.

If it is just that they values should not be in the OV, then the 'ignore' should be good enough.  

Can you expand on the reason why they 'must' be deleted?

We have requirement to delete all values from a nested attribute and data volume for this is around 40M .We tried Bulk update UI feature but its only putting ignore button .Another option is Bulk_Update API but with this volume of data it is not feasible option as it requires entity URI.

Please suggest how we can delete this.

Thank in advance.