locked
Documents sharepoint management issue CRM 2013 RRS feed

  • Question

  • Hi everyone,

    i'm experiencing a strange issue about document management in CRM 2013 with sharepoint integration probably caused by security roles.
    Our client has successfully completed the integration between sharepoint and CRM 2013 and can manage documents normally (the abilitate documents on opportunities), except for users that have only a custom security role created by them that, apparently, has all the correct permissions setted; they used this page as reference:

    http://msdn.microsoft.com/en-us/library/dn531196.aspx .

    What happening in this scenario il the disappearance of documents tab in opportunity form navigation bar.
    We stated that adding salesperson role to the user make things run just fine though salesperson and the custom role have the same permission setted.

    Can someone help me?

    Thanks in advance and best regards,

    Daniele Torlai


    • Edited by EBLtorla Wednesday, June 25, 2014 6:50 AM
    Tuesday, June 24, 2014 1:07 PM

Answers

  • I just figured this out minutes ago.

    The necessary permissions are not visible in the UI, so they can only be added by editing the XML.

    Add the following to the security role's XML:

            <RolePrivilege name="prvAppendSharePointData" level="Global" />
            <RolePrivilege name="prvAppendSharePointDocument" level="Global" />

            <RolePrivilege name="prvAppendToSharePointData" level="Global" />
            <RolePrivilege name="prvAppendToSharePointDocument" level="Global" />

            <RolePrivilege name="prvAssignSharePointDocument" level="Global" />

            <RolePrivilege name="prvCreateSharePointData" level="Global" />
            <RolePrivilege name="prvCreateSharePointDocument" level="Global" />

            <RolePrivilege name="prvReadSharePointData" level="Global" />
            <RolePrivilege name="prvReadSharePointDocument" level="Global" />

            <RolePrivilege name="prvWriteSharePointData" level="Global" />
            <RolePrivilege name="prvWriteSharePointDocument" level="Global" />

    I'm not sure if those permissions can be reduced, but this level made everything work again.

    Please mark this as the answer if it works!

    -James

    • Proposed as answer by James Reinhardt Tuesday, June 24, 2014 3:59 PM
    • Marked as answer by EBLtorla Wednesday, June 25, 2014 6:43 AM
    Tuesday, June 24, 2014 3:59 PM