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.
#339 - can' t assign products to a group
Hello, We are using SecuritySuite - Premium Edition /6516_Premium_SecuritySuite_268/. We have a problem when we try to assign products to a security suite group. We have created a group and we have created a role. We have set permissions for the role as in your tutorial video: https://www.youtube.com/watch?v=yJ-BzM3GTgA We have set Group access to every field from products (without import and mass update). We have assigned a users to the role and to the group. I have assigned products to the security group, but when I login as a user from the group I don’t see any products. I tried the same with accounts and it worked, with the same groups and roles, but it doesn’t work for products. Do you have any suggestions why it is not working for products?
-
"I can say that it has been one of the best modules within our SugarCRM CE instance!"
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
10 years ago
Products isn't a core module in CE. Are you using the AOS module for products? When you link custom (non-core) modules to SecurityGroups it requires a special way of doing so. If you use the Premium version available here, you can click on the Hookup Tool to correctly relate security groups to any custom module that you have. If on the Basic version, then you must do some custom coding to pull this off. You can follow the example code in this doc for manually hooking up modules: http://www.sugarforge.org/frs/download.php/6477/SecuritySuite_Documentation_2.1.pdf. Be careful though to not just copy and paste. That doc adds some junk characters that will cause errors.
10 years ago
We use AOS module for the products. We are using the premium version of the plugin and we have hooked up the module but it isn't working. We have a test server where we have installed the same plugin and we have made the same groups and roles and there it works.
10 years ago
That means that it either wasn't hooked up properly or that AOS is not using the core way of accessing data, which I doubt. Did you use the hookup tool in the Premium version? If not, did you follow the doc on how to do it? It is not as simple as simply adding a relationship in studio.
10 years ago
We used hookup tool in the Premium version. Can you tell me what is the name of the table in the database where I can check if the hooked up was successful?
10 years ago
When you add a group to a product it should go in the securitygroups_records table. Filter the table by the module column to find the ones just for products. It'll be the internal module name. Perhaps AOS is using a hard coded query. If so, then there isn't a way for SecuritySuite to work properly with it unless some coding is done. The AOS folks do have SecuritySuite working with AOS so I'm not sure what's going on then.
10 years ago
I checked the securitygroups_aos_products_1_c table and the relation between the group and the products is created in the database.
10 years ago
That's the problem. It needs to be in securitygroups_records. So what it looks like happened is that a relationship was added manually in Studio and then the Hookup Tool was used afterwards, but the subpanel shown is the relationship that was manually added.
I would suggest removing all relationships between groups and products. Then run a Quick Repair/Rebuild and Rebuild Relationships. Then use the Hookup Tool.
10 years ago
Should I remove the relation in Studio?
10 years ago
How can I unhook the module and hook up it again? Should I delete the relation in the database?
10 years ago
It can be a bit tricky. This is the best guide that I can find on how to do that: http://redinkdesign.co/blarg/remove-sugarcrm-custom-relationship/
The relationship name should be similar to that table in the database that got created: securitygroups_aos_products_1_c
10 years ago
Thank you for the help! The problem was really in the relations, because first we have created a relation in studio. Now it works. Thank you very much!
10 years ago
Glad that you got it figured out! That can be really tricky sometimes.