Control what your users can access and save time, money, and frustrations. Lock down sensitive data in SugarCRM or 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.
#2556 - In SuiteCRM
Hi, on a SuiteCRM 7.6.3 istance, i noticed that in Detail View of a custom module even logged in as admin, i can't see the SecurityGroups subpanel. In List View i see it.
-
"I just installen limited SS on sugarcrm CE version 6.5.21 and it seems to work quite well. Have not tested a lot but it looks good." - khobo
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
8 years ago
Is it a custom module that comes with SuiteCRM by default? Some of those modules do not use the view system of the framework and because of that the subpanel doesn't show up as it should. If you created the custom module in Module Builder, those are getting a custom securitygroups relationship added by default somehow. That needs to be removed manually and then "hooked up" to SecurityGroups using the Hookup Module tool. This may be helpful with that: http://www.ricardomalla.com/?p=996
8 years ago
Hi Jason, thanks for the link you provided me, it is a custom person module made with Module Builder. The relationship with SecuritySuite has been automatically added correctly:
8 years ago
It usually isn't automatically created correctly. It never does. It's a very special relationship that requires setting the relationship table to securitygroups_records. If you see that mentioned in the securitygroups_Is_insegnanti custom metadata then perhaps it is set correctly.
8 years ago
Hi Jason, please where and what do you mean it should appear to make SecurityGroup working correctly?
8 years ago
The securitygroups_Is_insegnanti needs to be deleted manually and then the relationship needs to be created correctly. The Hookup Tool does this correctly. If you are doing this manually then this thread will help on how to do that: https://suitecrm.com/forum/suitecrm-7-0-discussion/7796-applying-security-groups-to-custom-modules
8 years ago
I tried to follow them but without success,.. I manually created: custom/metadata/ls_insegnanti_securitygroupsMetaData.php did a Rebuild Relationships, Repair Roles, Quick Repair tried to follow these instructions: http://www.ricardomalla.com/?p=996 to manually delete the relationship but there were no files to delete but the one i created lastly,
i think the problem is that under the Studio > Security Groups > Relationships there is no "default" in the "
Subpanel from Security Group" field
8 years ago
When you add a security group to one of the Is_insegnanti records do you then see it immediately in the securitygroups_records table? If not, can you email me your ls_insegnanti_securitygroupsMetaData.php file, please? If you can, then there is something with the view for that custom module that is causing the subpanel not to show. I've seen this with other modules that do not use the view framework, but instead use the old DetailView.php method.
8 years ago
Thanks Mayer, got your attachment. If you are seeing records in securitygroups_records then the relationship is all set. I would move on an focus on why the subpanels are not showing. Does your custom module use a DetailView.php/html combo instead of view.detail.php?
8 years ago
I send you now the zipped module
8 years ago
That looks good so that then when the relationship was created the subpanel wasn't created. You will need to manually define the subpanel/layoutdefs to make it show for that custom module since Module Builder/Studio failed to create that. This is something that the Hookup Tool does in the paid-for version of SecuritySuite here.
8 years ago
Ok, thank you
7 years ago
I have confirmed that Module Builder creates this relationship automatically now. I'm adding logic to that process to ensure that the subpanel shows as well. This will be in the 2.9.5 release.
7 years ago
Thank you very much for all your efforts
7 years ago
This is fixed for the future 2.9.5 release so that the Hookup Module tool can be used, but it will only apply to future modules built in Module Builder. To fix existing modules deployed by Module Builder:
It should now show the subpanel correctly.