SharePoint integration - use separate site collections based on business unit
-
mardi 22 mai 2012 11:25
Hi,
I have a client with multiple divisions (Business Units) and have a requirement to separate not only records in CRM (easy enough with Business units and Security Roles) but also the documents that are stored in SharePoint.
Does anyone know of a way to do this using the out of the box features or will this require customisation?
Regards,
Matt
Toutes les réponses
-
mardi 22 mai 2012 13:14
What is Document Management?
The Document Management feature of Dynamics CRM 2011 allows out-of-the-box integration between CRM 2011 and SharePoint 2007, 2010, or SharePoint Online. It allows you to create records in CRM and maintain a link between the record and its related documents stored inside SharePoint. Integration with SharePoint 2010 offers the best user experience, as SharePoint documents are displayed within a familiar CRM user interface. SharePoint 2007 and SharePoint Online are also supported, but are displayed inside an iFrame hosted within CRM.
The SharePoint List Component
The SharePoint List Component is an add-on which you install and activate in SharePoint 2010 to obtain a rich integration with CRM 2011. The component is responsible for displaying SharePoint documents inside a familiar CRM grid control, as well as providing SharePoint functionality in a CRM grid toolbar. The List Component also controls automatic folder creation inside SharePoint to allow a tidier and more organized folder hierarchy.
So what are the Benefits?
- Access, edit, and create SharePoint documents from a single environment within CRM.
- No more fiddling with separate applications.
- Very simple to setup in 5-10mins.
- No need to setup permissions to SharePoint sites or documents inside CRM. All security is handled through SharePoint.
- Link records in CRM of any entity (including custom entities) to documents stored in SharePoint.
- Check-in/check-out documents to prevent other people from working on a document while you are.
- Versioning history to track the lifecycle of a document.
- Create and manage SharePoint locations within CRM.
- Point multiple CRM instances to a single SharePoint location.
gruss Daniel Ovadia MBSS - Microsoft Dynamics CRM MCNPS
-
mardi 22 mai 2012 13:18
Hi Daniel,
I appreciate the time you took to put together this response but it doesn't really give me the answer I am looking for. I've used the SharePoint integration and am aware of all the benefits but my customer has a very specific requirement whereby they wish for users in different business units to be restricted from viewing the documents stored by users from other business units but have the documents surfaced through CRM.
I'm thinking separate site collections to do this but wondering how i can dynamically link an opportunity to the correct site collection to ensure any documents are protected.
Regards,
Matt
-
mardi 22 mai 2012 13:30
Hi Matt,
you are right, there must be seperate site collections for each organization, because u must add the sharepointdocument URL for every seperate organization if you wish that the docs are protected against the other orgs. When some users uses workspace, they will be able to see via workspace the url of the root sites, for that u must use the lockdown feature in sharepoint, which version of sharepoint are u using? searchserverexpress?foundation or bigone?
If u are´nt using the list component then u will receive script errors, for example when u directly open a pdf file on a x86machine..
Rights (security roles) are not transferred from CRM to SharePoint, so if u want to figure out if somebody have access, look directly in sharepoint if he is able to see docs or not.
gruss Daniel Ovadia MBSS - Microsoft Dynamics CRM MCNPS
- Proposé comme réponse Daniel Ovadia jeudi 5 juillet 2012 15:20