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.
Clear attribute option is only ignoring the value it is not deleting.
I would suggest you look to see if there is an existing Aha request and vote on it or create an Aha request if one is not already voted on.
If you go to the Sources view and delete an attribute there, you can see in the browsers developer mode that the API is a delete of the specific URI of the attribute. However, how this would work for 40M is not clear. You could bulk export the attribute and write a program to parse the extract for the URI and call the API. However, I suggest that you work through this with your CSM.
What you should NOT do is remove the attribute from your data model. The data will remain in the Reltio database: you will not have remove it, and it will continue to take up space. Absolutely don't do that!
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?
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 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.
Thanks Gina for sharing your input, it works.
Senior Solution Consultant
100 Marine Pkwy #275, Redwood City, CA 94065
+1 (855) 360-DATA+1 (855) 360-3282
© 2022 Reltio. All Rights Reserved
Site by eConverse MediaAlso of Interest: Master Data Management (MDM) Reltio Community Reltio Integration Hub Community, Data Management Community Matching, Merge, Survivorship Reltio Workflow Master Data Management (MDM)