{"id":3900,"date":"2016-11-18T17:57:20","date_gmt":"2016-11-18T12:27:20","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=3900"},"modified":"2022-06-24T12:43:39","modified_gmt":"2022-06-24T07:13:39","slug":"insufficient-permissions-error-on-assigning-a-record-in-dynamics-365","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2016\/11\/insufficient-permissions-error-on-assigning-a-record-in-dynamics-365\/","title":{"rendered":"Insufficient Permissions Error on Assigning a record in Dynamics 365"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

While working on one of our client requirement, we came across with one interesting scenario about security roles access level setup for Read and Assign privileges, which leads to errors on Dynamics CRM forms.<\/p>\n

Scenario:<\/strong><\/p>\n

The requirement was to allow a user with specific security role in Dynamics CRM say \u201cSalesperson\u201d to assign lead record owned by them to other users on the basis of some criteria.<\/p>\n

Below is how Salesperson security role setup for lead entity,<\/p>\n

\"Security<\/a><\/p>\n

Read and Assign privilege both are user level.<\/p>\n

Process flow advised to follow was:<\/p>\n

    \n
  1. Sales people will check their leads (Since salesperson has user level privilege for read they can view only leads those are owned by them).<\/li>\n
  2. Open lead record, and click on \u201cAssign\u201d button and choose the user to assign the lead to.<\/li>\n<\/ol>\n

    Simple process, the privileges setup allow for assigning records, so they should be good to do the steps requested above.<\/p>\n

    However, in the above case we received an error saying Access Is Denied as shown below.<\/p>\n

    \"Access<\/a><\/p>\n

    When we downloaded error log, it stated insufficient privileges for reading lead record.<\/p>\n

    \u201cSecLib::AccessCheckEx failed. Returned hr = -2147187962, ObjectID: d014dcb3-c77f-e611-8127-fc15b4284c10, OwnerId: 3f92c9a1-f49f-e611-8127-c4346bad3608,\u00a0 OwnerIdType: 8 and CallingUser: 3f92c9a1-f49f-e611-8127-c4346bad3608. ObjectTypeCode: 4, objectBusinessUnitId: d7cf13e4-717f-e611-811c-c4346badf550, AccessRights: ReadAccess<\/strong>\u201d<\/p>\n

    \u201cReadAccess\u201d error was confusing as we actually assigned record and the user to which the record was being assigned also had similar privileges.<\/p>\n

    To dig a little deeper into this, we tried a couple of things;<\/p>\n