Cumulocity IoT Feedback Portal
Add new feedback Subscribe
Status Future consideration
Workspace Cumulocity IoT Device Mgmt. & Connectivity
Categories Cloud Fieldbus
Created by Guest
Created on Oct 2, 2020

RELATED FEEDBACK

Cloud Fieldbus UI: Validation of fragment / series names

Our Customer TT-Control has following issue:

Incident: 5428979

Basically the problem of TTC is that their customers uses spaces when they define device types in holding registers.

The problem results in empty reports.

TTC asks if it is possible to add a validation for the correct naming in the frontend?

  • Attach files
  • oana velicu
    Reply
    |     Apr 11, 2022

    Hi Nikolaus, pls confirm with Korbinian. I assume your assumption is correct. :)

    kr Oana

  • Admin
    Nikolaus Neuerburg
    Reply
    |     Oct 15, 2020

    Hi Dejvid,

    thanks for your feedback.

    Can I ask you to confirm that the problem is that if you map a register (holding or input) to a measurement we do not enforce the naming conventions (https://cumulocity.com/guides/concepts/domain-model/#naming-conventions-of-fragments) for measurements and thus allowing whitespace in fragment and series name. This leads to the resulting measurement not being displayable in data point graphs (in addition to other limitation).