When you write templates that access this table, follow these requirements:

1. Specify the Symbolic Name for the table version to use:

   Copy

   TableID = Route-1.0

2. Specify an Intent that this table supports:

   • Retrieve
   • Create
   • Update
   • CreateOrUpdate
   • Delete

3. 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.

4. Retrieve templates: This table requires the use of a fetcher. The following fetchers are available and are listed from most efficient to least:
   1. Id (Equals/In)
      Copy

      [Filter]
      Id(ExtId) = Equals(Id1)   # You can filter on literals or on variables from the [User] or [Calculated] sections.

      Copy

      [Filter]
      Id(ExtId) = In(["Id1","Id2","Id3"])

   2. StartTime (Between/GreaterThan)

      You can improve the performance of the StartTime fetcher by adding one or more of the optional filter parameters.

      Copy

      [Filter]
      StartTime = GreaterThan(StartTime)      # You can use either a GreaterThan or Between function
                                              # such as Between(TimeStart,TimeEnd)
      # Optional filter parameters:
      
      # TerritoryId(ExtId)=  In("Id1", "Id2", Id3")          # Or use Telogis Id: TerritoryId = Equals("123456...")
      # DriverId(ExternalIdName) = In("Id1", "Id2", Id3")    # Or use Telogis Id: DriverId = Equals("123456...")
      # UnitId(ExternalIdName) = In("Id1", "Id2", Id3")      # Or use Telogis Id: UnitId = Equals("123456...")  
      # LastUpdateTime = GreaterThan ("UpdateStartTime")     # You can use either a GreaterThan or Between function
                                                             # such as Between(StartLastUpdateTime, EndLastUpdateTime)

This table supports the following option, which can be set in the [TableOptions] section.

• DriverUnitSync - For Route table input templates, determines the way in which routes, drivers, and units are assigned. These settings only apply if you provide either the UnitId or the DriverId. If you provide both, then the values provided will be used regardless of this setting.

  Value	Description
  Never (default)	TDE only sets the values provided within the input data and does not update the route with related values from the Unit or Driver tables.
  Always	This setting affects the following scenarios: If you provide the UnitId and not the DriverId: The driver that is currently assigned to the unit will be automatically assigned to the route, or the route's driver will be unassigned if there is no driver assigned to the unit. In other words, the value for Route.DriverId will always be set to the value of Unit.DriverId. If you provide the DriverId and not the UnitId: The unit that is currently assigned to the driver will be automatically assigned to the route, or the route's unit will be unassigned if there is no unit assigned to the driver. In other words, the value for Route.UnitId will always be set to the value of Driver.UnitId.
  AssignOnly	This setting affects the following scenarios: If you provide the UnitId and not the DriverId: The driver that is currently assigned to the unit will be automatically assigned to the route if a driver is assigned to the unit. In other words, the value for Route.DriverId will only be set to the value of Unit.DriverId if a driver is assigned to the unit. If you provide the DriverId and not the UnitId: The unit that is currently assigned to the driver will be automatically assigned to the route if a unit is assigned to the driver. In other words, the value for Route.UnitId will only be set to the value of Driver.UnitId if a unit is assigned to the driver.

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.

Note
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.

Additional columns: