It goes without saying that if you have item A<\/strong> linked to item B<\/strong> and then delete item B<\/strong>, the link between A<\/strong> and B<\/strong> should disappear. In usual operations this is true and this is what Cradle will do.<\/p>\n However, it is possible to create a dangling cross reference when importing partial data from other projects or backups. Say for example you have exported all your Definition items<\/em> (one of which is item A<\/strong>) and separately all your cross references<\/em>.\u00a0 (including the one to item type Constraints<\/em> one of which is item B<\/strong>). Into a new project you import all the cross references and then the Definition item<\/em>s. You plan to create new constraints<\/em>. If one is not created called B<\/strong> there will be a dangling cross reference<\/em> in the new project.<\/p>\n Dangling cross references a<\/em>re just one of the\u00a0 anomalies that can be detected using the cross reference integrity checker<\/strong>. This is run from the Project ribbon<\/em>.<\/p>\n There are a number of tests which can be selected and these are shown below.<\/p>\n Once a problem has been identified, it can be fixed, deleted or exported for editing as appropriate. The availability of these will depend on both the problem and the current user’s privileges.<\/p>\n <\/p>\n Dangling xrefs can cause issues with performance when items have been deleted. If item A<\/strong> was linked to item B<\/strong>, then item B<\/strong> got deleted. There would be a dangling xref which isn’t linking any items, creating extra data. If another item B<\/strong> was then created. It would then be linked back with item A<\/strong>. Which could potentially cause problems?<\/p>\n For full information on the settings see the help on Cross Reference Integrity<\/a><\/p>\n Article Updated 04\/02\/2019 – Added performance section<\/p>\nFinding and Rectifying Cross Reference Problems.<\/h2>\n
Cross Reference Integrity Checker<\/h3>\n
![\"The](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2018\/01\/xref_integrity.png\")
\n\n
\n \nCheck<\/th>\n Description<\/th>\n<\/tr>\n<\/tbody>\n \n Dangling cross references<\/b><\/td>\n Detects cross references whose from or to item do not exist.<\/td>\n<\/tr>\n \n Duplicate cross references (A-B and B-A)<\/b><\/td>\n Cross references are considered to be duplicates if a cross reference exists from item A<\/samp> to item B<\/samp> and another exists from item B<\/samp> to item A<\/samp> and they both share the same link type.<\/td>\n<\/tr>\n \n Reversed hierarchical cross references<\/b><\/td>\n Detects cross references that are between items where the from <\/em>item has an identity that suggests it to be the child of the to <\/em>item.<\/td>\n<\/tr>\n \n Cross references to be reversed<\/b><\/td>\n Detects cross references that are invalid according to the current link rules but which, if reversed, become valid.<\/td>\n<\/tr>\n \n Cross references needing a new link type<\/b><\/td>\n Detects cross references that are invalid according to the current link rules but which become valid if their link type is changed and where there is only one link type that is valid for the cross reference.<\/td>\n<\/tr>\n \n Invalid cross references<\/b><\/td>\n Detects cross references that are invalid according to the current link rules.<\/td>\n<\/tr>\n \n Cross reference cardinality<\/b><\/td>\n Detects cross references whose cardinality does not match the current link rules.<\/td>\n<\/tr>\n \n All<\/b><\/td>\n Will perform all the above integrity checks.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Performance<\/h2>\n