Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Hide OOB fields on sel...
Microsoft Dynamics CRM (Archived)

Hide OOB fields on select records

(0) ShareShare
ReportReport
Posted on by Shidin Haridas 3,497

Hi fellow CRM Enthusiasts,

Got a requirement recently where I need to hide certain OOB fields such as 'Modified By, Created By' fields from the UI, for certain users (which will be decided by their Security Roles/Security Profiles).

I am working on MSCRM 2015, and I believe that the OOB fields in question do not support 'Field Level Security'.

I could use client side scripts to hide the fields from the UI, but a smart user can always use the 'Advanced Find' to view the information that I am trying to hide.

What would be a good solution to this requirement?

Thanks  in advance!

-SH

*This post is locked for comments

  • Nadeeja Bomiriya Profile Picture
    Nadeeja Bomiriya 6,804 on at
    RE: Hide OOB fields on select records

    Hi Shidin,

    The Retrieve plugin should run quick and shouldn't notice any difference.  RetrieveMultiple may have a second or two overhead for the restricted users.

  • Shidin Haridas Profile Picture
    Shidin Haridas 3,497 on at
    RE: Hide OOB fields on select records

    Hi Nadeeja,

    Thank you for your detailed response. I too came to the same conclusion, using the Retrieve & RetrieveMultiple plugin.

    When you say, 'performance will be slightly degraded due to additional processing', how big will the impact be?

    I understand the server processing, load balancing all might come into play here.

  • Shidin Haridas Profile Picture
    Shidin Haridas 3,497 on at
    RE: Hide OOB fields on select records

    @Shivaram,

    Thank you for sharing that link. Really informative.

    That being said, I would not dare to do any direct DB changes for now.

  • shivaram Profile Picture
    shivaram 3,315 on at
    RE: Hide OOB fields on select records

    Hi Shidin,

    This is really good requirement. Even So many facing this issue and raised in Microsoft service, It might be available in future versions.

    But as of now using following link you can change This.

    https://weblogs.asp.net/gayanperera/crm-2011-field-level-security-for-oob-attributes

    But there are few problems with this solution

    1st one is you should have access for CRM Database (Hope you are using OnPremise)

    2nd one is you should know the entity Id

    After this, you should change CanBeSecuredForRead,CanBeSecuredForUpdate,CanBeSecuredForCreate Columns from 0 to 1.

    Then you can Edit Field Security for Modifiedon/CreatedOn.

    But even System Administrator also can't see the value in those fields. I found this solution. But I can't suggest you strongly for this.

    Open the link and check once. Final decission will be yours.

    ModifiedOn_5F00_Disable.png

    ModifiedOn_5F00_Disable.png

  • Verified answer
    Nadeeja Bomiriya Profile Picture
    Nadeeja Bomiriya 6,804 on at
    RE: Hide OOB fields on select records

    Hi Shidin,

    This can be done by creating two plugins.  First one runs on "Retrieve" message and second runs on "RetrieveMultiple" message.  Retrieve message triggers before the data of a single form is displayed to the user.  RetrieveMultiple message triggers before a list of data is displayed to the user (including Advanced Find).

    Inside the plugin, you need to check the user's security role.  If the user is assigned a restricted security role, then you can modify the required fields with dummy data before they get displayed to the user.  For example, you can set all createdon dates to 1900/1/1.

    Please note, performance will be slightly degraded due to additional processing required.

  • Shidin Haridas Profile Picture
    Shidin Haridas 3,497 on at
    RE: Hide OOB fields on select records

    Using the PostOperation on the RetrieveMutliple plugin message will help to blank out the data from the Views, but I am more concerned about the performance overload if I have to use this approach.

    Is there any other solution than this?

  • Shidin Haridas Profile Picture
    Shidin Haridas 3,497 on at
    RE: Hide OOB fields on select records

    Hi,

    Hiding the fields from the Form is only one part of the solution.

    An user can always add the OOB fields into the Advanced Find view and see the information.

    Basic requirement: End User should not be able to see who created or modified the record.

    Thanks.

  • Community Member Profile Picture
    Community Member on at
    RE: Hide OOB fields on select records

    You can create a separate form and make only that form available to the users using roles.

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.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,409 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans