Rule entry errors for cmdb_ci_power_eq/cmdb_ci_appl/cmdb_ci_network_function_instance after upgrading CMDB CI Class Models appDescriptionThe CMDB CI Class Models app added related entries to the identifiers for cmdb_ci_power_eq/cmdb_ci_appl/cmdb_ci_network_function_instance that references the table tni_entity, which will be missing if you don't have the Network Inventory Core app installed. Errors seen: Note: if the errors are not exactly these 3 specific ones, then your problem is not this one.Steps to Reproduce On an instance with 'CMDB CI Class Models' 1.77.1' or later, but WITHOUT 'Network Inventory Core' installed.Open any pages related to CI identifiers, that would cause the "Rule validation on Identifier ..." business rules to run.e.g. https://<InstanceURL>/cmdb_identifier_list.do Expected behaviour: Dependencies and Conditional content in apps should be set up correctly to ensure Identifiers are not added without the tables they depend on. Actual behaviour: The tni_entity table does not exist, which is used in Related Entries of these identification rules. This can be confirmed if you see "label [tni_entity]" in the Related Table column of this list. "label" is the clue that a table doesn't exist.https://<instance_name>.service-now.com/cmdb_related_entry_list.do?sysparm_query=table%3Dtni_entity End-Users of the instance will see the following 3 big red error banners along the top of many pages:Error MessageRule entry under cmdb_ci_power_eq identifier using non-existent table is ignored during identification!Error MessageRule entry under cmdb_ci_appl identifier using non-existent table is ignored during identification!Error MessageRule entry under cmdb_ci_network_function_instance identifier using non-existent table is ignored during identification!WorkaroundThis problem has been fixed. The issue has been addressed in CMDB CI Class Model 1.78.0 and later. You can upgrade this in your instance from:https://<instance_name>.service-now.com/now/app-manager/home/app/id/ae99d84b2320330006c0110d96bf65b3/ However that only fixes it for customers who hadn't upgraded to the bad version yet. The bad records will need to be manually deleted. The records to delete will be listed with "label [tni_entity]" in the Related Table column of this list. "label" is the clue that a table doesn't exist.https://<instance_name>.service-now.com/cmdb_related_entry_list.do?sysparm_query=table%3Dtni_entityRelated Problem: PRB1925042