cmdb_ci_spkg creating new CIs instead of updating

[EtuodiE]

Hi ITOM community, 

I am working on our software table, and I discovered that all our software CIs have the same created and update date which leads to lots of CIs. Our identifier is set to Key which is OOB.  I will appreciate any ideas on how to tackle this. 

[Vishnu-K]

Hi @EtuodiE ,

As of now, my understanding is that you are using an out-of-the-box identification rule on cmdb_ci_spkg, where the key is a combination of Software Name and Version.

The issue arises when this data is coming from multiple sources. In such cases, inconsistencies can occur - for example, one source may provide the version while another does not. This leads to duplicate records being created instead of a single consolidated one, which is not ideal.

Although it might seem tempting to change the identifier to just the name, that would introduce a different problem. The version is a critical attribute. For instance, if the same software exists on two devices but with different versions, both should be represented as separate records. If we rely only on the name as the identifier, it would incorrectly result in a single record instead of two.

So, the better approach here is not to change the identifier. Instead, the focus should be on ensuring that all data sources consistently provide both the software name and version accurately.

Hope this helps

If it helped you please do mark it as helpful and accept the solution

Thanks,

Vishnu