Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

cmdb_sam_sw_install table missing on fresh Zurich instance

kunalachary
Tera Contributor

Hi all,

Per the ServiceNow documentation, cmdb_software_instance is deprecated as of the Zurich release, and cmdb_sam_sw_install is now the table used to store the relationship between a Computer CI and a Software Package CI.

However, on our Dev instance — a freshly installed Zurich version — this table doesn't exist. (Screenshot attached.)

Separately, we're also seeing the GlideRecord API fail silently when writing to cmdb_software_instance — specifically, the setValue() method fails silently, with no exceptions thrown.

What I'd like to know:
      - Is cmdb_sam_sw_install gated behind a specific plugin or SAM Pro license?

      - If so, which plugin needs to be activated to make this table available. Any documentation related to the same?

     - Is there any documentation on the setup steps required post-installation?

     - Is the silent failure on cmdb_software_instance writes expected/related to its deprecation?

Any pointers would be appreciated.

3 REPLIES 3

Tanushree Maiti
Tera Patron

Hi @kunalachary 

 

Can you confirm if you have SAM role to check this. Like sam_admin?

Also confirm following plugin is installed in your instance.

Software Asset Management Core (com.snc.sam.core)

 

Refer: https://www.servicenow.com/community/cmdb-forum/not-able-to-see-cmdb-sam-sw-install-table/m-p/260564...

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Dr Atul G- LNG
Tera Patron

Hi @kunalachary 

 

yes it is part of SAM Pro '[ You can install this plugin in PDIhttps://youtu.be/7P4PIwZOg-0

 

The Software Install table (cmdb_sam_sw_install) is the base table SAM Pro is built on. The Software Install table is a 1:1 from your discovery sources. For example, if you have SCCM or ServiceNow Discovery identifying software it would be loaded into this table with the same values as the source.

The next step is the SAM module looks at your raw Software Install data and normalizes and enriches it in the Discovery Model table (cmdb_sam_sw_discovery_model). This normalization happens automatically when new software install data is populated (software model is not a requirement for normalization).

After everything is normalized we come to the software model table (cmdb_software_product_model). The software model references what discovery models we want in scope.

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG

****************************************************************************************************************
Key Points Covered Recap of Previous Session Asset lifecycle: Plan → Request → Approve → Source → Allocate → Manage → Support → Sunset. Modules involved: Request, Contract, Inventory, License, Model, End-of-Life Management. Purpose of SAM Manage software licenses: what is owned, used, and needed ...

J Siva
Kilo Patron

Hi @kunalachary 
Once you install Software Asset Management (sn_itam_samp), the cmdb_sam_sw_install table will be installed automatically.
I just installed in my PDI and verified.

JSiva_0-1785485364650.png

 

Regards,
Siva