field security profile question RRS feed

  • Question

  • 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?

    Tuesday, December 31, 2013 12:43 AM

All replies

  • Have you enabled any field for field security? "Field Permissions" displays fields that are enabled for field level security. If none of teh fields are enabled then nothing is shown.. you cannot add fields from this area.

    If my response helps you in finding your answer then please click 'Mark as Answer' and 'Vote as Helpful'

    • Proposed as answer by Mamatha Swamy Tuesday, December 31, 2013 1:03 AM
    Tuesday, December 31, 2013 1:02 AM
  • Thanks Mamatha.  I updated my original question.  Any idea why only *custom* fields can be secured with OTB field-level security?  Seems like this creates a lot of additional work for developers who want to implement field-level security?

    Tuesday, December 31, 2013 1:15 AM
  • Hmmm... its a different question now! Will choose to post a new response rather than updating the earlier one :)

    Not very sure of why MS took that approach. Could be because implementing it on certain fields might break the OOB CRM functionality.

    Well, there are different approaches that people take to implement FLS for OOB fields. If you are okay with unsupported customizations then here is a simple way of doing it. http://weblogs.asp.net/gayanperera/archive/2010/11/02/crm-2011-field-level-security-for-oob-attributes.aspx

    This is being tracked as a suggestion to MS on connect. You could vote for it to get into the product in the upcoming versions


    Hope this helps!

    If my response helps you in finding your answer then please click 'Mark as Answer' and 'Vote as Helpful'

    Tuesday, December 31, 2013 2:04 AM