Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
Hide a customized field from other Business Unit

คำถาม Hide a customized field from other Business Unit

  • Thursday, July 05, 2012 10:26 AM
     
     
    Sign In to Vote
    0

    We have done the standard CRM 2011 implementation without any customization ( related to coding). As we have 5 separate LOB andthey do have their own field related to every entity.

    Now the situation is like  Everyone is  able to view each LOB's field but not able to edit though security roles. But the user has go to  through from the every field on entity form which he doesn't like.

    Please provide me a code through each the User can view the fields related to their own LOB but not others.

    Thanks

    DynCRM.

     

All Replies

  • Thursday, July 05, 2012 10:45 AM
     
     
    Sign In to Vote
    0

    HI DynCRM,

                    The easiest way (without coding) solution you could apply would be creating other forms for the different LOB and applying the right roles if you already have a different role for each LOB created. That way you could remove the fields you don’t want to be displayed.

    You can read more about creating multiple forms on this blog http://inogic.blogspot.com.ar/2010/10/multiple-form-layouts-for-single-entity.html

    Regards,
    Damian Sinay

     
  • Thursday, July 05, 2012 1:44 PM
     
     
    Sign In to Vote
    0

    Thanks Damian for the information.

    The shared blog is really very useful .But our application has gone live already and now we would like to hide the field without disturbing Users.

    As I discussed  the same with one of the technical person and he suggested me that it can be done through coding.

    Would appreciate a quick response on it.

    Regards,

    DynCRM


    • Edited by DynCRM Thursday, July 05, 2012 1:46 PM
    •  
     
  • Tuesday, July 10, 2012 3:39 PM
     
     
    Sign In to Vote
    0

    I would recommend you to go for Field Level Security where you can give permissions for a set of users. Here is the link for workaround.

    http://inogic.blogspot.co.uk/2010/10/field-level-security-in-crm-2011.html

    Regards

    RVB

    Please mark if it helps you.

    Rudravarma Batta