AnsweredAssumed Answered

How can I hide a field based on role from the Leads module in Community Edition?

Question asked by cx_elena cx_elena on Feb 15, 2014
Latest reply on Dec 16, 2016 by Anton Dyrdin

Like • Show 0 Likes0
Comment • 13

Dear All

On to second step of customizing Sugar CE 6.5.16.

Scenario
User creates the lead; he should be able to input information to a field name "CUST_PERSONAL"; however, every time there after the field should be visible only to ROLE:Manager, OWNER and should be hidden from Role: DataEntry, FollowUP.

Thanks
Elena

No one else has this question

Outcomes

13 Replies

Jason Eggers Feb 15, 2014 2:28 PM
Mark Correct
Correct Answer
In CE you can use SecuritySuite (https://www.sugaroutfitters.com/addons/securitysuite) to create custom layouts for different groups of users. So you could create a group called DataEntry and add a custom layout for that group in Studio. Then show the field on the Edit View, but hide it on the Detail View.

The next problem is that it will always show on the Edit View whether it is the initial creation or a subsequent edit. I have an open feature request in SecuritySuite to separate the rights for Create and Edit. When that is implemented you can prevent Data Entry folks from editing data after entering it.

For now, you can add that custom logic in the view.edit.php. Create custom/include/MVC/View/views/view.edit.php and extend include/MVC/View/views/view.edit.php. Then check to see if this is an existing record and if the current user belongs to the Data Entry group. If yes, then redirect to the detail view. There are some other possibilities that you could do there as well such as display an error or hide the edit button altogether based on the same logic.
Like • Show 0 Likes0
Actions
cx_elena cx_elena Feb 15, 2014 2:49 PM
Mark Correct
Correct Answer
Thanks @eggsurplus for the product headsup.

As this is a test project as of now and client is not really looking to spend any money initially; I have my doubts that I will be able to convince him for the yearly outlay.

However, the product looks promising; wish you best and I shall surely consider it as the client agrees towards it.

I am looking for hard-coded examples; I tried following Andre in one other posts but it crashed my system; repairing the system as I type this. :(

Hope to have some answers for the said problem.
Like • Show 0 Likes0
Actions
- Jason Eggers @ cx_elena cx_elena on Feb 15, 2014 3:03 PM
  Mark Correct
  Correct Answer
  As a sensible business, if they will save more money buying something off the shelf versus paying for services they will almost always do that. Buying off the shelf is almost always cheaper as cost is spread out amongst many users. Plus you will have earned a client for life by showing that you are looking out for their best interest and not your own.
  
  For hard coded solutions, Andre's usually always works. I'm guessing his example is looking up the current user's role and removing the field as appropriate.
  
  If you can share the solution or where you are getting stuck here it would help others down the road as the old forum is in the process of being turned off.
  Like • Show 0 Likes0
  Actions
cx_elena cx_elena Feb 15, 2014 4:01 PM
Mark Correct
Correct Answer
I referred to the post here .

As Marc Quoted:

I finally figured this out. In the listViewPrepare function of my newly-created custom/modules/Opportunities/views/view.list.php file, I changed this existing code:

PHP Code:
$displayColumns = array(); if(!empty($_REQUEST['displayColumns'])) { foreach(explode('|', $_REQUEST['displayColumns']) as $num => $col) { if(!empty($this->listViewDefs[$module][$col])) $displayColumns[$col] = $this->listViewDefs[$module][$col]; } //Global(log)= $this->listViewDefs[$module][$col] ///////// } else { foreach($this->listViewDefs[$module] as $col => $this->params) { if(!empty($this->params['default']) && $this->params['default']) $displayColumns[$col] = $this->params; } }

to this, specifying "UNWANTED_COLUMN_FIELDNAME" as the field/column I wanted to hide and "Account Executive" as the role I didn't want to be able to see it:

PHP Code:
//add three new lines to determine role(s) of current user include("modules/ACLRoles/ACLRole.php"); $acl_role_obj = new ACLRole(); $user_roles = $acl_role_obj->getUserRoles($current_user->id); $displayColumns = array(); if(!empty($_REQUEST['displayColumns'])) { foreach(explode('|', $_REQUEST['displayColumns']) as $num => $col) { if(!empty($this->listViewDefs[$module][$col])) { //new if-else starts here if(in_array('Account Executive',$user_roles) && $col == "UNWANTED_COLUMN_FIELDNAME"){ } else { $displayColumns[$col] = $this->listViewDefs[$module][$col]; } //new if-else ends here } } //Global(log)= $this->listViewDefs[$module][$col] ///////// } else { //didn't worry about this because UNWANTED_COLUMN_FIELDNAME was not a default; //otherwise, if-else this part, too. foreach($this->listViewDefs[$module] as $col => $this->params) { if(!empty($this->params['default']) && $this->params['default']) $displayColumns[$col] = $this->params; } }

It appears to work nicely, simply not including the unwanted column in the list view. Hopefully this will help some other people in the future. Thanks to everyone who has contributed.
marc

I did this in Lead Module for a custom field; So everything remains same but the fact that it was done in exactly same files under module Lead <path was replaced by lead instead of Opportunities.

The reason I did this was that I thought if I am able to replicate in list view, I will be able to do around details view and edit view.

However, this created fatal system error foreach(); I had to revert to the files as they were initially after 3-4 hours of wrestling along.

Now I am following this:

Hi,
Yes its possible
Grab the user role using the following
Code:
$acl_role_obj = new ACLRole();
$user_roles = $acl_role_obj->getUserRoles($current_user->id);
$user_roles will have the list of roles

Hide the panel display using javascript code
Code:
document.getElementById('LBL_SOMETHING').style.display="none";
LBL_SOMETHING would be the panels system name
Write all this code in custom/modules/YourModule/views/view.edit.php (or/and) view.detail.php
Hope it helps
Cheers,
Ishaan

Still stuck :-(
Like • Show 0 Likes0
Actions
- Anton Dyrdin @ cx_elena cx_elena on Dec 16, 2016 1:49 AM
  Mark Correct
  Correct Answer
  cx_elena, I cannot reproduce your action in view.list.php as for hiding a field column for a defined user role - please can someone help me with what Iḿ doing wrong?
  Here is the code I wrote inside the /custom/modules/Contacts/views/view.list.php
  function listViewPrepare() {
  global $current_user;
  include("modules/ACLRoles/ACLRole.php");
  $acl_role_obj = new ACLRole();
  $user_roles = $acl_role_obj->getUserRoles($current_user->id);
  
  $displayColumns = array();
  if(!empty($_REQUEST['displayColumns'])) {
  foreach(explode('|', $_REQUEST['displayColumns']) as $num => $col) {
  if(!empty($this->listViewDefs[$module][$col])) {
  //new if-else starts here || $current_user->is_admin && $col == "phone_mobile"
  if (in_array('Руководители отделов',$user_roles) && $col == "PHONE_MOBILE") {
  $displayColumns[$col] = $this->listViewDefs[$module][$col];
  echo "321";
  }
  else {
  //$displayColumns[$col] = $this->listViewDefs[$module][$col];
  echo "123";
  }
  //new if-else ends here
  }
  } //Global(log)= $this->listViewDefs[$module][$col] /////////
  }
  else {
  //didn't worry about this because UNWANTED_COLUMN_FIELDNAME was not a default;
  //otherwise, if-else this part, too.
  foreach($this->listViewDefs[$module] as $col => $this->params) {
  if(!empty($this->params['default']) && $this->params['default']) {
  
  //new if-else starts here || $current_user->is_admin && $col == "phone_mobile"
  if (in_array('Руководители отделов',$user_roles) && $col == "PHONE_MOBILE") {
  $displayColumns[$col] = $this->params;
  echo "321";
  }
  else {
  //$displayColumns[$col] = $this->listViewDefs[$module][$col];
  echo "123";
  }
  
  }
  }
  }
  parent::listViewPrepare();
  }
  Like • Show 0 Likes0
  Actions
- Anton Dyrdin @ cx_elena cx_elena on Dec 16, 2016 1:52 AM
  Mark Correct
  Correct Answer
  and my code which IS working as for view.detail and view.edit -
  global $current_user;
  $acl_role_obj = new ACLRole();
  $user_roles = $acl_role_obj->getUserRoles($current_user->id);
  if(in_array("Руководители отделов", $user_roles) || $current_user->is_admin || $current_user->id == $this->bean->assigned_user_id)
  {
  echo "Статус Безопасности: Одобрен для просмотра прямых контактов";
  }
  else {
  echo "<style>
  #phone_mobile {
  display: none;
  }
  #email1_span {
  display: none;
  }
  #phone_home {
  display: none;
  }
  #phone_work {
  display: none;
  };
  </style>";
  echo "Статус Безопасности: Прямой контакт не доступен - другой Ответственный агент";
  }
  Like • Show 0 Likes0
  Actions

