---
sourceDocument: Australia Operational Technology Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/operational-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Update the column mapping script

# Update the column mapping script {#ariaid-title1}

Release version: Australia  
Updated September 9, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
To transfer the custom column data to the Configuration Management Database (CMDB), update the column mapping script to add the corresponding entry to the importSetColumnsVsStagingColumnsMap object.

## Before you begin

Role required: ot_excel_import_user

## About this task

The importSetColumnsVsStagingColumnsMap object in the SGOTAssetImportExcelConstants script controls which columns from the SG OT Excel Stagings (sg_ot_excel_staging) table are
included when you trigger the CMDB import process. If you add a custom column to the staging table, you must add a corresponding entry to the importSetColumnsVsStagingColumnsMap object.
Otherwise, the custom column is ignored during import. For more information about triggering the CMDB import process, see [Trigger a CMDB import for valid staging records](https://www.servicenow.com/docs/U1Gv9UW1v5_TZMrMfmXWLw "Trigger a Configuration Management Database (CMDB) import for your valid staging records to directly import them into the CMDB").

Each entry in importSetColumnsVsStagingColumnsMap object is a key-value pair with the following format:

<kbd class="ph userinput">"&lt;import set column name&gt;": "&lt;staging table column name&gt;"</kbd>

The key is the field name that appears in the JSON payload sent to the CMDB import (sn_otsm_sgc_sg_ot_excel_import) set. The value is the name of the corresponding column on the SG OT Excel Stagings table.

When you create a key and value, they're typically identical. For example, a custom staging column named u_my_custom_field maps to itself. Only use a different name if you need the import set field name
to differ from the staging table column name.

## Procedure

1. Navigate to AllIndustrial Workspace AdminImport OT Devices - Script Includes.
2. Select the SGOTAssetImportExcelConstants record.
3. In the importSetColumnsVsStagingColumnsMap object, add a line in the following format:  
   <kbd class="ph userinput">"ETL Column Name": "Staging Table Column Name"</kbd>

   For example: <kbd class="ph userinput">"u_my_custom_field": "u_my_custom_field"</kbd>
4. Before your new entry, add a comma at the end of the line so that the object remains valid JavaScript.
5. Select Update.
{#update-column-mapping-script-sgc-excel__steps_aqs_ljp_skc}

## What to do next

Configure the Robust Transform Engine (RTE) mapping for the Extract Transform Load (ETL). For more information, see [Configure the RTE mapping for ETL](https://www.servicenow.com/docs/IyDo4vvVjYbBGnfXXuu9zg "Configure the Robust Transform Engine (RTE) mapping for the Extract Transform Load (ETL). The ETL process transfers custom column data from the import set to the target Configuration Management Database (CMDB) class.").

*[\>]: and then