Getting IDENTIFICATION_RULE_MISSING for Software Installation table (cmdb_sam_sw_install_list)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
I'm getting an IDENTIFICATION_RULE_MISSING error for the Software Installation table (cmdb_sam_sw_install) in SAM Pro. I’m loading discovery data from an external API into the Software Installation list table (cmdb_sam_sw_install_list) using IntegrationHub ETL. All the required fields (installed_on, display_name, publisher, version, etc.) are mapped, and the associated CI class is also mapped through installed_on, but the error still persists.
Because cmdb_sam_sw_install does not extend cmdb_ci, it does not appear in the CI Class Manager, so I can't create an identification rule using the standard method. I also tried adding an identifier directly in the Identifiers table, but that didn’t work either.
Does anyone have guidance or documentation on how to add the required identification rules for cmdb_sam_sw_install before the Utah release? I understand that Utah introduces IRE support for non-CMDB tables, but is there any way to insert records into cmdb_sam_sw_install via IntegrationHub ETL in Yokohama or Zurich?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi,
Your ETL should point to the main host CI which is from a hardware table and software installation table should be a related list to the host.
You cannot directly map software installation table without the host details.
Regards,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Vivek,
Thanks for your response. Could you please share more details if you have any regarding IRE for the Software Installations table?
I have already mapped the installed_on field of the Software Installation table to the corresponding hardware CI, and that mapping works fine without any issues. However, for the Software Installation table itself, I’m still getting the IDENTIFICATION_RULE_MISSING error because it does not have any IRE rules.
Do you have any guidance or insights on how IRE works for the Software Installations table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Vivek,
Thanks for your response. Could you please share more details if you have any regarding IRE for the Software Installations table?
I have already mapped the installed_on field of the Software Installation table to the corresponding hardware CI, and that mapping works fine without any issues. However, for the Software Installation table itself, I’m still getting the IDENTIFICATION_RULE_MISSING error because it does not have any IRE rules.
Do you have any guidance or insights on how IRE works for the Software Installations table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
The error IDENTIFICATION_RULE_MISSING appears when no identification rule is present in the system.
Utah is the first release that supports IRE for non-CMDB tables, such as Software Installation (cmdb_sam_sw_install). Therefore, you can create them in Utah. Before Utah, it was not feasible to define IRE in the Software Installation table.
Please upgrade your instance, as the latest ServiceNow release is Zurich, whereas Utah was released in 2023.
If this clarifies your doubt then, mark it as accepted solution ✅ and give thumbs up 👍!