May 14, 2026 - Strict validation of unit values in measurement fragments is now enforced

Change Log Platform services
, ,
1

Context

Change Type: API change
Product area: Platform services
Component: REST API
Deployed at: eu.latest.cumulocity.com, apj.cumulocity.com, jp.cumulocity.com

Technical details

Build artifact: cumulocity (2026.150.0)
Internal ID: MTM-64519

Description

As announced earlier, Cumulocity now strictly validates unit values in measurement fragments.

If a measurement fragment contains a unit value that is null or an empty string, the platform removes the unit value before persisting the measurement. The measurement itself is still stored, but without the unit.

For example, if you send a measurement with an empty unit value:

{
  "c8y_Temperature": {
    "T": {
      "value": 22.5,
      "unit": ""
    }
  }
}

The platform stores the measurement, but the unit field is not persisted and is missing in the API response. To retain the unit in the stored measurement, send a valid, non-empty value:

{
  "c8y_Temperature": {
    "T": {
      "value": 22.5,
      "unit": "°C"
    }
  }
}

This change improves data quality and consistency across the platform.