{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":36869,"path":"operational-technology/operational-technology-manager/update-column-mapping-script-sgc-excel.md","title":"Update the column mapping script","bundle":null,"doc_type":null,"release":"australia","body":"\n# Update the column mapping script\n\nTo 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.\n\n## Before you begin\n\nRole required: ot\\_excel\\_import\\_user\n\n## About this task\n\nThe **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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/trigger-cmdb-import.md).\n\nEach entry in **importSetColumnsVsStagingColumnsMap** object is a key-value pair with the following format:\n\n`\"<import set column name>\": \"<staging table column name>\"`\n\nThe 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.\n\nWhen 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.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Industrial Workspace Admin** &gt; **Import OT Devices - Script Includes**.\n\n2.  Select the **SGOTAssetImportExcelConstants** record.\n\n3.  In the **importSetColumnsVsStagingColumnsMap** object, add a line in the following format:\n\n    `\"ETL Column Name\": \"Staging Table Column Name\"`\n\n    For example: `\"u_my_custom_field\": \"u_my_custom_field\"`\n\n4.  Before your new entry, add a comma at the end of the line so that the object remains valid JavaScript.\n\n5.  Select **Update**.\n\n\n## What to do next\n\nConfigure the Robust Transform Engine \\(RTE\\) mapping for the Extract Transform Load \\(ETL\\). For more information, see [Configure the RTE mapping for ETL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/complete-rte-mapping-etl-sgc-excel.md).\n\n**Parent Topic:**[Add a custom column to the staging table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-manager/add-custom-column-staging-table.md)\n\n"}}