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

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ 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 not require advan

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet: ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience. You can also use ScreenMeet with other CRM products or even on its own without a CRM. Here is a short video demo of ScreenMeet with Dynamics integration: ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appea