If Serial Number is empty and name is same then why duplicates are getting created

[Riya25]

Hello Experts,

Recently we have a issue in which  duplicate CI's are getting created having the Serial Number Empty but Name is same.

As per the identification when Serial Number is empty it should have checked for the Name Identifier then why duplicates are being created instead of updating the same record?

Also,after discovering the duplicates Class is different than the class of existing CI and IP address is same also in the  Created By field name of user is occurring.

Please help!! 

Regards,

Riya

[Riya25]

Hello Ajim,

I have just observed that there are two identifiers CI identifier(Legacy)and cmdb Identfiers and thus checked which identifiers are we using by checking the Property "glide.discovery.use_cmdb_identifiers" and found that this property is not there and its clear we are using CI Identifiers.

Below I have attached the screenshot of the CI identifiers which are currently active for Hardware Table.

So what are your thoughts if we switch to CMDB Identifiers then this problem cab be solved or not.

Although we are having CMDB Identifiers also but since this property is not there so I  thing they are not working.

Please let me know how can we solve this.

Regards,

Riya

[Azim Kazi]

Hi Riya ,

yes,switch the identifiers due to conflict this problem might happen.

and one thing you directly applied on hardware table so my suggestion is create identifiers for individual class not directly on hardware because in hardware there are various kind of hardware such as computer,printers,routers they are having different unique attributes so it will be better if you create identifiers class wise

again if you are created an identifier which applicable for its child class as well then make sure whenever you will create identifier for child class tick for "Allow fallback to parent's rules" this option under identifier entries so that if your child identifier gets false then it goes for parent class's identifier.

Regards,

Ajim

[Riya25]

Hello Ajim, Thank you for the reply. So to conclude why duplicates are getting created is due to missing identifiers right and not because if manual import of CI's. And how can we delete the existing duplicate in the base class. There are many duplicates present. Regards, Riya

[Azim Kazi]

Hi Riya,

You can delete those records by writing background script.

I can provide you demo script you can customise it as per your requirement below is script for your reference

var duplicate = new GlideRecord('cmdb_ci_netgear'); 

duplicate.addQuery('install_status','=', '200');    

duplicate.deleteMultiple(); 

Regards,

Ajim

[Riya25]

Hello Ajim,

Can you please help which field we should consider other than serial number ,name to make a new Identifier rule especially for server table.

And also to delete the duplicates we should run the background script on individual table or base table (cmdb_ci) and whether deleting will automatically delete the their respective Relationships or not ?

Thank You in Advance.

Riya