---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Duplicate company names in extension tables

# Enabling duplicate company names in extension tables {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
You can create records with duplicate company names in extension tables, such as Customer Account \[customer_account\] table, without causing normalization conflicts in Normalization Data Services.

If your ServiceNow instance has company records in the Company \[core_company\] table from IT Service Management (ITSM) or IT Operations Management (ITOM), and you are adopting Customer Service Management (CSM), you may encounter errors when creating Customer Account records for the same companies.

Normalization Data Services manages company name normalization across the Company \[core_company\] table and its extension tables, such as Customer Account \[customer_account\] table. By default, Normalization Data Services enforces unique company name across all company-related tables. This causes conflicts when a vendor in the Company table and a customer account share the same name.

The glide.cmdb.canonical.use_base_core_company_only property introduces support for creating duplicate company names in extension tables. When you enable this property, Normalization Data Services restricts unique company name validation to the base, Company \[core_company\] table only. Each duplicate record in an extension table still links to the correct normalized record in the base
table.  
Enable this property if you are upgrading from Zurich or an earlier release. You must use Customer Service Management with one or more of the following applications that extend the Company \[core_company\] table:

* ITSM Software Asset Management
* Hardware Asset Management
{#enhanced-nds-for-duplicate-records__ul_fv4_xg4_k3c}

## Configure Normalization Data Services to create duplicate company name in extension table {#ariaid-title2}

Configure the Normalization Data Services feature to enable records with duplicate company names across core company's extension tables, such as Customer Account \[customer_account\] table.

### Before you begin

Role required: nds_admin

### About this task

Note:  
This procedure applies only if you are upgrading from Zurich or an earlier release. If you are on the Australia release or later, this feature is enabled by default and no action is required.

### Procedure

1. Navigate to AllSystem DefinitionsScript includes.
2. Search for and open the ClearNonCoreCompanyExtensionsFix script.
3. Select Run Script.  
   The script clears the hash values and sets the Normalized flag to false for all duplicate company name records in the Company \[core_company\] extension tables.
4. Verify that the script ran successfully.
   1. Navigate to AllSystem LogAll.
   2. Search for the following log entries in the Log \[syslog_list.do\] table.  
      * \[ClearNonCoreCompanyExtensionsFix\] Cleared hash
      * \[ClearNonCoreCompanyExtensionsFix\] Set canonical=false
      {#configure-enhanced-nds-to-create-duplicate-records-in-extension-table__ul_ttn_rkp_k3c}

   {#configure-enhanced-nds-to-create-duplicate-records-in-extension-table__substeps_pmc_1hp_k3c}  
   The log entries confirm that the hash values are cleared and the normalized flag is set to false.
5. Add the glide.cmdb.canonical.use_base_core_company_only system property and set its value to True.  
   For more information, see [Add a system property](https://servicenow-prod.fluidtopics.net/P1YgMM0DTfCJvVsoqOoJ6Q "Add or create a property to control system behavior.").
6. Normalize data in the CMDB table.
   1. Navigate to AllNormalization Data ServicesGuided Setup.
   2. In the Normalize Configuration Items (CMDB) Model step, select Configure.
   3. Select Start Update.
   4. Select Close after the update completes.
   {#configure-enhanced-nds-to-create-duplicate-records-in-extension-table__substeps_h12_1yx_k3c}
7. Verify if you can create records with duplicate company names in extension tables.
   1. Navigate to All, and then enter `customer_account.list` in the filter to go to the Customer Account table.
   2. Select New.
   3. On the form, fill in the fields.  
      For a description of the field values, see [Account form](https://www.servicenow.com/docs/access?context=customer-service-account-form&version=australia&pubname=australia-customer-service-management&ft:locale=en-US).
   4. Select Submit.
   {#configure-enhanced-nds-to-create-duplicate-records-in-extension-table__substeps_aqc_5fc_l3c}
8. **Optional:** If you're using Hardware Asset Management (HAM), run the following one-time script.
   1. Navigate to AllSystem DefinitionsScript includes.
   2. Select New.
   3. Enter a Name for the script include.
   4. Enter the script include code in the Script field.  

          var worker = new CanonicalUpdaterWorker(); 
                     var tables = { 
                     'sn_hamp_hw_manufacturer': ['company'],
                     'cmdb_hardware_product_model': ['normalized_company'], 
                     'cmdb_consumable_product_model': ['normalized_company'], 
              }; 
              for (var table in tables) {
                   if (tables.hasOwnProperty(table)) {
                   var fields = tables[table]; 
                   for (var i = 0; i < fields.length; i++) {
                       worker.addNormalization(table, fields[i]); 
                   } 
                 } 
              } 
              worker.setProgressName(gs.getMessage("Normalization Data Service")); 
              worker.setBackground(true); 
              worker.start();

   5. Select Submit.
   6. Select Run Script.
   {#configure-enhanced-nds-to-create-duplicate-records-in-extension-table__substeps_lpz_j2c_l3c}

*[\>]: and then