cx_elena cx_elena Feb 15, 2014 5:02 PM

I am now trying this post by Andre.

The problem is accounts and other modules, are way too different from Leads. So I understand that for hiding custom field from leads module I have to change:

custom/include/MVC/View/views/view.detail.php

I am trying to adopt this:

1. Edit the editviewdefs.php and detailviewdefs.php and convert the panels name to upper case;
2. Create a single metadata file into custom/modules/Leads/metadata/toggle_panel_fieldsdefs.php with the content:
PHP Code:

<?php 
$toggle_panel_fieldsdefs = array( 
    
    'OS_OWN' => array( 
            
            'LBL_CC_INFO' => 1, 
            
//            'PANEL2' => 1, 
            
//            'PANEL3' => 0, 
    ), 
    
    ), 
    'DE_SALES' => array( 
            
            'LBL_CC_INFO' => 0, 
            
//            'PANEL2' => 1, 
            
//            'PANEL3' => 0, 
    ), 
); 
    ), 
); 
?>

3. Modify the role name and panel name to fit your needs; //changed accounts to lead and rest above;
4. Create the file custom/modules/Leads/views/view.detail.php with this content:
PHP Code:

<?php
require_once('include/MVC/View/views/view.edit.php');

class 
class LeadsViewEdit extends ViewEdit {
     function 
     function display() {
        if(empty(
        if(empty($this->bean->id)) {
            global 
            global $app_strings;

            
            sugar_die($app_strings['ERROR_NO_RECORD']);
        }

        require_once(
        }
        require_once('custom/modules/' . $this->bean->module_dir . '/metadata/toggle_panel_fieldsdefs.php');
        
        global 
        
        global $current_user;

        foreach(
        foreach($toggle_panel_fieldsdefs as $role => $field_defs) {
            foreach(
            foreach($field_defs as $field => $visible) {
                foreach(
                foreach($value_defs as $panel => $panel_defs) {
                    
                    $panel = strtoupper($panel);

                    if(
                    if($visible == 0 && isset($this->dv->defs['panels'][$panel]) && $check_role->check_role_membership($role)) {
                        unset(
                        unset($this->dv->defs['panels'][$panel]);
                    }
                }
            }
        }

        
                    }
                }
            }
        }
        $this->dv->process();
        echo 
        echo $this->dv->display();
    }
}
    }
}
?>

4. Duplicate this file to view.edit.php and modify the enough to work for EditView. //not done yet

Problem
The field is still shown after aforesaid :-(

Actions

Jason Eggers Feb 15, 2014 5:08 PM
Mark Correct
Correct Answer
If it is for Leads then you would put the logic to hide fields on the detail view in custom/module/Leads/views/view.detail.php.
Like • Show 0 Likes0
Actions

cx_elena cx_elena Feb 15, 2014 5:36 PM

I added it to
custom/modules/Leads/views/view.detail.php

:UPDATE:
Reading through posts by Kuske did following and warnings are gone but fields are still visible:

<?php  require_once('include/MVC/View/views/view.detail.php');   class LeadsViewDetail extends ViewDetail {       function display() {          if(empty($this->bean->id)) {              global $app_strings;               sugar_die($app_strings['ERROR_NO_RECORD']);          }           require_once('custom/modules/' . $this->bean->module_dir . '/metadata/toggle_panel_fieldsdefs.php');                     global $current_user;          foreach($toggle_panel_fieldsdefs as $role => $field_defs) {             foreach($field_defs as $field => $visible) {                if ($current_user->check_role_membership($role)) {                // role matches panel name:                   foreach($this->dv->defs['panels'] as $panel => $panel_defs) {                      if ((strtoupper($panel) == strtoupper($field)) && ($visible == 0)) {                             unset($this->dv->defs['panels'][$panel]);                      }                  }                  }              }                }          parent::display();           /* CODE FROM ANDRE COMMENTeD         global $current_user;           foreach($toggle_panel_fieldsdefs as $role => $field_defs) {              foreach($field_defs as $field => $visible) {                  foreach($this->dv->defs['panels'] as $panel => $panel_defs) {                      $panel = strtoupper($panel);                       if($visible == 0 && isset($this->dv->defs['panels'][$panel]) && $check_role->check_role_membership($role)) {                          unset($this->dv->defs['panels'][$panel]);                      }                  }              }          }           $this->dv->process();          echo $this->dv->display();          *///CODE FROM ANDRE ENDS     }  }  ?>

Any idea what am I doing wrong?

Actions

Jason Eggers Feb 16, 2014 12:29 PM
Mark Correct
Correct Answer
I believe that method of unsetting the defs only works if you have developerMode turned on or if you bypass the cache somehow. If you don't then it will retrieve what is already in cache/modules/Leads/DetailView.tpl which means that your changes will not show.
Like • Show 0 Likes0
Actions
cx_elena cx_elena Feb 16, 2014 1:14 PM
Mark Correct
Correct Answer
Any way other than developer mode?

Looking for upgrade safe if any or any code?
Like • Show 0 Likes0
Actions
Jason Eggers Feb 16, 2014 6:03 PM
Mark Correct
Correct Answer
You can output javascript and remove the element from the DOM after calling parent::display in view.detail.php. However, this is a client-side hack and isn't completely fool proof. Meaning that if someone in Data Entry disabled javascript or watched the server response they could easily access that field that they shouldn't have access to.

An alternative is to force the detail view to always rebuild the detail view instead of using the cached version. I don't have the code on hand, but there should be examples in the old forums.
Like • Show 0 Likes0
Actions

cx_elena cx_elena Feb 17, 2014 1:02 PM

Finally, I was able to get it to work. Following is the solution:

1. Edit the editviewdefs.php [change constructor to ev] and detailviewdefs.php and convert the panels name to upper case;
2. Create a single metadata file into custom/modules/Leads/metadata/toggle_panel_fieldsdefs.php with the content:

PHP Code:

<?php 
$toggle_panel_fieldsdefs = array( 
    
    'OS_OWN' => array( 
            
            'LBL_CC_INFO' => 1, 
            
//            'PANEL2' => 1, 
            
//            'PANEL3' => 0, 
    ), 
    
    ), 
    'DE_SALES' => array( 
            
            'LBL_CC_INFO' => 0, 
            
//            'PANEL2' => 1, 
            
//            'PANEL3' => 0, 
    ), 
); 
    ), 
); 
?>

3. Modify the role name and panel name to fit your needs; //changed accounts to lead and rest above;
4. Create the file custom/modules/Leads/views/view.detail.php with this content:
PHP Code:

 <?php /*************************************************************************** ** Module /custom/modules/Leads/views/view.detail.php ** ** removes all DetailView panels for which ** $toggle_panel_fieldsdefs[role] matches role of current user ** and $toggle_panel_fieldsdefs[role][panel] = 0 ***************************************************************************/ require_once('include/MVC/View/views/view.detail.php'); class LeadsViewDetail extends ViewDetail {      function LeadsViewDetail (){         parent::ViewDetail();      }      function display() {      /* //need to comment this block for able to create lead else you will get retrieval error         if(empty($this->bean->id)) {             global $app_strings;             sugar_die($app_strings['ERROR_NO_RECORD']);         } /*         // Dirty trick to clear cache, a must for EditView:         if(file_exists('cache/modules/' . $this->bean->module_dir . '/DetailView.tpl'))             unlink('cache/modules/' . $this->bean->module_dir . '/DetailView.tpl');           require_once('custom/modules/' . $this->bean->module_dir . '/metadata/toggle_panel_fieldsdefs.php');           global $current_user;         foreach($toggle_panel_fieldsdefs as $role => $field_defs) {            foreach($field_defs as $field => $visible) {               if ($current_user->check_role_membership($role)) {               // role matches panel name:                 foreach($this->dv->defs['panels'] as $panel => $panel_defs) {                    if ((strtoupper($panel) == strtoupper($field)) && ($visible == 0)) {                           unset($this->dv->defs['panels'][$panel]);                     }                 }                 }             }         }         parent::display();       } } ?>

Now I am supposed to find solution for showing these fields when we create for first time.

Once that is done I can draft complete answer, and moderators can post it as a solution.

Thanks @eggsurplus.

Actions

How can I hide a field based on role from the Leads module in Community Edition?

Outcomes

Related Content

Recommended Content

Incoming Links