Customer experience | Sales, Customer Insights,...

minimum security role requirements to cancel and resolve a case

(0) Share

Report

Posted on by MikeC282

2,175

Hi all,

I've created a custom Model-Driven App and have added cases to the app. Everything seems to work fine and in my custom security role I've set organization level for all CRUD operations for Case, Account and Contact.

I've also set organization level for Subject, activitiy.

I've also set user level for User Entity UI Settings and User Entity Instance Data but it's still throwing up a insufficient privileges error for our users when they try to resolve or cancel a case. I then went into the BPFs and checked Organization for all the BPFs as well.

Is there any other security role areas I'm missing?

I have the same question (0)

All responses (5)

Answers (0)

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi,

The error message will tell you what exact security permission is missing.

Take a look at this article, if that doesn't fix your issue then please share screenshot of the error along with any logf files-

https://www.powerobjects.com/blog/2015/02/13/access-denied-identify-fix-security-role-issue/

Hope this helps.

Was this reply helpful? Yes No
MikeC282 2,175 on at

Like (0)

Report

Hi Ravi,

The error doesn't display much information at all even when I got the user to cancel in the old UI.

It just says:

"You do not have enough privileges to access the Microsoft Dynamics 365 object or perform the requested operation. For more information, contact your Microsoft Dynamics 365 administrator."

The error code is Error code: 0x80048306 but it's not giving me anymore detail into what exactly is causing this error or the entity object that I have to grant permission for cancelling and resolving cases.

Was this reply helpful? Yes No
RaviKashyap 55,410 Moderator on at

Like (0)

Report

Try giving the out of box customer service rep role and see if that works. If it wors then you can compare the permissions. Sorry but I don't have any other good solution :(

Was this reply helpful? Yes No
Suggested answer

Abhishek Dhoriya 1,013 on at

Like (0)

Report

Hi Mike ,

I would suggest you to give CRUD permission to Case Resolution Entity as well and give it a try.

A quick question here..... why are you assigning Custom Security Role when you can live with the OOTB Security Roles eg. Customer Service Representative.

Possible Cause:

You need to assign CRUD permissions to Case Resolution Entity, also any other related entities that your custom code or System is trying to create on Resolving a case.

For ex. If you are sending any mail to the Customer who raised the case then you need to have the CRUD permission on Activity entities as well.

I hope you got the some idea on the the error. How ever you can down load the Error log and share for more assistance if needed.

Let us know if this works for you.

Thanks and have a great day ahead.

Abhishek Dhoriya

Was this reply helpful? Yes No
Suggested answer

Eccountable 10 on at

Like (0)

Report

Hi Abhishek,

There is no security role setting for the Case Resolution Entity because it is an activity, and all activity type entities are managed under the Security Role Core Records/Activity entity, but you gave me a valuable clue. I found that the security role must contain the "User" right to delete activities in order to resolve a case. I also found that the security role must contain the rights to create/read/write/append/append to the Queue. (community.dynamics.com/.../user-cannot-resolve-a-case

Was this reply helpful? Yes No