Linking Software Model table to the Software Discovery Model table

[Frank Nijssen]

Hi,

We are currently implementing Life Cycle Management in SAM-P and we and we would like to create a report linking records in the Software Installation table to Software Model Lifecycle table. We created a database view, joining several tables in our attempt to achieve this.
One of the joins in this view is about linking the Software Model table to the Software Discovery Model .

Within a record of the Software Model table, you can click on Show Matching Software Discovery Models in Related Links and it shows something like this:I clicked on the filter icon and I concluded from this that the connecting fields would be
Product, Language, Platform, Edition and Version.

However, the ServiceNow Docs on
https://docs.servicenow.com/bundle/newyork-it-service-management/page/product/asset-management/conce...
says this about the subject:

The ServiceNow platform uses any of the following field combinations to match the new software discovery model to an
existing software model.

• Display Name, Publisher, and Version
• Display Name and Version if the Publisher field is empty
• Display Name only if the Publisher and Version fields are empty

This is not the same as the filter with the 5 fields mentioned above and the database view produces different results when I use these two alternate field options.

Could anyone advise me on what would be the recommended way to join these two tables?

[Deepti G]

Hi,

We are also trying to do the same.

Did you get the solution to this problem?

Thanks!

[Will Young2]

Hi Frank,

I can see what you are trying to accomplish and I wonder if there is not a better way. It seems like you are expecting to go to a software installation record and see the associated lifecycle(s). However, most people don't work directly on the software installation table, by design. This is why ServiceNow has provided the lifecycle reports as they have.

There are still solutions to your request, but it isn't as cut and dry as you'd hope. Can you narrow down specifically what questions you are trying to answer with this report? For example...

• How many software installations are EOL in our environment?

I have built scripts to perform the same type of matching done between installations and discovery maps in order to find software models. That may help. You may also consider a custom table or field and a scheduled job which counts installations and records the number, associated with the software model and/or lifecycle. Regardless of how you choose to do this, it will be a custom solution which your company will need to maintain.

This seems like something many customers could benefit from. You might try submitting this as an Idea using the Idea Portal here in Community.

Will Young
Service Delivery Manager
GlideFast Consulting - ServiceNow Elite Partner
ServiceNow CSA, CAD, CIS-ITSM/SAM/EM/SM/Disco
IAITAM Certified Software Asset Manager

[Frank Nijssen]

Hi Will, 
Thanks for responding. 
What we are trying to accomplish here is for each item in the Software Installation table, to show its corresponding EoS date and Risk level. The EoS/Risk data are retrieved from the Software Model Lifecycle (sam_sw_model_lifecycle) table.
We used another tool for this, but now we are trying to get the same using SAM-P in ServiceNow.

[Will Young2]

Hey Frank,

I think this is an interesting use case that ServiceNow may want to review as a potential enhancement. Perhaps you could put together this explanation and submit it in the Idea Portal. In the meantime, I can see several technical ways that might make this easy to report on, but all of them require some sort of development on the platform (new field, new relationship, new script, etc). If you find anything out-of-box I hope you'll update us.

Cheers!

Will Young
Service Delivery Manager
GlideFast Consulting - ServiceNow Elite Partner
ServiceNow CSA, CAD, CIS-ITSM/SAM/EM/SM/Disco
IAITAM Certified Software Asset Manager

[andydoyle]

Hi Frank.

We're implementing SAM PRO where I work, and are having the same issues while trying to report the lifecycle stage of a given software installation. We also tried matching on product, version, edition, and language, and like yourself, get multiple matches.

Did you ever find a solution?

Andy