How to import descriptive fields for visits
An option is now featured so you can import data present in your imported table; these will not be used by the optimisation engine, but will be used as descriptive data, notably at the time the results of the route plan are exported.
To use this functionality, proceed as follows: :
Associating data after export
In the My visits tab (that can be renamed depending on the terminology you have applied for visits in the My activity tab), once the file or spreadsheet has been iimported and the data sheet chosen, the field mapping step allows you to define which columns of your data will be used as constraints by TourSolver during route optimisations.
Each constraint should therefore be mapped in the second column.
Utilisation
If you do not wish to map a column with a TourSolver constraint, but use it anyway in the application as descriptive data:
- check that the check-box to the left of the column heading is checked
- put this column into correspondence with the 'Other data' item in the second column. You will notice that a number is automatically assigned to any 'Other data' item present, allowing you to import several descriptive data items into TourSolver.
In the example below, the last column is configured as a descriptive data item and will not be used during the optimisation of routes.