Use the Fleet table to manage fleets for the organization of units.
Fleets have two types:
This topic contains the following sections:
You can manage the vehicles assigned to a fleet by using the Unit table.
When you Create a fleet, Name is the only required value. On creation, all fleets are private and visible only to the creator. To make a fleet visible to all users, set IsPublic=True.
When you write templates that access the Fleet table, follow these requirements:
Specify the Symbolic Name for the table version to use:
TableID = Fleet-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.
|(primary key) The ID of the fleet.
|(Telogis key) The name of the fleet.
|Indicates if the fleet is public or private. Public fleets are available to all users, while private fleets are available only to their owner.
|Free form notes about the fleet.
|(read-only) Indicates if the fleet is a hierarchy fleet. Hierarchy fleets can only be edited by updating the hierarchy.
|A set of unit IDs in the fleet. Updates must include the full set of desired IDs.
|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].