Skip to main content

Microsoft SharePoint and Dynamics CRM -- Better Together: Part 6

Using Both Microsoft Dynamics CRM and SharePoint

By integrating SharePoint with Microsoft Dynamics CRM, you can easily add this extensive functionality to your solution. Dynamics CRM 2015 includes built-in integration with SharePoint so you can show related documents within a Dynamics CRM form. Dynamics CRM supports integration with SharePoint Server 2010, SharePoint Server 2013, and SharePoint Server Online.
An article in MSDN illustrates the integration options: https://msdn.microsoft.com/en-us/library/gg334768.aspx 
SharePoint integration enables you to store and manage documents on SharePoint in the context of a Microsoft Dynamics CRM record, and use the SharePoint document management abilities in Microsoft Dynamics CRM, such as checking the document in and out, viewing version history, and changing document properties. 

Because both SharePoint and Dynamics CRM are available deployed in the cloud or on premise, there are several permutations of how you can handle authentication and integration. 

You can integrate with SharePoint in two basic ways:
  • Client-to-server integration with SharePoint: This uses the Microsoft Dynamics CRM List Component in the sandboxed environment of SharePoint.  Client-to server integration is supported for both online and on-premises versions of CRM and SharePoint.
  • Server-to-server integration with SharePoint (CRM Online only): This does not require you to install the Microsoft Dynamics CRM List Component in the sandboxed environment of SharePoint or any other additional software to have the SharePoint document management functionality within CRM. After you enable server-based SharePoint integration for your organization, you can’t revert to the client-based authentication method. Server-based integration is supported for SharePoint Online, and SharePoint on-premises only if you have Microsoft Dynamics CRM Online 2015 Update 1.


You can automate many functions such as creation of document libraries triggered by events in Dynamics CRM.  For instance, when an opportunity moves to the stage when a proposal is prepared, you could create folders for the solicitation as well as the proposal, and associate them with the opportunity.    You might also want to use standard document templates to populate the folders.  

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do