Duplicate software model created after adding PPN to the software entitlement record

[Maggie2]

Hello,

We are currently using ITSM Asset Management to manage our software and will upgrade to SAM Pro within the next couple of months.  We have installed the SAM Pro plugins in a lower environment and started to get ourselves familiarize with the new module. 

We noticed that the way how the software records are created differently.  In ITSM Asset Management, we need to start with creating a Software Model first, then publish to a catalog item and create license asset.  However, it seems to be the other way around in SAM Pro.  We will need to create a software entitlement first.  Once the software entitlement is created, the associated software will be automatically created based on the PPN entered in the software entitlement.  

So, here is the problem.  We already have software models created via ITSM Asset Management.  When we tried to add PPN to an existing software entitlement record (license asset in ITSM Asset Management), it automatically created a new model record.  So, we ended up having duplicate sw model records, the new ones link to discovery map, software entitlement but not to product catalog, and the old ones do not link to discovery map or software entitlement but to a product catalog.  

It seems like we have missed some steps after installing SAM Pro plugins.  I'm not sure if any of you have this experience before.  If so, how did you fix it?   Is there some kind of script we can run to map the existing models to the entitlements before adding the PPN to the entitlements?     

Thank you in advance for your advice and assistance.

Maggie

[dreinhardt]

Hi @Maggie2,

The observed behavior is due to the fact that each PPN is linked to a DMAP that uniquely defines a software model and it's attributes (Publisher, Product, Edition, Version, etc.).

When creating an entitlement based on a PPN, SAM Pro tries to find a suitable software model in the background based on the PPN/DMAP information. If the values match, the existing one is linked; if the values do not match, a new model is created. This behavior is intended to ensure that the correct model is assigned and that all properties are taken into account.

Can you please provide us with a few examples of duplicate SW models, including the most important properties as a screenshot, to confirm this. I have now only been able to reproduce it within SAM Pro.

Best, Dennis