Hello, I'm new to field-level security in CRM, but based on my basic understanding, CRM only allows OTB field-level security on custom fields, as opposed to managed fields. Why did MS choose this approach for field-level security in CRM? It seems like this approach creates a lot of additional work/overhead?
*This post is locked for comments
Hello Andrew,
Below are few links that can give you more information regarding Field level security in CRM 2011
- www.microsoft.com/.../details.aspx
- social.technet.microsoft.com/.../15902.field-level-security-in-dynamics-crm-2011.aspx
- msdn.microsoft.com/.../gg309608.aspx
- community.dynamics.com/.../field-level-security-in-crm-2011.aspx
Thank You !
Andrew,
Of all the investments made by the product team for CRM 2011, Field Level Security was one of the biggest investments they undertook. FLS is actually a very daunting challenge to implement. They wanted to make sure it would work in all environments and situations.
I can't recall all the details from a conversation I had with a project manager at the time of the product release but there are all sorts of challenges when trying to apply FLS to OOB fields. I recall that one of them was related to entity to entity mappings of fields.
I am not aware of any public plans to change this in the current roadmap. If you want to kick the can a little bit further down the road, make a suggestion at Connect.microsoft.com and the repost the link back here so forum visitors can vote on it.
#1
André Arnaud de Cal...
291,784
Super User 2024 Season 2
#2
Martin Dráb
230,476
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
