Customising server-side integration between Dynamics CRM 2016 and SharePoint 2013

• Question

• 

  

  0

  Sign in to vote

  I have been investigating the use of the out-of-box server-side CRM 2016 to SharePoint integration to satisfy a number of document management requirements that we have. There are a number of things that it would be great to be able to customize and some behaviours that are potentially undesirable. I have searched around for documentation and other threads but found very little beyond the vanilla configuration.

  Desirable configuration:

  • Customise the list view of attached documents to include additional columns from the linked document library
  • Add document should allow user to set the value of any mandatory columns that exist on the document library (bonus points if we can also programmatically set some of these fields e.g. adding a registration number to SharePoint to assist searching from SharePoint)

  Undesirable behaviours:

  • No way to link an existing document from sharepoint. It has to be stored in a folder.
  • Use of folders causes problems with corporate document management, should allow linking by other column values.
  • A given document can only be linked to a single entity.
  • Library columns are not able to be set. Even when checking into a library that has mandatory columns with no defaults the SP rules seem to be bypassed.
  • No visible way to roll-up documents from child records in the CRM (or SharePoint really since the folder structures will be distinct between entities)
  • Check in always creates a major version without prompting.

  Am I missing something or are we completely stuck with the OOB behaviour with no way to customize in any way shape or form. If any of these behaviours can be customised; are there any resources out there describing how?

  Friday, January 15, 2016 12:46 AM