by eggsurplus

Control what your users can access and save time, money, and frustrations. Lock down sensitive data in SuiteCRM to specific groups or teams. Supports unlimited assigned users, unlimited group assignments to records, custom layouts for each group, login/sudo capabilities and much more.

Free 30 day trial
Try it Now

#1655 - unable to deploy multiple "Assigned to" field in Projects module

In Progress Bug? created by mta 3 years ago

We are trying to use FrontEnd Implicit to sync emails to custom modules --- we were given a solution by your team via Ronnie at Frontend Implicit to properly configure the Security Groups for custom module.

However, when I attempt to create the correct relationships for Security Group following your support, -- no Projects module can be found -- Project Holidays, Project Templates, and Task Templates can be found but now Projects

In Frontend Implicit, Projects is not considered a default module, so you need to access it via 'custom' module feature.

I believe that SugarCRM dropped Projects as a core module - but SuiteCRM did not -- so Frontend doesn't see it as a default module since they are frist writing to SugarCRM and SuiteCRM is a compatible app but requires some adjustments (eg. Teams v. Security Suite)

As a workaround, we thought we would bypass the need for syncing records that are owned by the group but not 'assigned to me' but employing the multiple assigned to user feature of Security Suite Pro.

unable to deploy multiple "Assigned to" field in Projects module

I can see the field in Studio>Accounts>Layouts>Edit View --- but I can't see the field in Studio>Projects>Layouts>Edit View - the assigned to field is labelled as 'Project Manager' but that should be the Assigned to Field as it is a 'User' module relationship.

  1. eggsurplus member avatar

    eggsurplus Provider Affiliate

    3 years ago

    Dug into this and found that SuiteCRM has made the Project module not assignable. This is why that additional assigned users field doesn't show in Studio. To change this for your own purposes you can edit /modules/Project/vardefs.php and change the last line of the file to:

    VardefManager::createVardef('Project', 'Project', array('assignable','security_groups',));

    Then do a Quick Repair & Rebuild.

    Hope this helps!

  2. mta member avatar


    3 years ago

    Thanks Jason,

    Is this a bug that should be submitted to the community - or would it be a CUSTOM edit - ie /custom/modules/Project/vardefs.php?

    • eggsurplus member avatar

      eggsurplus Provider Affiliate

      3 years ago

      It's not really a bug as it is intentional that a Project isn't assignable. Typically it is the tasks within a project that need to be assigned. However, I can see how that may be useful in some cases. There isn't a great way too make this change in an upgrade-safe manner thus my recommendation to edit the core file directly. However, if you manually add the assigned user id/name field to the Ext directory like typical new vardefs then that would also enable the additional assigned users field to show.

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
  • "Thank you so much. Highly recommend the module to work in teams."

    Read More Reviews