You’re offline. This is a read only version of the page.
10
Hello!
I am currently preparing the UR16 from UR11 for my client and I ran into a problem with the field level security.
In our CRM the field level access is provided to all users via teams that were given single field sharings through "PrincipalObjectAttributeAccess". Roles are only used for Create-Permission.
This worked fine in UR11 but with UR16 the field permissions do not apply to the team-members anymore. Directly sharing fields to the users works but is not applicable due to high migration effort of the sharings and must be avoided.
I observed, that I am able to retrieve the field level secured values by "Xrm.Page.getAttribute()" although the form shows only dots in the fields (if the user is in a Team that has access to the fields). Additionally team-members can see all secured fields in SubGrids like the Adv.Find.
It looks like a Problem with the Form being initialized with secured fields although it should be unlocked. But I have no clue how to fix this behaviour.
Any help is greatly appreciated!
Best regards,
Henryk
*This post is locked for comments
I have the same question (0)
The problem has been solved/clarified. I requested assistance from Microsoft and after some cycles of explaining, providing information and performing default steps this issue was escalated to the development team.
This issue comes with Update Rollup 14 and is related to a change within the security mechanism of CRM. I was told this changes were made to align the mechanisms of CRM 2011 with the ones implemented in CRM 2013.
The workaround for this issue is to add a security role to each team. The security role even don't has to have any priviliges. After applying a role ta a team the inheritance of shared field permissions works again.
Regards,
Henryk
Share
Report
All responses (
Answers (
