...
Name | Description | Data type |
|---|---|---|
Production unit id | The internal id of the production unit | String |
Production unit number | Production unit as shown in Qarma | String |
Production unit name | Production unit as shown in Qarma | String |
Address | Address of production unit (is empty if custom fields are enabled) | List of strings |
Contact person | Empty if custom fields are enabled | String |
Groups | List of Qarma groups (relating to access control) | List of strings |
Users | List of Qarma users (registered users in Qarma for this production unit) Will be added later | |
Upstream production units | List of production unit internal ids that are linked as upstream. | List of ids |
Downstream production units | List of production unit internal ids that are linked as downstream. | List of ids |
Latitude | Location added on the production unit | Float |
Longitude | Location added on the production unit | Float |
Status | Status string of the production unit. | String |
Is deleted? | False if the production has not been deleted, true if it has been deleted | Boolean |
Custom fields |
Users - a list of structs with full name and email, is a contact person
Groups - group names as JSON array
Custom field definition names (column headers should use the key) - field, keep hierarchical order from custom fields definitions if possible
We don’t show custom field definition types
Show only visible (not hidden) custom field values