First Steps after Install

01 Geocode records:

To “geocode” a record means to convert its address in geographic coordinates (longitude and latitude) and save those values. The coordinates are required for all accounts, contacts and leads in order to display them on the map.

tourManager24 does this job for you by using the Salesforce standard geocoding feature.

NOTE: This option is selected by default. But before you can enjoy all functionalities of the app, please make sure you have set up geocode clean rules in your org. Assistance to set up and activate those clean rules can be found within tourManager24 installation guide and in the Salesforce success community.

tourManager24 provides also its own geocoding option. To use this option you have to request an API key and a client Id from google. Please refer to the "get API key" support page to learn how to do this. Detailed information about how to setup this geocoding option can be found in our tourManager24 installation guide.

02 Show a record on the map:

To show a record on the map simply add the tourManager24 “Show on map” button to all page layouts for accounts, contacts and leads that will be accessed by the app’s users.
 

03 Show multiple records on the map:

tourManager24 lets you display records from list views of accounts, contacts, leads, opportunities and cases on the map. For opportunities, the associated account will be mapped, for cases you can choose whether to map the associated account or contact.

To enable this option, add the “Map + object name” button (e. g. “Map account”) to the corresponding list view layout. Details on this steps can be found within tourManager24 installation guide .

FAQ

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.

 

  1. Create event for route
    One event is created for the route (Related to the saved route).
     
  2. Event for each point
    An event is created for each point on the route. For each such event, 'related to' field is the record shown on the map (the location) and the "route" custom field holds a link to the route (you need to add the "route" custom field to the event's page layout).

In the options page, change "Max find nearby distance" to 999.

I want to perform a find nearby search with a filter on accounts, but the filter page doesn't have a section for filtering account fields.
Please check, whether you selected the checkbox next to accounts in the "Search parameters" panel.
(This panel appears left from the panel for setting filter criteria.)

 

This is mostly caused by a record’s address that has not been geocoded, yet, or could not be geocoded. You can check the geocoding status fields for this record (see above "How do I know what is the geocoding status of a record?").

 

You get an overview on the status of all records within the geocode tab. Besides that, you can run a report to get more details on which records could not be geocoded and why.

 

Furthermore, four fields contain the results of the geocoding process for each record: Latitude, longitude, geocoding status and geocoding error. If you put those fields on page layouts they provide you information on the status of a record. We recommend you to set those fields to read-only on the page layouts.

The different values for geocoding status are:

  • Needs geocoding
    The record has never been geocoded, or its address has been changed since the last run of the geocoding process
  • Geocoded:
    Address was successfully geocoded, the result is saved in the fields latitude and longitude.
  • Address not complete:
    the address street and/or city fields are empty
  • Cannot be geocoded:
    Geocoding server could not geocode this address. For example, the address is a post office box, or it does not exist. Check the geocoding error field for more details.

I closed the geocoding tab, or logged out of Salesforce, while the geocoding process was running. Has any data been lost?
No. The geocoding will work in the background, no matter whether you leave the tab or log out of Salesforce.

 

Error message: 'Problem accessing geocoding server. There might be a communication problem or the daily limit for geocoding requests has been reached. Please try again later'.
This usually occurs when the daily limit of geocoding requests per day has been reached (100,000 per day ). Please restart the geocoding process again after a few hours, sometimes it is necessary to wait until the following day.