by eggsurplus

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.

Free 30 day trial
Try it Now

#844 - "Hooking" custom modules to SecuritySuite

Closed General Question created by Stefan Verified Purchase 5 years ago

I'm using SuiteCRM and their custom sales modules (i.e. quotes, contracts, invoices...) are not related to SecuritySuite. If I use the "Hookup Module" functionality to relate them (funny enough, it fails the first time and succeeds the 2nd attempt), the values in the "securitygroups_records" table seem to be reversed i.e. "securitygroup_id" field contains the related record id, the "record_id" field contains the security group id and the "module" field contains "SecurityGroups" instead of "Quotes" for example. Is this by design? I ask because if it is, how do you know which table that related record comes from?

  1. eggsurplus member avatar

    eggsurplus Provider Affiliate

    5 years ago

    Very interesting. Do you see this if you create a module in Module Builder, deploy, then hookup to SecuritySuite?

  2. staganyi member avatar

    Stefan Verified Purchase

    5 years ago

    I will try and post back my findings.

  3. staganyi member avatar

    Stefan Verified Purchase

    5 years ago

    Just created a custom module and hooked it up and looks like it's doing what it should: "securitygroup_id" contains the security group, "record_id" contains the record id of my custom module and the "module" field contains "Test1_Test1Module1". I checked the relationships in studio and it put "Security Groups" as the primary module and "Test module" for the related module (I checked and it's the same for accounts). For "Quotes", it put "Quotes" as primary and "Security Groups" as the related module.

  4. eggsurplus member avatar

    eggsurplus Provider Affiliate

    5 years ago

    So odd. Not sure why the Quotes one is all wonky. My guess is that those modules were hand created and not done in a way that mimics Module Builder. My suggestion for now would be too look at that custom SecurityGroup/Quote relationship in /custom/metadata and flip the values in that file so that it goes into the right spot. That would require a Repair Relationship afterwards.

    • vishal.mehra member avatar

      vishal.mehra Verified Purchase

      4 years ago

      What all files do you have to change to make this happen?

    • vishal.mehra member avatar

      vishal.mehra Verified Purchase

      4 years ago

      Figured it out. Not only did we had to change the lhs and rhs on the relationship, but also had to change the relationship_role_column_value value accordingly to point to the custom module name.

  5. staganyi member avatar

    Stefan Verified Purchase

    5 years ago

    Manually changing it seems to have worked. Going forward, if I simply create the relationship myself in studio, do I need to do anything else or is that all there is to the "Hookup Module" functionality?

    • eggsurplus member avatar

      eggsurplus Provider Affiliate

      5 years ago

      Creating the relationship in Studio to SecurityGroups just doesn't work. It fails miserably at it. The Hookup tool is meant specifically for that so that it creates the relationship correctly.

  6. staganyi member avatar

    Stefan Verified Purchase

    5 years ago

    Ok good to know. You can close this off.

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
Rating
Rating
  • "The features are exactly what is needed to turn a SugarCRM CE into a Teams based CRM."

    Read More Reviews

Keep up to date on the latest additions

We'll send you an email every month with handpicked add-ons, reviews, tricks and tips. Don't worry, we hate spam as much as you do.