Errors and Warnings

Orange question mark icon that reads Quick Reference Guide

Error & Warning Messages

If you’ve received an error or warning message, you might be wondering what to do now. Here are some of the most common errors and warnings people see in Mapline, and what they mean.

UNABLE TO GEOCODE ROW

When uploading a dataset, you may see a red error stating, We were unable to geocode your row. Please adjust the address and try again.

This message appears when our geocoder is unable to identify your address and plot it on a map.

To fix this, open your dataset within Mapline and locate the row with a red exclamation mark next to it. Check the address in that row, make any neccessary edits, and then click the exclamation mark to re-process the row.

ADDRESS HAS CHANGED

Whenever a column containing address information is edited, an orange exclamation mark appears to the left of the row. This indicates that the address has been changed since the last time that the row was gecoded. To re-process the row and update the position on any maps, simply click the exclamation mark.

MISSING HEADERS IN YOUR DATA

This error message appears when a user pastes in a territory color spreadsheet without the required headers of Shape Name and Color.

To resolve this, add an additional row to the top of your spreadsheet and enter Shape Name as the first column’s header and “Color” as the second column’s header. If you’ve already entered these column headers and are still seeing the error message, check the spelling of your headers.

Learn how to create custom-colored territories if you need additional assistance.

UNABLE TO FIND A ROUTE BETWEEN THESE POINTS

When creating a route using Mapline Routing, you may receive the following error message: Unable to find a route between these points.

This happens most often when a location included has been plotted on a separate landmass from other locations on the route.

To fix this, create a route that does not include the disparate location. Alternatively, if the location in question was plotted inccorectly, re-geocode the location and try again.