You’re offline. This is a read only version of the page.
(I'm a SharePoint guy - so please forgive my ignorance...)
CRM Online - Document Management configured for Account and Opportunity entities, with folders hierarchy created based on Account.
All works great - Account library, folder in there for each account, then for a given account, an opportunity subfolder, and a folder for each opportunity in there - all fine.
Customer wants to secure SharePoint so that 'account managers' only have access to the SharePoint folders for their own managed accounts.
ok - cheap and cheerful solution (rather than syncing CRM and SP security) was implemented as follows:
In SharePoint, in the Account library, create folders for each manager - e.g. RobEllis would be my folder - and set permissions as required.
In CRM, create a document location called RobEllis, whose parent document location is the account library document location, and whose path is RobEllis.
(so the combined location is account/RobEllis)
In SharePoint, move the existing folders for the various accounts into the relevant named manager folders - e.g. from the root of 'Account', into 'RobEllis'
In CRM, update the document location for each moved folder, to change the parent location to be RobEllis
Done.
All good - users can see the moved documents from CRM fine, add documents, etc, including for opportunities.
Then we find a problem after a few weeks:
Creating a new opportunity and add documents, or add documents to an existing opportunity with no previous documents - user is prompted 'do you want to create the folder' (the folder path is correct) - click OK - error - file not found.
The document location is not created in CRM, and the folder is not created in SharePoint.
Moving the account folders back into the root of the library, and undoing the changes to their document locations fixes the issue.
This issue is reproducible in a trial environment as well as the live customer one.
Thoughts, suggestions? Is this a bug, or 'as designed'?
Is it some quirk of having 'nested' document locations?
The options as I see it currently are:
1. Undo all the changes made so far - so security is weaker in SP, but users can create documents for opportunities.
2. Configure opportunities to use their own library (instead of hierarchy based on account), and accept opportunity docs are less secure, but account docs are secure.
3. do 1 above, and develop or buy a tool to sync permissions from CRM to SP - so users can create documents for opportunities, and the whole lot are secure.
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
4
