Remove unwanted fields from filter

[ajdinnebier]

We are using the table cmdb_ci_netgear to manage our inventory of switches and routers.

However, cmdb_ci has TONS of pre-canned fields, which causes the filter for cmdb_ci_netgearto have a huge list of fields to choose from. This can make searching for equipment a chore (for example, we use a custom Model Number field, so the filter shows the pre-canned 'Model number', 'Model id' and my custom "Model Number")

What I would like to do is make the filter for cmdb_ci_netgear show only specific fields, (Serial Number, Model Number, IP address, etc) and leave out the 50 or so other fields that no one searches on. Is it possible to do this without moving the data to a new table that does not extend CMDB_CI?

Thanks!

[Joe_Employee]

What you could do is use either the Category or Department field off cmdb_ci table and note the fields you want. Then use a reference qualifier to limit that field. If you are already using all the fields in the cmdb_ci you could also simply add an additional field on the cmdb_ci table and then use that field to do the same idea around the reference qualifier.


http://wiki.service-now.com/index.php?title=Reference_Qualifiers

~Joe

[ajdinnebier]

If I understand you correctly, what you are describing is a way to limit the selections of a reference field.

What I want to do is limit the actual fields when shown in the filter. Only allow people to search on specific fields.

[Chuck Tomasi]

If it's a field that you're not using anywhere in the cmdb_ci hierarchy, you could go in to the dictionary entry and change "active=false" (uncheck Active). That would keep the field and any pre-existing values, but take it out of active service and the filter list.

Use this with caution. Making a field inactive will be a global setting for any tables that extend a base table. For example, if you turn off cmdb_ci.model_id, it won't be available to any other tables in the CMDB.

[CapaJC]

I know of only two good ways to prevent someone from filtering on a field.
1) remove their read access to the field via ACLs
2) personalize dictionary on the field and uncheck the "active" checkbox. That will prevent the field from showing up in any slushbucket, and prevent it from being added to forms or lists