Business Rule(Create CI on insert) Blocking Import Despite No Duplicate CI Found

[ahmadfaruqu]

One of the business rules (Create CI on insert) is preventing data from being imported into our alm_hardware table.
As per my understanding, it is meant to stop duplicate CIs.
However, when I manually check, I don’t see any existing records matching the data I’m trying to import.

Thank,

Faruqui

[GlideFather]

@ahmadfaruqu or there is something called "Enforce CI Verification": https://www.servicenow.com/community/itsm-forum/enforce-ci-verification/m-p/918889

Perhaps it can also bring some ideas to you

[ahmadfaruqu]

Hi Kamil,

Thanks a lot for the detailed explanation — it’s very helpful.

I’ve already set the coalesce on the alm_hardware table using the serial number field. However, as the CI (cmdb_ci_computer) record is auto-generated during the process, I now realize I’ll need to add logic there as well to avoid duplicate entries.

Also, during my testing, I did observe cases where records had blank values or extra spaces, which could lead to duplication or messy data. So, I’ll make sure to handle those scenarios properly as well.

Appreciate your guidance!

Best regards,
Ahmad

[GlideFather]

Thanks for confirmation and good luck 🤞