SharePoint and Dynamics CRM are excellent products from Microsoft. What happens when you integrate the two platforms?
It reminds me the book “Men are from Mars, Women are from Venus”, written by American author John Gray, and states that most relationship problems between men and women are a result of fundamental differences between the sexes, that men and women are from different planets. Each one is speaking his own language, and they met on earth.
The case here is similar, when you decide to integrate SharePoint with CRM. SharePoint is designed to store unstructured data, and it is excellent document collaboration tool. The strength of CRM is in its ability to capture structured business data, and centrally store it.
While both SharePoint and CRM can exist independently, much more can be achieved when they act in concert.
The Dynamics CRM integration feature enables you to store and manage documents on SharePoint in the context of a Dynamics CRM record, and use the SharePoint document management abilities in CRM. When enabling document management for entities, CRM creates folders in SharePoint, one per each entity selected in the set up process. The folders can be Account or Contact centric folders or standalone folders.
CRM users can select and upload documents to SharePoint, and save them in the corresponding folder in SharePoint, which also bears the name of the entity where the documents are uploaded from. Documents are now spread over different SharePoint folders. While users are expected to work as a team to achieve common business goals through improved communication between CRM and SharePoint users, these folders do not have the familiar structure of folders and tree representation of folders, as we are used to, which makes it so difficult when a document cannot be located or searched for by SharePoint users.
Metadata is the way to go.
Metadata (columns) and views are better and the recommended alternative to managing documents in folders. Metadata provides descriptive information about the document. Views are using the metadata for grouping, filtering and sorting documents in an organized and methodological way.
The challenge is retrieving metadata tags from CRM records and saving them with the documents in SharePoint, where each such field (attribute) retrieved from the CRM record, is saved in the corresponding column of the document library in SharePoint.
Consider a company managing projects in CRM, using a customised Project entity, and billing clients when each of the project’s stages is completed. Using Word Template the Scope of Work (SOW) of the project is generated in CRM, by populating the Word Template with data from the project record and related records. Invoices are also created in CRM, using Invoice Word Template, with the deliveries and services provided for a project stage. In CRM out of the box integration with SharePoint, both documents, the Project SOW and related invoices are uploaded to CRM, one to the Project folder the other to Invoice folder.
As the project progresses team members, which are not necessarily CRM users, follow the project milestones and how the associated invoices are paid by clients. If the company has many clients and each has many projects, and each project has invoices, and their payment needs to be followed up, imagine the effort required collecting details from the project SOW and invoices documents, without having metadata to allow search and views built on logical and easy way to retrieve them.
What is your experience with CRM and SharePoint?
We find this topic so important for better CRM and SharePoint integration, that we have also created LinkedIn Group (join by following the URL below) for all readers to share with all of us, your knowledge, experience and earned best practices on how to improve using SharePoint and CRM in harmony.
Join LinkedIn Group:
Follow us on Twitter:
1 thought on “CRM is from Mars, SharePoint is from Venus”
Thanks! I have been trying to explain this to people, even at Microsoft, for years. It is amazing how many times you stumble across (usually on the SharePoint side, in my experience) who try to twist one product into the other. It would be great is people looked at the total solution and not the product.
Comments are closed.