The translation table, tblXImportTranslations, can also be found in X Dispatch under X Stream > Route Mappings. It is used for looking up a RouteID based on import data. Usually, this functionality is used to assign a RouteID to imported route stops based on a Route and Stop ID set within the import file.

Translation Table Structure

• PKID: automatically generated
• CustID: Customer
• TranslationType: Standard Route Translation (or ID = 1)
• Reference1: First lookup (CustRouteID)
• Reference2: Secondary lookup (CustSecondaryLookup)
• Translation: RouteID to use when the lookups match

Make sure that RouteID is not specified in the configuration file and that CustRouteID (and optionally CustSecondaryLookup) are filled in correctly when using route translation.

• CustRouteID maps to Reference1 in the translation table, tblXImportTranslations.
• CustSecondaryLookup maps to Reference2 in the translation table, tblXImportTranslations.

How the translation is determined

• Find the translation where the value of CustRouteID is equal to Reference1 in the translation table, and CustSecondaryLookup is equal to Reference2.
• If CustSecondaryLookup is not specified, or there are no matches for the specified CustRouteIDm and CustSecondaryLookup, then the translation falls back to a match on CustRouteID only (tblXImportTranslations.Reference1).
• If there are no matches for CustRouteID and CustSecondaryLookup, the translation will fall back based on the Customer ID.

Example

tblXImportTranslations

Example Translations