---
sourceDocument: Australia Telecom Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-service-ops

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecom Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Extend TNI entity support

# Extend TNI entity support for duplicated ETLs {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.

## Before you begin

Role required: admin  
* Ensure TNI is installed and active in your instance.
* Complete the duplication of the Telecom Discovery Builder framework ETL into the target application scope.
{#configuring-tni-entiry-support-for-duplicated-etls__ul_edf_r1s_dfc}

## Procedure

1. Navigate to AllIntegrationHub ETL.
2. Select the CMDB Application associated with the duplicated ETL.  
   The CMDB Integration Studio application in a new page
3. In the ETL configuration page, check the Execute Before Script option.
4. Replace the default script with the following:  

       (function(input, runId) {
           new sn_tsom_core.TelcoGenericMappingHelper().checkAndUpdateIrePayloadForTni(input);
       })(input, runId);

5. Click Update to save the changes.  
   The duplicated ETL links TNI entities for discovered CIs.

*[\>]: and then