The Mapsimise SugarCRM connector offers the following functionality:

  • Map any module that has latitude/longitude fields, including custom modules. Note that the out-of-the-box latitude/longitude fields in Sugar are text fields and are unsuitable for use with Mapsimise. See the article: Preparing your SugarCRM Modules for Geocoding
  • Use bulk geocoding to geocode your records directly in CRM.
  • Create Target Lists from Mapsimise after geospatially filtering SugarCRM records on a map.


Users and Authorisation

There are two ways to authorise with SugarCRM via Mapsimise: with per-user credentials or by using shared credentials.

If you supply shared credentials on the SugarCRM connector, all Mapsimise users will use those credentials to read and write data from/to SugarCRM. You may wish to do this by setting up a “service” user in SugarCRM specially for Mapsimise, with a limited permission set only for the objects that you want to map.

Generally, we would recommend per-user authorisation where each Mapsimise user has their own user account on SugarCRM. To do this, leave the Shared Credentials on the SugarCRM connector unset. When each Mapsimise user loads a map that has a layer that uses the SugarCRM connector, they will be prompted to log in to SugarCRM with their own user account.


Geocoding Data

See also: Bulk Geocoding and Updating of Records via Live Connectors.

To geocode records in your SugarCRM system, you should provide Service Credentials on the connector and then use Bulk Geocoding via the Geocoding Rules for your SugarCRM connector.

Please see this article for information on setting up your SugarCRM modules for geocoding.

The user account supplied for the Service Credentials on your SugarCRM connector should have read/write permissions on all the entities you need to geocode. You will not be able to use the Bulk Geocoding functionality until  Credentials have been supplied.