Product Model Display Name Includes Duplicate Manufacturer After SG-SCCM ImportIssue .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Product models created from Service Graph Connector for Microsoft SCCM (SG-SCCM) data can contain the manufacturer in both the Manufacturer and Name fields. This can produce a display name that appears to repeat the manufacturer. For example, a model with the manufacturer Dell Inc. and the name Dell Pro 16 Plus PB16250 can have the display name Dell Inc. Dell Pro 16 Plus PB16250. Symptoms .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The product model display name contains both Dell Inc. and a model name beginning with Dell.Setting glide.cmdb_model.display_name.shorten to true does not remove the manufacturer from the display name.Manually changing the product model name does not provide a permanent resolution.A subsequent SG-SCCM import can create the original model again because SCCM continues to supply the unchanged model value. Facts .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The product model display name is generated from model identity fields, including the manufacturer and model name.The glide.cmdb_model.display_name.shorten system property controls whether duplicate manufacturer information is omitted from the generated display name.The default value of the property is false.The property changes only the generated Display name. It does not change the source value stored in the model Name field.The manufacturer is omitted only when the manufacturer name matches the manufacturer text in the model name. Differences in punctuation or company suffixes prevent the values from matching.For example, Dell Inc. does not exactly match the leading text Dell in Dell Pro 16 Plus PB16250.SG-SCCM imports SCCM data into the CMDB and uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE) to transform and process the data.For the affected models, SCCM obtains the model value from Win32_ComputerSystem.Model. The value is stored in the SCCM database as v_GS_COMPUTER_SYSTEM.Model0. Release Yokohama, Zurich, Australia Cause .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The source computer reports a model value that already contains the vendor name. For the affected Dell Pro series, the firmware-provided model string is exposed through Windows Management Instrumentation (WMI) as Win32_ComputerSystem.Model. SCCM collects this value during hardware inventory and stores it as v_GS_COMPUTER_SYSTEM.Model0. SG-SCCM imports the value without removing the leading vendor text. The ServiceNow manufacturer record contains Dell Inc., while the imported model name begins with Dell. Because these values are not an exact match, glide.cmdb_model.display_name.shorten does not identify the manufacturer text as a duplicate. Changing the product model manually does not correct the source data. When SCCM sends the original value again, the integration cannot find a model with that source name and can create the model again. Resolution .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } .kb-wrapper .kb-steps { counter-reset: kb-step; list-style: none; margin-left: 0; } .kb-wrapper .kb-steps > li { position: relative; min-height: 32px; padding-left: 44px; counter-increment: kb-step; } .kb-wrapper .kb-steps > li::before { content: counter(kb-step); position: absolute; left: 0; top: 1px; width: 28px; height: 28px; border-radius: 50%; background: #032D42; color: #63DF4E; font-weight: bold; line-height: 28px; text-align: center; } .kb-wrapper .kb-note { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 12px; margin: 0 0 12px 0; } .kb-wrapper .kb-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 12px; margin: 0 0 12px 0; } The glide.cmdb_model.display_name.shorten property cannot change the imported model name. Normalize or remap the value before model lookup and creation. Option 1: Normalize the model value in the source Verify the value returned by Win32_ComputerSystem.Model on an affected computer.Review the collected value in the SCCM hardware inventory and in v_GS_COMPUTER_SYSTEM.Model0.Determine whether the computer manufacturer or SCCM administrators can normalize the value before SG-SCCM imports it.Run the SG-SCCM Computer Identity import and verify that the normalized model is used. Option 2: Normalize the value in the SG-SCCM transformation Open IntegrationHub ETL and select the generated SG-SCCM Computer Identity integration.Review the source-data preparation operations used to produce the cleansed manufacturer and model values.Create a custom RTE entity operation that normalizes only the affected model values before model lookup and creation.Configure the operation to preserve unaffected manufacturers and models.Test the transformation with representative records from each affected model family.Run the generated SG-SCCM Computer Identity import.Verify that the expected product model is selected and that another model is not created with the original source name. Option 3: Evaluate an alternate SCCM model field Query Win32_ComputerSystemProduct.Name on affected and unaffected computers.Verify whether SCCM stores the value in v_GS_COMPUTER_SYSTEM_PRODUCT.Name0.Confirm that the alternate field consistently returns the required model name for all computer manufacturers imported by the data source.Map the verified alternate value to the model input through IntegrationHub ETL when possible.If a SQL change is required, update only the generated, connection-specific Computer Identity data source. Do not directly modify or execute the out-of-box SG-SCCM prime data source.Replace v_GS_COMPUTER_SYSTEM.Model0 AS model with v_GS_COMPUTER_SYSTEM_PRODUCT.Name0 AS model only after validating the result for all imported computers.Run a test load and verify the resulting model values before enabling the scheduled import. Warning: Custom RTE operations and SQL changes are customer-managed customizations. Test and document the changes in a non-production instance. Revalidate them after upgrading the SG-SCCM application. Changing the selected SCCM field affects every computer processed by that generated data source, not only the affected Dell models. Note: Correct the transformation before cleaning up duplicate product models. Manually renaming a model while the source continues to send the original value can cause the model to be created again. Related Links .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Service Graph Connector for Microsoft SCCMModel form fieldsComponents installed with Model ManagementService Graph Connector for Microsoft SCCM 3.0 Setup Guidelines