When creating SLA Items on SLAs I'm getting the error below. This error is due to the SLA record owned by a user in a business unit that is different than the business unit of the user creating the SLA Items. I haven't been able to find where I can change the security role's access to SLA Items to allow creating SLA Items for organization wide SLAs. Is there somewhere in the security role where I can set this or is it something that can't be changed?
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: SecLib::AccessCheckEx failed. Returned hr = -2147187962, ObjectID: 113077a0-1465-4980-b796-5d1956388c16, OwnerId: 902c606e-aff3-e611-80e2-0050568a271b, OwnerIdType: 8 and CallingUser: 8f7659b7-645e-e611-80dd-0050568a271b. ObjectTypeCode: 4703, objectBusinessUnitId: a090c318-6453-e611-80db-0050568a271b, AccessRights: 524296 Detail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ErrorCode>-2147187962</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>SecLib::AccessCheckEx failed. Returned hr = -2147187962, ObjectID: 113077a0-1465-4980-b796-5d1956388c16, OwnerId: 902c606e-aff3-e611-80e2-0050568a271b, OwnerIdType: 8 and CallingUser: 8f7659b7-645e-e611-80dd-0050568a271b. ObjectTypeCode: 4703, objectBusinessUnitId: a090c318-6453-e611-80db-0050568a271b, AccessRights: 524296 </Message>
<Timestamp>2017-02-22T15:51:06.4216675Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>
*This post is locked for comments
Thank you for clarifying this. It does make sense because SLA Items create workflows in the system that are triggered when the SLA Item's conditions are met. The workflow is most likely assigned to the owner of the SLA record and thus requires assign permissions. Changing the assign permission on the Process entity to org fixed the issue.
ObjectTypeCode 4703 is the Workflow entity and the AccessRights 524296 is the assign permission, though why it's saying they need the ability to assign a workflow is anyone's guess...
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156