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.
#3576 - When a security group is deleted, the registry of the modules are not deleted
Good morning, We are using SugarCRM 6.5.11 and Security Suite 2.6.4
We have observed that at the time of erasing a security group, the records that so far belonged to this group remain linked to it. The registry of the securitygroups_record table maintains the field deleted = '0'.
Obviously the deleted group no longer appears in sugarcrm or in the registry, but by doing a report with for example Kreporter, you can see that the record maintains the relationship with the deleted group with the blank name.
Is this a possible bug? Is there something we are doing wrong?
Thanks!
-
"The features are exactly what is needed to turn a SugarCRM CE into a Teams based CRM."
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
6 years ago
Hello,
That's pretty typical for how SugarCRM works for any module. KReporter works in other cases because it creates the correct queries that checks for the deleted flag. For whatever reason it isn't checking if the securitygroups record has deleted set to 0. Once that is addressed then your reports should work. I'm not aware enough to know if this is a bug with KReporter or a report design issue, but hopefully this helps.
6 years ago
But, regardless of what we use or not kreporter for reporting, what I want to say is that when a security group is deleted, I understand that all records related to this deleted group (which are in the securitygroups_record table) should be placed with deleted = '1'. This is what all sugarcrm modules do, but these records continue with deleted = '0' although the security group is eliminated. Thanks!
6 years ago
I understand. It's a shortcoming in Sugar's relationship model with this specific type of relationship. I'll look and see if this is still the case in the current Sugar version. For the reports, changing to check that the securitygroup deleted flag is not set should do the trick.