Correction of modified reference field types in TPP table hierrarchyIssue In some instances, we may see an error where a field in a table which is part of a table hierarchy (e.g cmdb_ci_disk) is of some other value instead of reference even though it has been inherited from the parent table. It is also inactive. We will also likely to see the below error message : "This cloned descendant element is read-only, Click here to open editable first element (xxxxxx.xxx) in a new window". Steps to reproduce this issue : Log in to the instance and traverse to sys_db_object.LIST to find the hierarchy for tables.For instance, if you take cmdb_ci_disk (Disk) table, you can see it's hierrarchy as CMDB -> cmdb_ci -> cmdb_ci_storage_device -> cmdb_ci_disk -> cmdb_ci_storage_disk(descendant). To check the hierrarchy please check the "extends" field value in each of the records in sys_db_object.Ensure that the field computer is of type reference.Open the sys_dictionary entry for the field computer for cmdb_ci_disk table and manually update type to char(if you are not having access to modify you can achieve this by manually running an update query through the backend for testing).Once the dictionary entry is modified, you can see that it is inactive, and will show the error message: "This cloned descendant element is read-only, Click here to open editable first element (cmdb_ci_storage_device.computer) in a new window".Open the dictionary entry for computer in cmdb_ci_storage_device(ancestor) and select reference type from the searcher again, and save the record.Open the dictionary entry for field computer for cmdb_ci_disk. You will find the field is active now, and type set to reference.CauseThese may have been caused by manual modification by the user having admin privileges, some background script or from some update sets. This can be determined by looking at the audit history of the record.Resolution Modifications to the base dictionary entry are automatically propagated to all cloned dictionary entries for that field. To resolve this issue, in the parent instance for the same field(we can see the parent instance from the above error message), we have to select the same field to reference again from the searcher and save the records again. We would find that the change has propagated to the target table and the field value changes to reference and active is set as true. Related LinksThe above error message is a feature of TPP extension model inherited fields, where fields are physically duplicated to child tables meaning that: A single field can have multiple dictionary entries (i.e. multiple records in the sys_dictionary table) -> The single 'base' record (i.e. the sys_dictionary record corresponding to the table against which the field was initially created). One additional cloned record corresponding to every child table which extends the fields 'base' table. Only the base dictionary entry can be modified.