I am currently trying to update the Field Level Security on a field for Account Numbers (String, max length 20) so that only Admins and Users in a specific group can make the update. I am currently running into an error when I attempt to save the field after updating the Field Security to Yes, that states: /Cannot Secure Entity Key Attribute The field Account Number is not securable as it is part of entity keys ( AccountNumber_Key ). Please remove the field from all entity keys to make it securable./
We are wondering as a team if this is something in the design of Dynamics, and if there is any suggested course of action to lock down the field from all users except those in a single team.
To verify, I did the following test in another environment:
1)Create one Key, and select 'Account Number' field
2)Enable field security and encounter the same error as you did:
So, field security cannot be enabled if the field has been selected as alternate key.
I hope you can mark my answerverifiedif it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.