Tag Archives: SharePoint

REMINDER: SharePoint BCS connector for CRM

I’ve been going through a bunch of CRM integration scenarios to refresh my “hands on” abilities.  You have to do that in a job like mine, otherwise you’re just a talking head that doesn’t know what you’re talking aboutSmile.  Anyway, the topic of integrating CRM with SharePoint beyond what’s available out of the box comes up often.  Two sessions worth watching to understand some of the possibilities are:



They are very similar sessions, but from two different presenters.  One of the things covered in these sessions is how to integrate CRM and SharePoint through BCS.  The trick to doing it productively is the sample code Chris and Girish made available here:


With this, you can now open up the world of possibilities that SharePoint BCS enables including cross entity searching.  See Configuring Business Connectivity Services (BCS) Search in SharePoint 2010 as an example.


CRM 2011 OnPrem integrating with SharePoint Online

“Can I get the the integration the Microsoft Dynamics CRM 2011 List Component for Microsoft SharePoint Server 2010 provides to work with SharePoint Online when my CRM 2011 deployment is OnPrem (i.e. installed inside my organizations private network or somewhere else that’s not CRM Online)?”

The answer is Yes with a few caveats / configuration hints. 

First, you have to understand that the built in integration between CRM 2011 and SharePoint 2010, enabled through the List Component, is actually at the UI level. 


Everything inside this highlighted blue border is UI rendered on the SharePoint server and surfaced through an iFrame.  The CRM 2011 List Component for Microsoft SharePoint 2010 is responsible for the CRM 2011 look and feel.  CRM 2011 just stores metadata about SharePoint in a set of Entities.  Therefore, you will obviously need internet connectivity from your browser.

But remember, the scenario we want to get working is a “hybrid solution” where SharePoint Online is “in the cloud” and CRM 2011 is OnPrem.  If you just follow the instructions provided through the Configuring the List Component in SharePoint Online blog post, there is a good chance will run into issues with these instructions. 

The first caveat for this scenario is that you have to take authentication into consideration.  If you are one of the more advanced organizations using Office 365 configured to work with your Active Directory Federation Services (ADFS) 2.0 deployment for authentication, then you likely have Single Sign On (SSO) working.  In that case, the Configuring the List Component in SharePoint Online instructions should “just work.”  However, if you aren’t, then you will have to make sure you are logged in to SharePoint Online first.  Once you’ve done that, you can follow the Configuring the List Component in SharePoint Online instructions.  That is IF your CRM 2011 deployment is configured for https.  If not you will run into browser warnings about “mixed mode” and subsequent issues due to your CRM 2011 deployment running under http and your SharePoint Online deployment running under https.  This is to be expected.  To remove the warnings and resolve the issues, make sure you’ve added your SharePoint Online site and your CRM 2011 site to the IE “Trusted sites” list. 


In my case, that’s “http://crm2011” and “*.sharepoint.com” in the screenshot.  However, you could choose to be more granular and enter “yoursubdomain.sharepoint.com” for SharePoint Online if you like.  Finally, make sure that you configure a “custom level” setting for your trusted sites to enable the display of mixed content without prompts:


If you weren’t in a position to follow the Configuring the List Component in SharePoint Online instructions before, then you should be now.  Again, both initial configuration AND end user scenarios will require the user to login to SharePoint Online first before you bring up your CRM UI, unless you have SSO configured.


PubSec Dev Dinner on External Data and Services with SharePoint 2010

My old team is having a developer dinner tomorrow night titled Developing SharePoint 2010 Solutions Using External Data and Services.  See here for more details at http://bit.ly/kPUq5n.


What you will learn

SharePoint 2010 allows developers to work with both internal and external data using Business Connectivity Services (BCS), Excel Services, Access Services and custom WCF services. During the presentation we will discuss and demonstrate several common usage scenarios.

  • Bringing SQL Server data to SharePoint using BCS
  • Sharing Excel Data using PowerPivot for SharePoint
  • Publishing Access Database applications to SharePoint
  • Sharing secure data using BCS and the secure store service
  • Creating Silverlight Using WCF RIA services for SharePoint


