Issue in deleting field in CMDB descendant table.Description Issue with deleting a field from CMDB descendant table. Field not completely deleted.CauseHere we have dealt with 2 issues. The field not completely deleted.Traces of the field are still existing after the deletion of the field.ResolutionIssue 1: The field not completely deleted. As this is a CMDB descendent table, any field creation/deletion will be created/deleted from all its descendant tables. This query takes a while. Observed from the log that the transaction has been canceled by a user. Hence the field deletion was incomplete. 2019-03-05 19:02:01 (800) http-15 WARNING *** WARNING *** GlideRequestCancel: Request to cancel: #277036 /sys_dictionary.do 2019-03-05 19:02:01 (808) http-15 SYSTEM WARNING *** WARNING *** Transaction: Cancelling transaction #277036 /sys_dictionary.do (cancelled by user request): Thread Default-thread-3 (USER_NAME, AE624A49DB40FF003AF79E04DB9619D9), after 109996ms As the User: USER_NAME, has issued cancellation request, Transaction: Cancelling transaction #277036 /sys_dictionary.do (cancelled by user request): The delete was not complete. Issue 2: Traces of the field are still existing after the deletion of the field. Check for the field existence in the sys_db_object related tables. (sys_documentation, sys_storage_alias, sys_storage_table_alias, ) I found that the field artifacts are being left at sys_storage_alias. --> Hence deleted the traces from Stroage_alias table for this field. --> It allowed deletion of the field from UI. --> Need to clear the cache after the field is deleted. GlideTableManager.invalidateTable("sys_storge_alias");GlideCacheManager.flushTable("sys_storage_alias"); This should remove the traces of the field.