Summit 7 Team Blogs

Integrating SharePoint and Bing Maps

By far one of the most simple jQuery demos I show during one of my sessions that also seems to get the best reaction is a demo where I show how quickly you can integrate SharePoint and Bing Maps. Using jQuery you can easily make an address from a SharePoint list appear in Bing Maps using the Bing Maps API.


If more applications were named using onomatopoeia what would their names be? I’m thinking “Thud” would be the next Google social application…  Anyway! We will be integrating SharePoint with Bing Maps. The first thing you should do is get a Maps Developer Account so you can get a Bing Maps Key. You will need this in order to write code and use the API (no, you can’t use mine).

Next, take a look at the Bing Maps AJAX Control SDK. Specifically we will be looking at the REST Search API. We are going to take the HTML and script for the “Filed a location by query” example and massage it to work for our purposes. Basically, we are going to strip out all the HTML and then modify the “findLocation” function to work with an address from a SharePoint List using a bit of… yep… you guessed it jQuery.

When all is said and done we end up with the following Script:

   1:  <script type="text/javascript" src="../SiteAssets/jquery.min.js"></script>
   2:  <script type="text/javascript"
   3:      src=""></script>
   5:  <script type="text/javascript">
   7:      jQuery(document).ready(function($) {
   8:          getMap();
   9:          //execute the findLocatin function on page load
  10:          findLocation();
  11:      });
  13:      var map = null;
  14:      var query;
  16:      function getMap()
  17:      {
  18:          map = new Microsoft.Maps.Map(document.getElementById('myMap'),
  19:          {credentials: '<GET YOUR OWN CREDENTIALS>'});
  20:      }
  22:      function findLocation()
  23:      {
  24:          query=    $("input[title='Address']").val() + " " +
  25:                  $("input[title='City']").val() + " " +
  26:                  $("input[title='State']").val() + " " +
  27:                  $("input[title='Zip']").val();
  29:          map.getCredentials(callSearchService);
  30:      }
  32:      function callSearchService(credentials)
  33:      {
  34:          var searchRequest = '' +
  35:              query + '?output=json&jsonp=searchServiceCallback&key=' + credentials;
  36:          var mapscript = document.createElement('script');
  37:          mapscript.type = 'text/javascript';
  38:          mapscript.src = searchRequest;
  39:          document.getElementById('myMap').appendChild(mapscript)
  40:      }
  42:      function searchServiceCallback(result)
  43:      {
  44:        var output = document.getElementById("output");
  45:        if (output)
  46:        {
  47:            while (output.hasChildNodes()) {
  48:                output.removeChild(output.lastChild);
  49:            }
  50:        }
  51:        var resultsHeader = document.createElement("h5");
  52:        output.appendChild(resultsHeader);
  54:        if (result &&
  55:        result.resourceSets &&
  56:        result.resourceSets.length > 0 &&
  57:        result.resourceSets[0].resources &&
  58:        result.resourceSets[0].resources.length > 0)
  59:        {
  60:            resultsHeader.innerHTML = "Bing Maps REST Search API  <br/>  Found location " +
  61:                result.resourceSets[0].resources[0].name;
  62:            var bbox = result.resourceSets[0].resources[0].bbox;
  63:            var viewBoundaries =
  64:                Microsoft.Maps.LocationRect.fromLocations(new Microsoft.Maps.Location(bbox[0], bbox[1]),
  65:                new Microsoft.Maps.Location(bbox[2], bbox[3]));
  66:            map.setView({ bounds: viewBoundaries});
  67:            var location =
  68:                new Microsoft.Maps.Location(result.resourceSets[0].resources[0].point.coordinates[0],
  69:                result.resourceSets[0].resources[0].point.coordinates[1]);
  70:            var pushpin = new Microsoft.Maps.Pushpin(location);
  71:            map.entities.push(pushpin);
  72:        }
  73:        else
  74:        {
  75:            if (typeof (response) == 'undefined' || response == null)
  76:            {
  77:                alert("Invalid credentials or no response");
  78:            }
  79:            else
  80:            {
  81:                if (typeof (response) != 'undefined' && response && result && result.errorDetails)
  82:                {
  83:                    resultsHeader.innerHTML = "Message :"  + response.errorDetails[0];
  84:                }
  85:                    alert("No results for the query");
  86:            }
  87:        }
  88:      }
  90:  </script>
  92:  <div id='myMap' style="position:relative; width:600px; height:400px;"></div>
  93:  <div id="output"></div>


As you can see, I did very little to modify the way the script works in the example from the Bing Maps API. I just hacked it to work for my purposes. Because why?? Yes… that’s right… I’m lazy…


For this demo all we need to know how to do in jQuery is read SharePoint form fields (lines 24-27 in the script above). Luckily, I already have a blog post that walks you through understanding this:

A Dummies Guide to SharePoint and jQuery–Getting & Setting SharePoint Form Fields


In SharePoint we are going to create a list called “Offices”. This list will contain the fields “Address”. “City”, “State”, and “Zip”. These are the fields we will send to the Bing Maps API so it knows which address to display in a map.

Then all we need to do is create a page in SharePoint and put all the pieces together. I’ll actually show you all of this in action in the video below, but the breakdown of the steps for those of you taking notes is:

  1. Create a Web Part Page
  2. Add the List View for “Offices” on the page
  3. Open the page up in SharePoint Designer and put an Edit Form Web Part for Offices on the page
  4. Make sure the Edit Form Web Part has the fields Address, City, State, and Zip. This is the form that the script will use to read the Address fields.
  5. Create a Web Part Connection between the Offices List and the Office Edit Form Web Part. This will enable us to click on one specific office to populate the edit form.
  6. Add the above Script to the page. I’ll be doing this by linking to the script in a Content Editor Web Part.
  7. Hide the Edit Form Web Part

And that’s all there is to it!  So, without further ado, here’s the demo in action:

Integrating Bing Maps with a SharePoint List


Hopefully you can see some real world use for a simple solution like this. I’ve barely scratched the surface with the Bing Maps API and do look forward to having some time to see how else I can integrate it into SharePoint.

Were there other ways to make this functionality work?? Absolutely! Many probably. I didn’t HAVE to use the Edit Form Web Part, I could have written more jQuery to read the address directly from the List View when a user clicked on a row for instance. However, as a practitioner of the KISS principle this approach provided the functionality with the least amount of script and effort.

I know that my buddy Tom Resing (@resing) has done quite a bit with Bing Maps and SharePoint, so you might want to check out his blog for some of the magic he’s done: In fact I wouldn’t be surprised if he’s blogged something similar… hopefully not TOO similar. :)

Anyway, I hope you learned something, if you didn’t, feel free to leave a comment and teach me a thing or two… Believe me, there’s a lot I don’t know.  As always, thanks for stopping by.


The sample scripts are not supported under any Summit 7 Systems standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Summit 7 Systems further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Summit 7 Systems, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Summit 7 Systems has been advised of the possibility of such damages.

About Mark.Rackley