|TS1042: Deleting an Icon Can Result in Reported Collection Damage|
Throwing away a field or abacus that is no longer used can result in Update Collection reporting that the collection is damaged. (Diagnostic Code: 30/xxxx/xxxxxxxx)
This is a known bug from older versions of Helix. What has happened is this: at one time the "bad" icon was referenced by another icon (probably an abacus) but that reference was no longer needed, so the collection designer removed it. When this was done Helix failed to update an internal usage table, called a backlink table. Because the table was not updated properly, the referencing icon continues to believe that the unlinked icon is still needed. When you subsequently throw away the unused icon, the referencing icon’s backlink table is not updated. When Update Collection sees this situation, it marks this as a problem that is "not corrected" and flags it with error code 302.
It is important to understand that throwing away the unused icon does not damage the collection. The damage already exists; throwing the icon away is what reveals it.
There are a number of options:
January 2012 Update: Helix RADE 6.2b8 (5767) addresses this bug by rebuilding all of the backlink (and related SUL) tables when a collection is opened. It is our recommendation that all collections be updated to Helix 6.x and opened with RADE 6.2b8 or later in order to correct any instances of this that may exist in your collection.
This bug has been reproduced in our test lab. The bug does not appear in current versions of Helix, but we are working on a way to "scour" existing databases looking for (and repairing) this type of damage. Until that solution is found, use one of the workarounds described above to repair collections that have this problem.
This bug existed in versions of Helix Express prior to our company's acquisition of Helix. Damage caused by this bug will continue to surface in current versions of Helix when previously created icons are discarded, until the collections are opened (and saved) in Helix RADE 6.2b8 or later.
This bug affects Helix RADE 6.2b7 and earlier, extending back to the Double Helix days.