The Team table allows you to manage teams for the organization of drivers.
Teams have two types:
This topic contains the following sections:
You can manage the drivers assigned to a team by using the Driver table.
When you write templates that access this table, follow these requirements:
Specify the Symbolic Name for the table version to use:
TableID = Team-1.0
Specify an Intent that this table supports:
Input templates: In your [Output] section, be sure to map an input value to every table column that is flagged as being a primary key or required.
This list includes each column's name, which you use in expressions to retrieve or create data, and data type, which defines how the data is retrieved and set.
|If a column of data type Id is a primary key OR if it refers to other tables (Id <OtherTable>), then you can map it to an external key or, in some cases, a Telogis key.|
|Id||Id||(primary key) The ID of the team.|
|Name||Text||(Telogis key) The name of the team.|
|IsPublic||BoolType||Indicates if the team is public or private. Public teams are available to all users, while private teams are available to only their owner.|
|Notes||Text||Free form notes about the team.|
|IsHierarchy||BoolType||(read-only) Indicates if the team is a hierarchy team. Hierarchy team can only be edited by updating the hierarchy.|
|DriverIds||Set<Id<Driver>>||A set of driver IDs in the team. Updates must include the full set of desired IDs.|
|Custom.name||Text||Specifies a user-defined custom column name to store additional information in the table. If the column name contains non-alphanumeric characters, enclose the value in brackets, for example Custom.[Special column].|