Important considerations for server-based SharePoint integration
Applies To: Dynamics CRM 2013
Before you move to server-based SharePoint integration, review the following table to see some of the differences you’ll experience between client-based versus server-based SharePoint integration.
Area |
Client-based SharePoint integration |
Server-based SharePoint integration |
For those moving to Server-based SharePoint integration |
|---|---|---|---|
Sign in |
Must sign in to both Microsoft Dynamics CRM and SharePoint to be able to view the document grid. |
Only need to sign in to CRM. |
|
List component |
Must download list component and upload directly to SharePoint site before connecting site to CRM. |
No list component required. |
|
Support lifecycle |
This approach relies on the sandboxed solutions functionality on SharePoint. SharePoint plans to deprecate this functionality. If the sandboxed functionality isn’t available for a SharePoint site, this integration won’t work. |
This approach relies on server-to-server authentication and won’t be affected by the deprecation of the sandboxed solutions functionality in SharePoint. |
More information: Deprecation of Custom Code in Sandboxed Solutions |
SharePoint commands |
Includes:
|
Does not include the SharePoint commands listed in the client-based integration column. |
The client-based actions can be accessed directly in SharePoint with server-based integration. Select Open SharePoint to view the document location directly in SharePoint and access the actions. .jpeg "Open SharePoint Team Site")
|
Custom content types |
Can create new custom content types. |
Can’t create new custom content types. |
Previously created custom content types can still be viewed and edited but to create a new custom content type you’ll need to create it directly in SharePoint using Open SharePoint. |
Absolute URLs |
Supported |
Unsupported |
Users moving from the client-based approach to the server-based approach need to convert their absolute URLs to relative URLs. This will only work if the absolute URL provided is in a SharePoint site valid for server-based SharePoint integration. |
Folder navigation |
Users can create SharePoint folders while in CRM. Folders are displayed in a grid that users can navigate through. |
Users can’t create folders in CRM and the folders aren’t displayed in CRM. |
All documents under subfolders are displayed in the CRM grid. Relative URLs are displayed to show users where the document is located relative to the parent folder. SharePoint document views can be customized so users see only documents in a specific folder or subfolder. More information: "Validation Error" when you try to configure server-based SharePoint integration for Microsoft Dynamics CRM Online and SharePoint Online |
Online vs. on-premises support |
Can connect:
|
Can connect:
|
|
Resource Throttling |
Doesn’t apply. |
A document library with 5000 or more documents might experience resource throttling. More information: Resource throttles and limits |
If you have more than 5000 documents in your document library, you can view the documents in the default grid view. However, if you sort on columns other than the default sorted column, you might see an error indicating that the throttling limit has been exceeded. |
Known issues with server-based SharePoint integration
The Microsoft Dynamics CRM List Component builds the SharePoint library using the internal name of the document-enabled entity in CRM. Server-based SharePoint integration uses the entity display name. When you upgrade to server-based SharePoint integration, be sure to check that the display names in your document library on SharePoint match the entity display names in CRM.
.jpeg "SharePoint library name and entity display name")
These names should match.
See Also
Installing Guide for Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online
Install the Microsoft Dynamics CRM List component or enable server-based SharePoint integration