How does discovery model verify if its a duplicate before creation?Description<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview The discovery model is created by a business rule "Create a Software Normalization". This rule checks for the primary key data before it creates a discovery model. If the primary key of the record matched the primary key of the discovery model then it will update the matched record else it will create a new discovery model. Business rule that creates discovery model:https://<instance-name>.service-now.com/sys_script.do?sys_id=9ec2b34d37101000deeabfc8bcbe5d43&sysparm_view=&sysparm_record_target=&sysparm_record_row=1&sysparm_record_list=nameCONTAINScreate+a+software%5EORDERBYname&sysparm_record_rows=2 The primary key field is a value that is built based on the serial number and other factors. The business rule that builds the primary key is as below. https://<instance-name>.service-now.com/nav_to.do?uri=%2Fsys_script.do%3Fsys_id%3Defd6bb4d37101000deeabfc8bcbe5d44%26sysparm_record_target%3Dsys_script%26sysparm_record_row%3D3%26sysparm_record_rows%3D15%26sysparm_record_list%3DnameCONTAINSprimary%255EORDERBYname