20,919,685Total Points24,106Total Sites23,382Cell Towers69,500Racks Monitored56,753HVAC Units Monitored31,322UPS Units Monitored24,788Generators Monitored20,919,685Total Points24,106Total Sites23,382Cell Towers69,500Racks Monitored56,753HVAC Units Monitored31,322UPS Units Monitored24,788Generators Monitored20,919,685Total Points24,106Total Sites23,382Cell Towers69,500Racks Monitored56,753HVAC Units Monitored31,322UPS Units Monitored24,788Generators Monitored

Chapter 2: Core ConceptsLesson 7 of 65

How to Apply and Manage Tags in Bulk

Learn how to add, edit, and remove tags across hundreds of data points at once using Bulk data point edit, JSON export/import, and REST API bulk operations.

  • 10 min read
  • Intermediate
  • Mango 4.x / 5.x

Overview

Tags are key-value pairs attached to data points that enable filtering, dashboard auto-population, and bulk operations. Tags do not grant access — each point’s own permissions control that. On a small system you can tag points one at a time. On a deployment with hundreds or thousands of points, you need bulk methods.

Method 1: Bulk Data Point Edit (UI)

The fastest way to bulk-tag from the Mango by Radix IoT interface:

  1. Navigate to Data integration → Bulk data point edit. The page is superadmin-only
  2. In the point browser on the left, choose how to find the points — Lists (watch lists), Devices, Sources (data sources) or Tags — and pick the ones you want
  3. Use Show filters on the table to narrow the list further, for example by an existing tag value
  4. Select points using the checkboxes, or Select all (matching filters) to take every point the current filter returns rather than only the visible page
  5. Click Edit, open the Tags tab, add or change tags, then click Save. A tag you add lands on every selected point; tags you leave alone keep each point’s own value
Tip: Narrow first, then select. If you have 500 points but need to tag only the 50 belonging to Building A, pick Building A’s data source under Sources first to avoid accidentally tagging the wrong points.

Method 2: Data Source JSON Export/Import

For complex tag changes or when you need a spreadsheet-based review process:

  1. Navigate to Data integration → Data sources
  2. Select the data source, open the ellipses (…) menu, and choose Export with points
  3. Edit tags in the exported JSON (or convert to CSV for review)
  4. Import the modified file back into Mango

This method gives you full control and an audit trail (save the file before and after). It's the best approach when you need to review tag changes before applying them.

Method 3: REST API

For programmatic tag management, use the REST API. REST updates require server login credentials and are best reserved for admins or automation scripts — not casual UI users.

Warning

A data point has no partial-update endpoint. PUT /rest/latest/data-points/{xid} replaces the point with the body you send, so a request carrying only tags is rejected by validation — and any field you omit is not carried over from the existing point. Always read the point first, change the tags on the object you got back, and send it back whole.

# 1. List the points on a data source (this endpoint takes an RQL query)
GET /rest/latest/data-points?dataSourceXid=DS_BLDG_A

# 2. Read the point you intend to change
GET /rest/latest/data-points/DP_BLDG_A_AHU1_SAT

# 3. Send that same object back, with tags modified
PUT /rest/latest/data-points/DP_BLDG_A_AHU1_SAT
{
  "xid": "DP_BLDG_A_AHU1_SAT",
  "name": "Supply Air Temperature",
  "dataSourceXid": "DS_BLDG_A",
  "dataType": "NUMERIC",
  "pointLocator": { ... unchanged ... },
  "tags": {
    "site": "Building-A",
    "deviceType": "RTU",
    "floor": "2"
  }
}

Updating Many Points in One Call

Do not loop single PUTs — Mango has a bulk endpoint for this:

POST /rest/latest/data-points/bulk
{
  "action": "UPDATE",
  "requests": [
    { "xid": "DP_BLDG_A_AHU1_SAT", "body": { ... full point, new tags ... } },
    { "xid": "DP_BLDG_A_AHU1_RAT", "body": { ... full point, new tags ... } }
  ]
}

Each entry in requests takes an xid, an optional action, and a body; the top-level action and body act as defaults for every entry. The call is asynchronous — it returns a temporary resource, and you poll GET /rest/latest/data-points/bulk/{id} for progress and per-point results. See the REST API documentation for authentication and pagination details.

Tag Naming Conventions

Establish conventions before you start tagging:

ConventionGoodAvoid
CasePick one convention and hold it. Exception: Platform Manager reads site, deviceType and deviceID exactly as spelled — camelCase is required for those threeVarying case on the same key: site in one place, Site in another
SeparatorsHyphens in your own keys: point-type, asset-classSpaces or underscores: point type, point_type
ValuesConsistent format: Building-AInconsistent: Bldg A, building_a
HierarchySeparate keys: site=Campus-1, building=ACompound values: location=Campus1-BuildingA

Common Bulk Tagging Scenarios

Tag All Points on a New Data Source

After creating a data source with many points, filter by that data source in Bulk data point edit and apply site, building, and device-type tags in one operation.

Rapid Device Duplication via Export/Reimport

To duplicate a fully tagged device quickly: export the device's data source and points as JSON, remove or replace the XIDs in the exported file, change each point’s deviceName (e.g., RTU-01 to RTU-02) and any device-specific tag values such as deviceID, then reimport. device is not a stored tag — Mango derives it from Device name — so editing a device tag in the JSON changes nothing. All tags, logging settings, and point configurations carry over to the new device.

Tip

This export-remove XIDs-reimport workflow is the fastest way to stand up a new device that mirrors an existing one. Always search-and-replace XIDs, device names and device-specific tag values before reimporting to avoid overwriting the original device.

Retag After Restructuring

If you change your tagging convention (e.g., from location to site), export all points as JSON, find-and-replace the tag key, and re-import. Always back up before bulk changes.

Add a New Tag Dimension

Adding a new tag like criticality=high to selected points: filter by the relevant data sources, select the critical points, and bulk-add the tag.

Verifying Tag Changes

  • After bulk tagging, go to a dashboard that filters by the new tag and confirm the expected points appear
  • Use Bulk data point edit filtered by the new tag to verify the count matches expectations
  • Check for typos — site=Biulding-A won't match filters looking for Building-A

Troubleshooting

IssueCauseFix
Tag doesn't appear on filtered listTypo in key or valueCheck exact spelling and case in Bulk data point edit
Dashboard shows wrong pointsTag applied to incorrect pointsReview tag assignments; filter by data source first
JSON import doesn't update tagsXID mismatch or missing XIDEnsure point XIDs in JSON match existing points
REST API returns 403Insufficient permissionsUse a superadmin account or a role with data point edit permission

Summary

Bulk tag management keeps large deployments organized. Use Bulk data point edit for quick UI-based tagging, JSON export/import for reviewed batch changes, and the REST API bulk endpoint for scripted automation. Establish naming conventions early and verify tags after every bulk operation.

Get free access to all 65 Mango by Radix IoT training lessons

One short form unlocks every lesson and its video in this browser.

This form is hosted by Zoho. It loads only after you enable support cookies or choose to load it below.

We honored your browser’s Global Privacy Control signal — optional cookies are off and nothing is tracked.