Not able to make a field dependent on the Configuration Item's Class field (sys_class_name)Issue Making a field dependent on the Configuration Item's Class field does not work. The field will show the choice as "None" no matter what Configuration Item Class gets selected.CauseThe CMDB Class field (sys_class_name) is a special field type called 'System Class Name' that cannot be used as a dependent field. Class field is not standard Choice field and the normal procedure for Choice field won't work because this field is empty and is populated based on a script. This is due to the "unique qualities of the Class field in the CMDB, this field is locked down." The Class field is the mechanism that links the base CMDB table to its extended tables and it was determined that this field needs to be locked to prevent changing its' value. A modification to this value will lead to orphan records.ResolutionDue to this limitation to the Class field (sys_class_name) in relation to being a dependent field, the only option would be to create a new custom field , e.g 'u_cmdb_class' and have a Business Rule that will copy the value of the Class field (sys_class_name) values to the new custom field. After that, the new custom field could be used as the dependent field as required.Related LinksLinks to our documentation on setting Business Rule and a link to a Community Article where a script was used to filter out [cmdb_ci] records based on the Class field (sys_class_name).