Note
The Import Jobs and Import Routes tools do not support the Internet Explorer browser. Some advanced features, such as driver shifts and multi-day routes, are also unsupported in import files. Some of these features can, however, be applied through the user interface after you have imported your jobs or routes. The import process can be used to create markers and routes, butnot to update existing markers and routes.
Note
When you create breaks on a route, or assign jobs or depots to a route, there are limitations that you must consider regarding the maximum number that can be used on a single route. For more information about these limitations, see the Route and Job Limitations page.
The Job Import and Route Import tools are useful when you want to create a large number of one-off jobs or one-off routes quickly using import files, rather than doing this manually, as described on the Creating Jobs and Creating Routes pages. Using these tools you can also import both routes and jobs at the same time, in the same file. You can also use the similar legacy Job and Route import tools that are accessed from the Jobs & Routes section of the main menu, by clicking either the Route Import or Job Import links.
Tip
For information about avoiding duplication of your markers when importing jobs and routes, read Avoiding Duplicate Markers When Importing.
To import a jobs and routes file into Dispatch or Response:
-
Select a territory from the territory drop-down menu in the upper right corner of the screen.
Note
A territory consists of customers, depots, drivers, and vehicles. Only territories that have previously been configured under Jobs & Routes > Territories can be selected in Dispatch or Verizon Connect® Response™.
-
Click the Import Jobs button
in the toolbar above the Jobs List, or the Import Routes button
Note
The Import Jobs or Import Routes dialog boxes display links to example job and route import files that contain the required columns. You can use these files as a guide when creating your own import files.
-
Select a file to import using one of the following methods:
-
Click the Choose File button to open File Explorer, find the .csv, .xls, or .xlsx file, select it, and then click Open.
-
Open File Explorer (Start+E), find the .csv, .xls, or .xlsx file, and then drag the file into the Import Jobs or Import Routes dialog box.
Note
The import file should follow these criteria:
-
Contain columns of data as described in the Job Import Supported Columns section or the Route Import Supported Columns section. If the columns in the file do not match the supported columns exactly, the Configure Import dialog box opens. The Configure Import dialog box helps you to map your existing columns to the supported columns. See Using the Configure Import Tool below for more information on using this tool.
-
Be no larger than 10MB in size.
-
Contain no more than 10,000 rows of data. If your file exceeds these size restrictions, you can split it into smaller files and import these individually.
The import file is validated and the Validation Complete dialog box opens. If the import file contains errors and cannot be imported, the Validation Complete dialog box lists the errors that must be fixed. To fix the errors, open the .csv, .xls, or .xlsx file, edit the file, and then save it. To re-upload the edited file click the Re-upload File button.
If the import file is free of errors, the Validation Complete dialog box displays an import summary.
Note
If the chosen file contains unrecognized or new columns that have not been mapped, the Configure Import dialog box opens. The Configure Import dialog box helps you to map your existing columns to the supported columns. See Using the Configure Import Tool below for more information on using this tool.
-
-
-
Click the Import button to import the jobs or routes into the selected territory. After a successful import, the following message box is displayed:
The jobs or routes are listed in the Jobs List or the Routes List.
If an imported job or route file includes one or more columns that are not supported (see the Job Import Supported Columns table or the Route Import Supported Columns table), the Configure Import dialog box opens when you try to import the file.
|
1: |
Examples of the data that is stored in the column. This helps you to decide if the mapping tool has mapped the column to the correct supported column. |
|
2: |
The name of the column in the import file. |
|
3: |
Indicates that there is at least one imported column that the mapping tool was unable to map to a supported column. |
|
4: |
The supported column that the import tool has matched the imported column to. If this is wrong and you want to change it, see Ignoring or Re-Mapping Columns. |
|
5: |
Indicates that the mapping tool was unable to map the imported column to a supported column. See Mapping Columns That Were Not Mapped. |
You can map imported columns to supported columns, if the mapping tool was unable to do this. The Configure Import dialog box displays the following message if there are unmapped columns:
To map an imported column to a supported column:
-
On the Configure Import dialog box, find the column that needs to be mapped.
-
Click the down arrow
to expand the drop-down menu:
-
From the drop-down menu, do one of the following:
-
To ignore a column: Select “Ignore This Column”. Choose this option if you do not want this column to be imported. Click Next.
-
To map a column to a custom field: Select “Map to Custom Property”. Choose this option if you want to map the column to a custom job field. Enter the name of the custom field in the Custom field text box, and then click Add. The name of the custom field has “job.custom.” added to the front of it. For example, “route_driver” becomes “job.custom.route_driver”. Click Next.
-
To map a column to a supported column: Select a supported column from the list in the drop-down menu. The supported columns that best match the imported column are listed in the Suggestions section. If you choose a supported column that is already in use, the imported column that was mapped to that supported column becomes unmapped, and you will need to map it. Click Next.
-
-
Click the Import button on the Validation Complete dialog box to complete the import.
You can ignore a column that you do not want to import, or re-map an imported column to a custom field or supported column.
To ignore or re-map a column:
-
On the Configure Import dialog box, click the X beside the name of the supported column.
-
Click the down arrow
-
From the drop-down menu, do one of the following:
-
To ignore a column: Select “Ignore This Column”. Choose this option if you do not want this column to be imported. Click the Ignore and Continue button.
-
To re-map a column to a custom field: Select “Map to Custom Property”. Choose this option if you want to map the column to a custom job field. Enter the name of the custom field in the Custom field text box, and then click Add. The name of the custom field has “job.custom.” added to the front of it. For example, “route_driver” becomes “job.custom.route_driver”. Click Next.
-
To re-map a column to a supported column: Select a supported column from the list in the drop-down menu. The supported columns that best match the imported column are listed in the Suggestions section. If you choose a supported column that is already in use, the imported column that was mapped to that supported column becomes unmapped, and you will need to re-map it. Click Next.
-
-
Click the Import button on the Validation Complete dialog box to complete the import.
Job import files should contain the following columns of information about individual jobs. Not all of these columns are mandatory, but when they are used, the column names in your files must be the same as those shown below. Note that you can import both jobs and routes in the same file, as long as the required fields for both jobs and routes are present in the file.
Note
Only the 'job.name' and a job location, such as 'job.address', are required for unassigned jobs. Assigned jobs require a job name and location, and a specified route driver or vehicle. An ‘assigned’ job is a job that has a route with a particular vehicle or driver that you want to use, or a specific route date. If these details are not provided, the ‘best’ driver, vehicle, time, and date for each job is selected by the routing engine. The import process can be used to create markers and routes, butnot to update existing markers and routes.
|
Field |
Purpose |
Example |
|---|---|---|
|
job.name |
The name of the job.This field is required. |
Smith Steel Pickup |
|
job.id |
The unique ID of the job. Stored as an External ID with a System Name value of 'default'. Used to identify and prevent duplicate imports. |
466c4b9d-2204-400c-ac72-b0bb1c0ec9c6 |
|
job.address |
The full street address where this job occurs. Must include a street number.Required if job.lat and job.lon together, or job.lat_lon alone, or a full component address including street_number, street_name, city, state, and post_code are not provided. |
20 Enterprise, Aliso Viejo, USA |
|
job.street_number |
The street number of the address where this job occurs. Required if job.lat and job.lon together, or job.lat_lon alone, or job.address alone are not provided. |
20 |
|
job.street_name |
The name of the street where this job occurs. Required if job.lat and job.lon together, or job.lat_lon alone, or job.address alone are not provided. |
Enterprise |
|
job.city |
The name of the city that this job occurs. Required if job.lat and job.lon together, or job.lat_lon alone, or job.address alone are not provided. |
Aliso Viejo |
|
job.state |
The name of the state where this job occurs. Required if job.lat and job.lon together, or job.lat_lon alone, or job.address alone are not provided. |
CA |
|
job.post_code |
Optional. The postal code of the address where this job occurs. Can only be provided if job.street_name and job.street_number have also been provided. |
92656 |
|
job.lat |
The latitude coordinate of the job. If used, a job.lon value must also be supplied. Required if job.lat_lon alone, or job.address alone, or a full component address including street_number, street_name, city, state, and post_code are not provided. |
33.584297 |
|
job.lon |
The longitude coordinate of the job. If used, a job.lat value must also be supplied. Required if job.lat_lon alone, or job.address alone, or a full component address including street_number, street_name, city, state, and post_code are not provided. |
-117.731632 |
|
job.lat_lon |
The latitude and longitude coordinates of the job. Required if job.address, or a full component address including street_number, street_name, city, state, and post_code are not provided. |
33.584297, -117.731632 |
|
job.time_on_site |
The length of time that will be spent at the customer site servicing this job. Enter a duration value between 30 seconds (minimum) and 23 hours and 59 minutes (maximum) using hh:mm or hh:mm:ss formatting. Jobs with a job type value of 'Depot' cannot have a time on site value specified. |
00:30:00 |
|
job.required_driver |
The driver who is required to complete the job. This driver will be used for the job unless they are otherwise unavailable (for example, if they are not working on the day of the job, or if the job is scheduled to occur outside their shift hours) or if the driver is forbidden. If importing only a driver and not a vehicle, the driver must have a base marker. |
Steve McGibbon |
|
job.forbidden_drivers |
The names of the drivers that are forbidden from completing this job. Accepted as a comma-delimited list. |
John Smith, Chen Ho |
|
job.type |
The job type of the job. These are created from the Jobs & Routes Menu > Job Types screen (see Job Types). Only 'Stop' and 'Depot' job types are supported. 'Depot' job types are optional in your import files when importing assigned jobs: If depots are not provided, they are added automatically. If 'Depot' job types are used, job.sequence_number values are required. |
Stop |
|
job.earliest_date |
The earliest date that the driver can arrive at the customer site to service this job, in mm/dd/yyyy or dd/mm/yyyy format, depending on your platform settings (click your account name in the upper right corner of the platform screen, and then select Settings > User > Region). The job is not serviced before this date. The date provided for 'earliest date' cannot be after 'latest date'. Jobs with a job type value of 'Depot' cannot have an earliest date value specified. Date components can be separated by '/', '-', or '.'. |
04/18/2019 |
|
job.latest_date |
The latest date that the driver can arrive at the customer site to service this job, in mm/dd/yyyy or dd/mm/yyyy format, depending on your platform settings (click your account name in the upper right corner of the platform screen, and then select Settings > User > Region). The job is not serviced after this date. The date provided for 'latest date' cannot be before 'earliest date'. Jobs with a job type value of 'Depot' cannot have a latest date value specified. Date components can be separated by '/', '-', or '.'. |
04/22/2019 |
|
job.time_window_start |
The earliest time that the driver can arrive at the job location. Accepted in 24-hourhh:mmformat. The time provided for 'time window start' cannot be after 'time window end'. Jobs with a job type value of 'Depot' cannot have a time window start value specified. |
11:00 |
|
job.time_window2_start |
The earliest time that the driver can arrive at the job location within the second delivery time window. The second time window is off by default, and should only be used if the first time window is already set using job.time_window_start and job.time_window_end. Accepted in 24-hour hh:mm format. The time provided for 'time_window2_start' cannot be after 'time_window2_end'. Jobs with a job type value of 'Depot' cannot have a time window start value specified. |
14:30 |
|
job.time_window_end |
The latest time that the driver can arrive at the job location. Accepted in 24-hourhh:mmformat. The time provided for 'time window end' cannot be before 'time window start'. Jobs with a job type value of 'Depot' cannot have a time window end value specified. |
16:30 |
|
job.time_window2_end |
The latest time that the driver can arrive at the job location within the second delivery time window. The second time window is off by default, and should only be used if the first time window is already set using job.time_window_start and job.time_window_end. Accepted in 24-hour hh:mm format. The time provided for 'time_window2_end' cannot be before 'time_window2_start'. Jobs with a job type value of 'Depot' cannot have a time window start value specified. |
20:00 |
|
job.allowed_days_of_week |
The days of the week that this job can be serviced. Accepted as a comma-delimited list with values of 'mon', 'monday', 'tue', 'tuesday', 'wed', 'wednesday', 'thu', 'thursday', 'fri', 'friday', 'sat', 'saturday', 'sun', 'sunday', 'weekdays', or 'all'. These values are case-sensitive. Jobs with a job type value of 'Depot' cannot have allowed days values specified. |
monday,tuesday,wednesday |
|
job.priority |
The priority of the job. Accepted values are 'Lowest', 'Low', 'Normal', 'High', and 'Highest'. Higher priority jobs are typically routed ahead of lower priority jobs when building routes. Jobs with a job type value of 'Depot' cannot have a priority value specified. |
High |
|
job.tags |
Tags that have been attached to the job. These tags must already exist: they cannot be created during import (see How to Define a New Tag). Accepted as a comma-delimited list. Jobs with a job type value of 'Depot' cannot have a tags value specified. |
Heavy goods |
|
job.required_driver_tags |
Tags that specify the driver skills or properties that must be present to complete the job. These tags must already exist: they cannot be created during import (see How to Define a New Tag). Accepted as a comma-delimited list.Jobs with a job type value of 'Depot' cannot have a driver requires tags value specified. |
CraneOperator |
|
job.required_pre_job_depot_tags |
Tags that specify additional depots that the driver needs to visit before a job; for example for a pick-up. |
Frozen |
|
job.required_post_job_depot_tags |
Tags that specify additional depots that the driver needs to visit after a job; for example for a drop-off. |
Frozen |
|
job.required_vehicle_tags |
Tags that specify the vehicle capabilities or properties needed to complete the job, such as refrigeration, a boom arm, or PTO connections. These tags must already exist: they cannot be created during import (see How to Define a New Tag). Accepted as a comma-delimited list. Jobs with a job type value of 'Depot' cannot have a vehicle requires tags value specified. |
PTO |
|
job.notes |
Free-form notes that have been attached to the job. Like codes, these are typically used for filtering jobs.Jobs with a job type value of 'Depot' cannot have a notes value specified. |
Use side entrance |
|
job.code |
An arbitrary code associated with the job. These codes are typically used for filtering operations, together with tags. Jobs with a job type value of 'Depot' cannot have a code value specified. |
3256 |
|
job.load_type |
The loading type of the job: either 'delivery' or 'pickup'. |
delivery |
|
job.loads.[metric] |
The number of units of a given load type will be delivered or picked up at the customer site as part of this job, for example job.loads.pallets or job.loads.cases. |
10 |
|
job.custom.[custom property name] |
Any custom properties associated with the imported job, for example job.custom.alarm_code or job.custom.lawn_size. These properties are shown on the Jobs List and can be used to sort the grid. |
2987 |
|
job.location_name |
The name of the marker at which the job takes place. If no marker with this name is found, a new marker is created at the address or location of the job. |
Enterprise Marker |
|
job.location_id |
The unique ID of the marker at which the job takes place. Stored either as an External ID with a System Name value of 'default' or, if you have previously configured markers in your account, as an inline marker ID (shown under the 'ID' column of the Markers screen grid). Used to identify and prevent duplicate imports. |
2197jftba-ea2a-679d-b9c9-148d85e44670 or 7296330 |
|
job.description |
An arbitrary, but typically descriptive, name used to represent the job such as the job address or the marker name. |
20 Enterprise Morning Pick-up (Short Notice) |
Route import files should contain the following columns of information about individual routes. Not all of these columns are mandatory, but when they are used, the column names in your files must be the same as those shown below. Note that you can import both jobs and routes in the same file, as long as the required fields for both jobs and routes are present in the file. If you import only routes without jobs, the imported routes will be empty.
|
Field |
Purpose |
Example |
|---|---|---|
|
route.name |
The name of the route. Optional, and blank if not supplied. |
McGibbon Morning Route |
|
route.driver |
The driver assigned to complete this route of the job. Optional unless route.date has been supplied and route.vehicle has not been supplied. |
Steve McGibbon |
|
route.vehicle |
The vehicle that will be used to service this route. If importing only a vehicle and not a driver, the vehicle must have a base marker. Optional unless route.date has been supplied and route.driver has not been supplied. |
Truck 10 |
|
route.date |
The date that this route will begin, in mm/dd/yyyy or dd/mm/yyyy format, depending on your platform settings (click your account name in the upper right corner of the platform screen, and then select Settings > User > Region). Either route.driver or route.vehicle must be provided if route.date is used. |
04/22/2019 |
|
route.id |
The unique ID of the route. Stored as an External ID with a System Name value of 'default'. Used to identify and prevent duplicate imports. |
217ecdba-ea2a-438d-b9c9-148489e40670 |
|
job.sequence_number |
This is an optional job value that can be used when importing both jobs and a route in the same file. The order of this job in the route, starting from 0. If not included, the routing optimizer selects the optimal order of your jobs in a route. If a value is specified for any job in an import file, this value must be supplied for all other jobs. If importing jobs with a job.type value of 'Depot', job.sequence_numbers must be used, and depots must be used as the first and last jobs in the specified sequence. |
0 |
Comments
0 comments
Please sign in to leave a comment.