Best Practice for Dealing with Duplicate Software Models

Matt Saccento
Kilo Contributor

‎07-14-2021 08:00 AM

I've got a lot of duplicate software models. Usually this creates an issue on the workbench, but sometimes, to my surprise, everything appears to be reporting correctly (they're all "license under management"). So a few questions:

  • Is it OK to have multiple software models for the same thing? Is it actually able to reconcile data from multiple software models correctly?
    • Is it best practice to have a single model?
  • If we want to eliminate the duplicates, what the best way to go about that?
    • Combine all the info into a one model and delete the others?
    • Just uncheck the "license under management" box on the duplicates?

Thanks, Matt

  • 3,069 Views
6 REPLIES 6

ritahester
Giga Contributor
In response to Daniel Slocum

‎02-04-2022 11:22 AM

Hi Daniel, 

Thank you for your response. That feature is NOT turned on in the SAM Properties. Any other suggestions on how this might occur? Would importing entitlements possibly create this scenario?

Daniel Slocum
ServiceNow Employee
ServiceNow Employee
In response to ritahester

‎02-07-2022 11:47 AM

Hi Rita,

Yes, an import of SW Entitlements does have the possibility of creating duplicates if the version and edition values are specified and do not explicitly match model record values already existing.  The best way to preclude this is to leverage the Publisher Part number (PPN) for every entitlement record even if that means creating a custom product should the PPN not be present in the Content Library. Entering a PPN in the entitlement import template and not specifying model details will then match on products in the content library or raise an Entitlement Import Error which can be systematically mitigated through the guided steps presented to the user on the Entitlement Import Error record.