Invalid 'Table' selected on the SNMP OID Classification record - Scoping issue with SNMP OID records when updating the Table value - Dictionary is missing the allow_public=true for the Table fieldDescriptionIt may be necessary to customise SNMP OID records used by Discovery and Service Mapping to change the table the CI gets created in, or perhaps to use a custom Classifier instead.Some of these OID records are in different application scopes if they have been added by e.g. Discovery and Service Mapping Patterns app. A lot of CMDB table classes are also in scoped applications, or added by store apps. Some existing records already have incompatible scope compared to the table scope, which prevents them being updated at all. Others won't allow changing the Table value. The "Table" field of the SNMP OID Classification table [discovery_snmp_oid] does not have the allow_public=true attribute, and so the table field is currently only allowed to reference a CMDB table that is in the same scope as the OID record. This is specific to 'Table Name' type fields like this. Given there is a mixture of scopes used for OID records and CMDB Classes, this attribute needs adding to allow any combination of OID record scope and CMDB CI class scope. Note:If the records are in one of the other Classification tables, not discovery_snmp_oid, then the problem may instead be:KB1156526/PRB1595328 Invalid 'Table' selected on the xxx Classification record - Scoping issue when updating due to the Table value being in a different scope to the record - Dictionary is missing the allow_public=true for the Table fieldSteps to Reproduce Open an OID record which can be inconsistent for cross scoping rules.For example /discovery_snmp_oid.do?sys_id=570ed0e2db6c9780e5adff78bf9619f8 in the "Discovery and Service Mapping Patterns" scope, which references a table that is instead Global.Change the table or classifier values and Update.Observe the error Message: Invalid 'Table' selected on the SNMP OID Classification record. The 'xxx' table is in application 'xxx', but the current application is 'xxx'."e.g.Invalid 'Table' selected on the SNMP OID Classification record. The 'Communication Hardware' table is in application 'CMDB CI Class Models', but the current application is 'Global'."WorkaroundThis problem has been fixed in an upcoming release. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to. If an upgrade is not possible yet, contact Technical Support to add the missing attribute to the field on your affected instance as a Normal Change.Related Problem: PRB1475444