Purposes/Uses Of Table "Key Values" [cmdb_key_value]?

[Tom Rausch]

What are the purposes and/or uses of the table "Key Values" [cmdb_key_value]?

Am I free to add ad-hoc entries in this table?

[Jitendra Diwak1 · Accepted solution]

Hi @Tom Rausch,

Below are some suggestions for Key Values (cmdb_key_value) table in ServiceNow:

1. Use a naming convention for your key-value pairs. This will help you to identify and track the different key-value pairs in your environment. For example, you could use a naming convention that includes the name of the source that created the key-value pair, the type of key-value pair, and the date the key-value pair was created.
2. Set a default value for the updated field. This will ensure that the updated field is always updated, even if the incoming value does not change. For example, you could set the default value to the current date and time.
3. Create a script that runs on a regular basis to check the validity of the key-value pairs in the table. This script could check for the following:
   1. Whether the key-value pair still exists in the source system.
   2. Whether the value of the key-value pair has changed since it was last updated.
   3. Whether the key-value pair is still relevant to the configuration item.
4. Use a custom discovery rule to filter out invalid key-value pairs. This rule could check the validity of the key-value pair in the separate table and only create a record in the cmdb_key_value table if the pair is valid. This would prevent invalid key-value pairs from being created in the cmdb_key_value table in the first place.

Please accept my resolution if it works for you and humps up.

Thanks

Jitendra