Other than using Bing, you can easily integrate other geo-location sources. One of the most enterprise level solution is of course Esri Maps. They have a very good solution for mapping. They can also be pricy, so if you are looking for a solution on the cheap, and are not afraid of doing very little coding, read on.
Google Maps provides a very robust mapping API. You can find more details HERE.
To integrate this into your existing CRM, you will use an iFrame, and a custom HTML web resource. Your HTML will include a div tag with an id of “geolocation”. You can use another id, we’re using “geolocation” in the context of this example. Basically, your div will look like so:
<div id="geolocation" style="width: 800px; height: 500px;"></div>
Define the style width and height as needed to render properly within the iFrame at a standard screen resolution set at the enterprise level.
Pass the context to the iFrame, so you can retrieve the address fields. You will use these to build the address string you pass to retrieve the longitude and latitude.
With the new v.3 of the maps API, you do not need a API Key anymore, which makes it a lot easier to move your solution between various environments, and to have the solution internal only (no IFD).
When calling the API, if your CRM is set to use HTTPS, use the HTTPS Google API URL, otherwise use the HTTP address.
Add in the header of your HTML web resource the reference to the JS library:
<script src="http://maps.googleapis.com/maps/api/js?v=3.exp&sensor=false"></script>
In this example I am using HTTP.
In your HTML web resource, first function you want to call on page load is a function that takes the value of the address fields, and concatenates it all into a string. It will be along the lines of:
var _address = street + city + province + country + postalCode;
check and use only the fields where you have a value populated.
Once you have this address as a string, pass it to the first function that converts the address into latitude and longitude. This will look as follows:
ParseAddress: function(address) {
var url = "http://maps.googleapis.com/maps/api/geocode/json?" +
"address=" + address +
"&sensor=false"
var xhr = base.createCORSRequest(‘GET’, url);
if (!xhr) {
alert(‘CORS not supported’);
return;
}
// Response handlers.
xhr.onload = function () {
var text = xhr.responseText;
var _start = text.indexOf("\"location\" :") + 12;
var _location = text.substring(_start, text.indexOf("}", _start) + 1);
geoCode.Initialize(_location);
};
xhr.onerror = function () {
$("#message-area").append("Woops, there was an error retrieving server data.");
};
xhr.send();
},
This example is using CORS. CORS stands for “Cross-Origin Resource Sharing”, and for more details on CORS see the W3C documentation HERE.
This function makes a call to the Google API and on successful retrieval of data, calls another function called Initialize, passing the trimmed returned string that includes the location lat and lng.
The Initialize function takes this location, builds the map representation, sets the zoom on it, and drops a pin at the location provided by the coordinates:
Initialize: function (_location) {
var jsonData = $.parseJSON(_location);
var _bGeoLocation = new Array();
_bGeoLocation = jsonData;
var myOptions = {
zoom: 16,
center: new google.maps.LatLng(_bGeoLocation .lat, _bGeoLocation .lng),
mapTypeId: google.maps.MapTypeId.ROADMAP
}
// Draw the map
var mapObject = new google.maps.Map(document.getElementById(“geolocation”), myOptions);
// Place the marker
new google.maps.Marker({ map: mapObject, position: userLatLng });
}
Et voila, now you have a map with a pin on it pointing to the record’s address.
Enjoy!
