Few weeks ago I taught Course 8912A: Customization and Configuration in Microsoft Dynamics CRM 4.0 and a student asked an interesting question:

How should I integrate SharePoint and CRM?

Here are some of my advices and experiences on this topic.

Scenario 1. Integrating CRM with SharePoint (SharePoint to CRM)

  • Problem: CRM is really great application but it lacks document management capabilities (this will probably be shipped with CRM 5.0). You do have an ability to attach documents to CRM entities but you cannot change these later on.
  • Benefits: Each CRM user needs to produce a document that is related to a CRM entity (e.g. Quote). Users will benefit from the ability to see both quote financial information (stored in CRM) and the document itself (stored in SharePoint) from the same application.
  • How to implement it?:
crm
Figure 1: SharePoint site as a document storage in CRM account entity form.

Scenario 2a. Integrating SharePoint with CRM (CRM to SharePoint)

On the other side, you can use CRM to extend your SharePoint site.

2A. Profiling documents

If you are storing your customer related documents to SharePoint (e.g. Project proposal, project plan, vision scope, quote…) you probably want to uniquely connect each document to a customer from your CRM database. This is easy to achieve. You can use Business Data Catalog to create custom, business columns, which connect to your CRM system directly. With this custom business column, you can profile your documents with the unique values coming from your CRM system.

Benefits:

  • This solution is easy to setup and manage
  • You do not need to duplicated your CRM data (e.g. Accounts and Contacts) in SharePoint lists
  • By using SharePoint filtering and search you will find your documents in no time…

Downside:

  • Business Data Catalogs is a feature of SharePoint Enterprise
doclib1
Figure 2: Document Library with Business Data Columns. Columns source is CRM.

2B. Enterprise Search

When it comes to search, CRM built-in search capabilities are somewhat limited (you can only perform entity by entity search). SharePoint comes to the rescue here, allowing your users to use single query across all entities from a familiar search interface.

Benefits:

  • SharePoint is more powerful search engine
  • Familiar SharePoint search interface
search
Figure 3: Shows unified search results. Some coming from CRM and some from SharePoint.

In next post I will go deeper to explain how you can implement these scenarios…

5 Comments

  1. Parth Says

    Nice read! Thanks for the info

  2. manish tyagi Says

    hi
    i want to integrate the feedback form with MS CRM 4.0 means when i enter the data from feedback form it enter in ms crm. can u help me out from the problem please send me link or any other material that help me in solving this problems. plz send it to my id ermanishtyagi@gmail.com

  3. Toni Frankola Says

    @Manish:

    1) Which SharePoint edition do you use? WSS, SharePoint Standard or Enterprise?
    2) What is a feedback? Is it a new CRM custom entity, or you plan to use an existing one?

    T.

  4. Greg Says

    One thing, have you run into the issue where once there are 200 or more records in the entity you are using for the BDC drop-down, that it no longer is usable?

  5. Toni Frankola Says

    @Greg: Yes I did have some problems with it. In such a case I would go create custom columns.

Leave a Reply