problem with security role in case entity

(0) Share

Report

Posted on by ehsan af

215

i changed write permsion in case entity to user level security role but user still can edit the case form .

i checked share permision and everything in teams and BU security role.

what i must do check to solve this problem ?

I have the same question (0)

All responses (8)

Answers (1)

Linn Zaw Win 3,407 on at

Like (0)

Report

Can you please check the following forum thread with the similar issue? As mentioned in one of the answers, you can use Entity Security Role tool to see which security roles have access to the Case entity. Then, use the User Security Manager tool to see which security roles a user has, including the security roles of his team.

https://community.dynamics.com/365/f/dynamics-365-general-forum/391987/hide-entity-to-certain-users/1054615

Was this reply helpful? Yes No
ehsan af 215 on at

Like (0)

Report

i checked everything in Entity Security Role and User Security Manager .

user still can edit the case form :/

Was this reply helpful? Yes No
Jomy Jose 290 on at

Like (1)

Report

Check whether the user is the manager of another user. In that case user may have the edit privilege's of cases owned by sub level.

Also if the record owned by same user then user level privilege's will allow him to edit.

Was this reply helpful? Yes No
Linn Zaw Win 3,407 on at

Like (0)

Report
When you checked everything in Entity Security Role and User Security Manager, you did not see any role that would grant write privilege to the Case entity, is that correct?

Can you double-check by using Your User Security - Magnified tool from XrmToolBox for that user and look into the Case row?

If you also don't see any role with write access to Case entity in that role,

another possibility is access teams. Please check if there is access teams implemented in your system.

Finally, please also check the cascading behaviour of the N:1 relationship from Case to the parent entities to see if there is any of them may cause this issue with Share Cascading and Reparent Cascading.

Was this reply helpful? Yes No
ehsan af 215 on at

Like (0)

Report

I checked everything .

Even when the user is limited to "user" read security role to case entity , but can still see the record when asigned to another user.

I checked everything and clear user from all teams member.

I checked N:1 realationship and changed it to cascading none in reparent and share.

and user only has one security role that in read and write permision that set to user level security role in case entity.

I use dynamics 365 On-Premises version 9.0.13.11 .

Could this be a bug from Microsoft?

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Have you tried to create new security role and assign to the user?Make sure when you create new roles create copy from system define roles.see if this works.

Also please try to apply different user and check.

Was this reply helpful? Yes No
Verified answer

Linn Zaw Win 3,407 on at

Like (1)

Report
Even if you change the relationship to cascading none in reparent and share, the existing auto-share will not be reverted for the existing records.
If your environment is on-prem, will you be able to run a SQL query on POA table? Replace @UserId with the impacted user and @CaseGUID with the GUID of the case record that the user can see (but not supposed to).

SELECT * FROM PrincipalObjectAccess WHERE PrincipalId = @UserId AND ObjectId = @CaseGUID

Was this reply helpful? Yes No
ehsan af 215 on at

Like (1)

Report

thank you linn.

existing records not effected in new permisions defined in security role and new records work correctly after set cascading none for n:1 relationship for parent filed (contact) .

It caused a lot of trouble and wasted my time.

thanks

Was this reply helpful? Yes No