Skip to main content

Extended CSV Export as Template

The Extended CSV export includes all columns of a data point's configuration. By modifying an export file, you can create a reusable template for rapidly deploying new data points with consistent settings. This is particularly useful when commissioning new devices that share the same point structure.

This guide assumes that you have already configured one or more data points with the correct parameters and are ready to create a template for reuse.

Notation: Column headers are shown in bold italic for clarity.

Step-by-Step Template Creation​

1. Prepare the Action Column​

Change the action column from GET to CREATE. This tells Mango to create new data points when the file is uploaded rather than attempting to retrieve existing ones.

2. Clear Identity Columns​

Remove the values from the following columns so that new identifiers are assigned during import:

  • originalXid -- Clear this column entirely.
  • deviceName -- Clear this column (you will set it per-device during import).
  • dataSourceId -- Clear this column.
  • dataSourceXid -- Clear this column.
  • dataSourceName -- Clear this column.

3. Clean Up Tag Columns​

  • Remove values from tags/deviceID (this will be set per-device).
  • Remove any tags/xxx columns that are not appropriate for a generic template. Keep only the tag columns that apply to all devices using this template.

4. Auto-Generate XIDs with Formulas​

Change the xid column to an Excel formula that constructs a unique XID from other columns. For example:

=CONCAT("DP_", BJ2, "_", BQ2)

This formula constructs the XID from the deviceID tag value and the point name, ensuring each data point gets a unique and predictable identifier.

5. Update Published Point Settings​

If your data points include published point configurations:

  • Change publishedPoints/0/action from GET to CREATE.
  • Clear publishedPoints/0/originalXid.
  • Clear publishedPoints/0/id.
  • Clear publishedPoints/0/xid.
  • Set publishedPoints/0/dataPointXid to the same formula as the xid column so that published points reference the correct data point.
  • Clear publishedPoints/0/publisherXid.

6. Hide Unchanged Columns​

Extended CSV exports can have close to 100 columns. To make the template easier to work with:

  • Hide all columns that you did not modify in the steps above.
  • Also hide originalXid, dataSourceId, and dataSourceName (which were cleared but do not need to be visible).

After hiding unnecessary columns, you should be left with just the following visible headers:

actiondeviceNamedataSourceXidtagstags/deviceTypetags/sitetags/deviceIDtags/dataHallxidpublishedPoints/0/actionpublishedPoints/0/xidpublishedPoints/0/dataPointXidpublishedPoints/0/publisherXid

The specific tag columns shown will depend on your tag schema. Adjust to match your deployment.

7. Save as Excel​

Save the file as an Excel spreadsheet (.xlsx) so that the formatting, formulas, and hidden columns are preserved. When you are ready to import, you can export a CSV copy from this Excel file.

Using the Template​

When commissioning a new device:

  1. Open the Excel template file.
  2. Unhide the deviceName column if hidden.
  3. Fill in the deviceName, dataSourceXid, and tag values (tags/deviceID, tags/site, etc.) for the new device.
  4. The xid column auto-populates via the formula.
  5. Export the visible data as a CSV file.
  6. Upload the CSV on the Bulk Data Point Edit page or via the REST API.
  7. Verify the newly created data points on the data source page.

Tips​

  • Keep the master template in Excel format so formulas and hidden columns are preserved across edits.
  • Test with a single device first before using the template for a large batch import.
  • Version control your templates by including a version number in the file name (e.g., VAV_Template_v3.xlsx).
  • Document the required fields for each template so that field technicians know which columns to fill in.
  • Validate after import by checking the data source page to confirm that all points were created with the correct names, tags, and configurations.