2023-Nov-03-R11.1a

Export/Import ADT

The functions of exporting/importing ADT are introduced so that the ADTs created by power users can be shared with end users and repeatedly used by end users.

Export ADT File

ADT can be exported as an XADT file or a CSV file for documentation.

  • Export ADT to CSV file: Click Export to CSV Only from the drop-down menu of an open ADT to export the file. The exported CSV file will be automatically saved to the default location for storing downloaded files (for example, C:\Users\<your username>\Downloads).

  • Export ADT to XADT file: The system offers two entrances for exporting ADT to XADT file. The exported ADT will be automatically saved to the default local Download folder.
    • You can Click Export from the drop-down menu of an open ADT. Then the ADT will be exported to XADT file.

    • Alternatively, you can click Export from the drop-down menu of a target ADT in the Folder Tree of the Automation Data Table Manager to export the ADT.

What data will be exported?

  • The data displayed in the ADT and the configurations made when ADT is defined.
  • The paths to the resources for building the ADT Base Table (for example, NIT, NIC, Application Path, Map Folder, Site, Device Group, Imported CSV) are contained in the exported file so that the paths to the resources can be reused when the file is imported to NetBrain again (if the resources still exist).
  • The paths to the resources for building the ADT Column Groups (for example, NIT, NIC, Application Path, Site, Device Group, Imported CSV) are contained in the exported file so that the paths to the resources can be reused when the file is imported to NetBrain again (if the resources still exist).
  • The exported file does not contain the associated resources in the ADT (such as the NIT, NIC, etc.).
  • The data manually added to the ADT after the basic ADT is defined will not be exported.

For more information, see Data Exported/Imported

Import ADT File

The system enables users to import an ADT file to be used in the NetBrain system. You can select a folder (both major folders and subfolders can be selected) for storing the imported ADT file from the Folder Tree in Automation Date Table Manager, then import the ADT file and save the imported ADT file under the folder.

  1. Click  > Automation Data Table Manager.
  2. From the ADT Folder Structure in the left pane, select a folder for storing the file to be imported to ADT, then click Import from the folder's drop-down menu.
  1. In the prompt Import Automation Data Table dialog, Click Add Automation Data Table
  1. Select a local file, then click Open to select the file.
  1. Click Import to import the file to ADT. 
Information Note: If the ADT to be imported contains manually added data, the manually added data will not be imported. 

Data Exported/Imported

The following two tables describe the data to be exported/imported when Base Table/Column Group are built by different methods.
For the data in the Base Table of ADT:
No. Method for Building Base TableData Exported/Imported
1Pre-replicated Intent Template
  • The path to the intent template used for building Base Table is included in the exported file.
  • The data of the path to the intent template can be used if the file is imported to NetBrain again (if the NIT still exists).
2Intent Cluster
  • The path to the intent cluster used for building Base Table is included in the exported file.
  • The data of the path to the intent cluster can be used if the file is imported to NetBrain again (if the NIC still exists).
3Application Path
  • The paths used for building base table are included in the exported file.
  • The paths can be used if the file is imported to NetBrain again (if the paths still exist).
    Information Note: The paths of the application have to be selected again when the file is imported.
4Map and Intent
  • The path to the map folder used for building Base Table is included in the exported file.
  • The path to the map folder can be used if the file is imported to NetBrain again (if the map folder still exists).
5Devices of Device Group
  • The path to the Device Group used for building Base Table is included in the exported file.
  • The path to the Device Group can be used if the file is imported to NetBrain again (if the Device Group still exists).
6Site
  • The path to the Site for building Base Table is included in the exported file.
  • The path to the Site can be used if the file is imported to NetBrain again (if the Site still exists).
    Information Note: The Site has to be selected again when the file is imported.
7Imported CSV
  • The CSV data is included in the exported file.
  • The CSV data can be directly used if the file is imported to NetBrain again.

For the data in the Column Group of ADT:
No. Method for Building Column GroupData Exported/Imported
1Intent Template
  • The path to the intent template used for building Column Group is included in the exported file.
  • The intent template can be used if the file is imported to NetBrain again (if t the NIT still exists).

2Intent Cluster
  • The path to the intent cluster used for building Column Group is included in the exported file.
  • The intent cluster can be used if the file is imported to NetBrain again (if the NIC still exists).

3Intent Replication for Path
  • The path to the intent template for path intent replication is included in the exported file.
  • The intent template can be used if the file is imported to NetBrain again (if the NIT still exists).
  • The configurations made in Define Logic to Populate New Columns for Each Row area are reserved.
  • The exported file is in unlocked status so that it is reachable to most end users.


4Monitoring Probe
  • The Probe Name of the probe used for building Column Group is included in the exported file.
  • The Probe Name of the probe can be used if the file is imported to NetBrain again (if the probe still exists).

5Path Intent Filtering
  • Only path column data is exported.
  • Path column data is re-built based on the Base Table data when the ADT is exported.
  • The data manually added to the path column will not be exported/imported.

6Function Call
  • Only the data in the source column of the ADT is exported.
7Imported CSV
  • The data of the CSV for building Column Group is included in the exported file.
  • The CSV data can be directly used if the file is imported to NetBrain again.


Auto-Clean ADT Execution Log

ADT execution log can be automatically cleaned to reduce redundant data. 

Following the steps below to configure to automatically clean ADT execution log. 


  1. Go to Domain Management > Global Data Cleaning Settings.
  2. Locate Automation Data Table Execution Logs entry from the Other Data table.
  3. Set the period for cleaning ADT execution logs.
    Information Tip: You can click Clean Now in the last cell of this entry to manually clean ADT execution log data once.