SCREENCAST: JavaScript Intellisense for SharePoint

Follow devkeydet on Twitter

In this screencast, you will learn how to get the most out of JavaScript programming with SharePoint 2010 projects in Visual Studio 2010. You will see how to get JavaScript Intellisense and debugging working for jQuery and the Client Object Model. You’ll also learn about the benefits of using the Microsoft Ajax Content Delivery Network (CDN).

If you don’t pause your video player at the right time, you might miss the location of the SharePoint JavaScript files. Here is a link to the MSDN How to article that talks about those files:


Direct link:


Does jQuery ship with SharePoint 2010? (and why you should be using an Ajax CDN)

jQuery is one of the most popular javascript libraries used by ASP.NET developers.  In fact, jQuery ships with Visual Studio 2010.  It is in the “Scripts” folder of a new “ASP.NET Web Application” or “ASP.NET MVC 2 Web Application” project template.

Does jQuery ship with SharePoint 2010?  Short answer: No.  I see this asked (publicly and internally) a few times a month.  Long answer: You don’t need it to.  Just use it from the Microsoft Ajax CDN

Assuming you don’t have to build a solution on a closed network with no internet access, then one of the first things you should consider is to replace all the references in your code to local javascript files to CDN references.  By doing so you get the general benefit that all CDNs offer (not just Ajax CDNs) which is that you get directed to a server the is closer to you.  Also, since browsers cache files based on URL, referencing the CDN from all your code means that different web apps use the same version of the javascript file cached in the browser.  Last, but not least, it means less files you have to maintain on your own servers.

Here’s what a script reference to jQuery 1.4.2 looks like when it is local:

<script src="../../Scripts/jquery-1.4.1.min.js" type="text/javascript"></script>

Here’s what it looks like when referencing the CDN:

<script src="http://ajax.microsoft.com/ajax/jquery/jquery-1.4.2.min.js" type="text/javascript"></script>

So that’s how easy it is to reference jQuery from your SharePoint code.  However, as you can see, this applies way beyond just SharePoint programming.

LINQ to SharePoint DSL Extension for VS2010


This extension looks very useful!  I haven’t gotten around to trying it out just yet because I am in the process of rebuilding my SharePoint 2010 dev environment now that the product has released.  However, it essentially gives you “Add Service Reference” like capability so you don’t have to use spmetal to use LINQ to SharePoint 2010.  You can see a video walkthrough of this extension at http://code.msdn.microsoft.com/linq2spdsl/.

FREE TRAINING: What’s New in Microsoft SharePoint 2010 for Developers

digg_url = “http://blogs.msdn.com/devkeydet/archive/2010/04/26/free-training-what-s-new-in-microsoft-sharepoint-2010-for-developers.aspx&#8221;;digg_title = “FREE TRAINING: What’s New in Microsoft SharePoint 2010 for Developers”;digg_bgcolor = “#555555”;digg_skin = “normal”;http://digg.com/tools/diggthis.jsdigg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;

“This two-hour clinic describes various new features and enhancements that Microsoft SharePoint 2010 provides developers. It describes how you can create and deploy SharePoint 2010 solutions using Microsoft Visual Studio 2010. It also describes how you can develop remote clients for SharePoint 2010 and develop SharePoint 2010 solutions that incorporate data from external line-of-business applications.”


Great PDC session on SharePoint 2010 sandbox solutions


I missed this session at PDC.  There were so many good sessions, it was hard to choose.  The good news is that the sessions are now showing up at http://microsoftpdc.com/Videos

I didn’t get to elaborate on sandbox solutions in any great detail during my recent developer dinner presentation on SharePoint 2010 due to time constraints.  However, this is a very important feature of SharePoint that you will want to dig into as you go explore SharePoint 2010.  Chances are the environment you will be deploying solutions to will only allow sandboxed solutions.