Edition Field Population in ServiceNow SAM — Technical OverviewSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Overview of How the Edition Field Is Populated on software discovery models Method 1: SAM Normalization JobThe SAM normalization job runs on a scheduled basis and populates Edition by matching software discovery model records against the content library. Edition is pulled from the content library entry if a match is found. In addition to this it also creates a normalization suggestion rule in table samp_normalization_suggestion if not pre-definitely existshttps://www.servicenow.com/docs/r/it-asset-management/software-asset-management/normalization-suggestions.html Method 2: Discovery Application PatternsWhen Discovery discovers applications like MSSQL or Oracle, it captures edition as a structured attribute and adds it to the display name of the software install record. The normalization job then reads the display name, matches it against the content library, and populates the Edition field on the discovery model. https://www.servicenow.com/docs/r/zurich/it-operations-management/itom-visibility/mssql-data-collected-pattern.html Method 3: Integration Sources (SCCM, JAMF) Integration sources such as SCCM and Jamf can populate the edition_override field on the Software Installation CI. This value is appended to the discovery model’s display name, which is then used by the normalization process to populate the Edition field. ServiceNow Discovery does not populate the edition_override field by default. A custom solution may be available to collect software edition information from SCCM. ServiceNow customers who require this functionality can open a case with ServiceNow Support. Support will review the requirements and provide the available solution when applicable. Core Requirement The display name of the discovery model must contain edition information for the normalization process to populate the Edition field. If a product does not have edition information in the display name (either from the discovery pattern output, content library, or integration source override), the Edition field will remain empty. This is expected behavior and not a configuration issue. Diagnostic Approach: Check the discovery model's display name for edition keywordsVerify the product exists in the content library with edition definedConfirm the discovery pattern executed successfully (if applicable)Validate the integration transform maps edition data to edition_override (if applicable)