How to stop duplicates created when the discovery source in asset is set to SNAssetManagementDescriptionDuplicates are created when the discovery source in asset is set to SNAssetManagement. CauseThe cause is glide.asset.create_ci_with_ireResolutionThere is a way to stop this. To answer question, there are 2 methods to this. 1. Add the sys_property: glide.asset.create_ci_with_ire. and set it to true. This will create the CI when you create the original asset which discovery will match on based on IRE and will not create a duplicate. https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/asset-management/concept/c_ManagingAssets.html The system property glide.asset.create_ci_with_ire enables CIs to be created from assets using the ServiceNow® Configuration Management Database (CMDB) Identification and Reconciliation engine (IRE). This property affects CI classes that have an identification rule on serial number and have no dependent relationships with other CI classes. Note: CI classes that are extended from the hardware CI class [cmdb_ci_hardware] are also created from assets using the IRE, but are not controlled by this property. CIs created with the IRE are named using the format Serial number - Model name and the source is SNAssetManagement. The Serial number field is mandatory on assets with model categories that correspond to these CI classes. Asset creation fails if its serial number is present on an existing CI or asset. The Serial number field is also required to receive purchase order line items for model categories that correspond to these CI classes. The Serial number field is not mandatory to create pre-allocated assets, but the serial number must be provided when the asset is allocated. 2. Check the Force CI verification box on model category. https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/product-catalog/task/t_CreatingAssetsManually.html The conditions under which an asset is not automatically created include the following. Forced CI verification: If you select the Enforce CI verification check box in the Model Category form, the system does not create an asset automatically when a CI is created or discovered. When Enforce CI verification is enabled, newly created CIs do not trigger an automatic creation of an asset. Instead, these newly created CIs have their Requires verification field automatically set to true, which displays the following UI actions for the CI: Create Asset: Creates an asset and sets Requires verification to false. Merge CI: Merges duplicates of a CI. This action is useful if an asset for the CI was created in a separate process, which created an associated CI. Then a second CI was created either manually or via the discovery source - and the duplicate CIs did not properly coalesce.