Objects and their data are the core payload of every project. Objects represent real-world entities (machines, sensors, sites). Data records contain their measurements and events.
Objects are rows in generated object structures (OTs). They form hierarchies via parent/child relationships and can reference each other.
Objects start from "root". Two view modes:
| Tab | Content |
|---|---|
| Children | Child objects (according to child OTs) |
| Data | View/edit data if a data table is assigned |
| Data export/import | Bulk operations on object data |
| Role access | Per-object role permissions (if access table is enabled on OT) |
| History | Change log (if history table is enabled on OT) |
| Data table assignment | Select which DT this object uses |
| Copy | Duplicate the object |
Navigate to the parent → Add object. Fill columns defined by the OT.
Optional settings:
DATA_ALLOWED on OT)PRIVATE_ALLOWED on OT)SETTINGS_ALLOWED on OT)Changing an object's assigned data table requires deleting the object's data in the previous table first. Data from other objects in that table is not affected.
Data are rows in a generated data table, always belonging to a specific object.
DISCONNECT_VALUE/DISCONNECT_TIMEOUT configured)The GUI supports manual add/edit/delete of individual rows. For bulk operations use the JSON-RPC API.
| Permission | Allows |
|---|---|
DATA_ANALYST |
Read data |
DATA_SOURCE |
Insert data (and read last value) |
DATA_MANAGER |
Edit/delete data (and read last value) |
No per-row permissions or change history are stored for data (unlike objects).
OTs flagged with ENUM are hidden in the default browse view and cannot have data. They serve as lookup tables — their objects are referenced by OBJECT_REFERENCE or ENUM_REFERENCE columns in other OTs or DTs.
If an OT has PRIVATE_ALLOWED:
PRIVATE_OBJECTS_ENTRUSTED on the project can see all private objectsFor non-private objects with access control enabled:
For private objects:
PRIVATE_OBJECTS_ENTRUSTED)See Permissions for the full cascade.