If you need to assign a Task to a specific Driver during CSV import, you can use Task Pre-assignment. This can be done by including one of the following identifiers in your import file:

These fields can contain both text, numbers, and special characters.

You can use any of these identifiers to map Tasks to exact Drivers, and here is how to map them:

You can either use the mapping feature to map the corresponding values or use the eLogii default import naming convention.

Whichever one you choose to use, eLogii will behave the same, and it will force-assign Tasks to the associated Driver immediately on import.

This can be prevented by enabling the Do not automatically pre-assign imported tasks to routes where driver is specified for the task option that can be found in Configuration ⇒ Imports.

Click Save to apply changes.

To associate a Task with a particular Team, you need to populate the teams field in the Task CSV file with the exact name of your Team. If you have multiple teams you wish to associate a Task with, separate them with a comma. For example, if you have 2 teams - Team 1 and Team 2, and for each Task you wish to associate with both teams, you would specify it like this: Team 1, Team 2.

Task and Zone association is done automatically, and it depends on the Task's coordinates and whether its latitude and longitude fall under the specific Zone.

Customer and Task association on Task import can be done by including one of the following identifiers in your Task import file:

When uploading Tasks via CSV, you must include both the Customer UID and the Location UID. These two IDs serve different purposes: the Customer UID, taken from the customer’s profile in eLogii, goes into the customerUID field to link the Task to the correct customer and apply any customer-specific defaults. The Location UID, on the other hand, should be entered in the pickupUID or dropoffUID fields to specify where the Task should be carried out.

Alternatively, if you wish to use your references, you would need to specify those for both the Customer and the Customer's location. The Customer reference would be customerUID, and for the Customer location reference, it should be either the pickupReference or dropoffReference, depending on whether the Driver is picking up something from the customer location or delivering something.

You can use any of these identifiers to map Tasks to exact Customers and their locations, and here is how to map them:

No geocoding will be required in either case, because the Customer locations are already stored in eLogii, so there is no need for the system to retrieve the coordinates of the locations again.

Depot UIDs and references are used for the Task and Depot association. Either one of these can be used to connect Tasks with the appropriate Depot - whether it's a pickup or a delivery location.

The Depot UID follows a fixed naming convention, and it's a string that always starts with DEP- and is followed by a string of 8 characters (e.g., DEP-ABC12345).