Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have a user trying to assign another user to a work team, we checked the permissions and roles, and everything looks correct. The error it flagged was:<Message>RoleService::VerifyCallerPrivileges failed. User: ec0ebfdb-e5e1-e811-8106-0050569f3039, PrivilegeName: prvAppendSharePointData, PrivilegeId: 2e774df5-2d24-4c8b-b9bb-973d5ef46f3e, Depth: Global, BusinessUnitId: bca38cd5-b0a0-e611-80d8-0050569f5e28</Message>
The problem is that this happens in a productive environment, and in dev we can't replicate it.
Has anyone had a similar error, this is in an on premise environment.
Translated with www.DeepL.com/Translator (free version)
I think it's interesting to compare Production and Development. To start with, the error message has to do with missing the privilege "Append" on Sharepoint Data. It should be "Global" (full green circle). Please check for "Sharepoint" options and review that it's correctly configured the "Append", as it surely is non marked or is set to User.
Hello, thank you very much.
I checked that field and its privileges, in both environments, I give you context. The error was reported when a user wanted to add another user to a work team.
Looking in the documentation I found that there are two fields to review "SharePoint Site" and "Document Location", so I reviewed the custom role permissions that allow adding users to work teams (in addition to the system administrator) and has at the organization level those fields.
I could only get the error when you do not have that custom role or administrator role, neither the user nor the work team to which it belongs, because if the user does not have the role but his team does, the error does not come out or vice versa.
Business Applications communities