Case sensitivity in Name, Serial Number, etc

[robin850]

Having 2 records in my CMDB with identical names, other than one is UPPERCASE and one is lowercase, is not fun.

How did these get here and what can be done to prevent this?

We don't import this data nor do we manually enter it. It all comes in from the midserver or from the snc_discovery.js script.

What is the trick?


cheers,

robin850

[robin850]

i logged a ticket with Support on this.

[Jay_Ford]

If you go to 'Discovery Definition->Properties' there is an option in there to translate all hostnames to lower case, upper case, or no change. What is your's set to? Image attached.

[aleck_lin]

Robin,

Currently the property of hostname case isn't applied to the wmi script (snc_discovery.js). I will put it in the product soon when I get chance to make it more consistent. Feel free to log an incident too.

Now, it's hard to answer the question how you end up having two CIs (one from Discovery and one from wmi script) without looking at the actual data. Maybe the identifiers from Discovery wasn't able to figure out that there was a already copy in the CMDB and then created a duplicate.

Lastly, the case of name shouldn't affect the name matching algorithm we have out of the box. We actually do a case-less matching.

[michaelmassey]

Is there a way to always force Lower Case on a Dictionary Entry (a string column on cmdb_ci) when that column is populated with an insert or update?

Thanks,
Michael