Software Installation vs Software Discovery Model

[Elie Baho1]

In the SAM implementation course it mentions the following:

"If a Software Installation record matches a record found in the Software Discovery Model table, then the Software Installation table updates the software discovery model record."

If there's a match with a discovered model already found, then what information is updated in the Discovered Model table?

[dnnsrnhrdt]

Hi,

with reference to the docs (https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/software-asset-manageme...)

The information updated (Table cmdb_sam_sw_discovery_model), is the link between a discovery model and the software installation discovered on your devices

Software Installations

The Software Installations list contains the software installed in your organization and is populated by discovery.

Installed software is placed in the Software Installation [cmdb_sam_sw_install] table by Discovery, and a primary key is built (using Publisher, Display Name, and Version fields).

Discovery automatically matches the discovered software installation with a new or existing software discovery model using the primary key.

Best, Dennis

[Elie Baho1]

Allow me to reiterate my question:

I understand the path how the Discovery model table is built from the SW installations, then makes the link with the software model and then matches it to a software entitlement in the license workbench.

What I don't understand is: it mentions if a SW installation is FOUND in the Discovery model table, it updates the sw discovery model record.

If it's not found, I can understand if it creates a new record in the discovery model table, but if a match is found, what does it update in the discovery table if it's already a match?

[Alex Panzarella]

Blog that will assist with the different tables and what they do

https://community.servicenow.com/community?id=community_blog&sys_id=5a8a6cd4db7ab8103dd13ca8f49619b9

[Elie Baho1]

I understand what the tables do and how discovery works.

I just don't understand what the SW installations table updates in the Discovery model table when it's already a match.  It's not specified in the training docs.