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.
#4448 - Dashlet search damaged after Upgrade to 3.1.21
Hello together, after the upgrade from 3.1.18 to 3.1.21 the dashlet search doens't search for other assigned user. If you choose a colleague in the assigned user field, you don't get any results in the Dashlet.
This function is very important for us.
Br, sgi
-
"Absolutely necessary for limiting user visibility."
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
3 years ago
Hello,
This functionality still works in 3.1.21. Can you try the following, please?
Also try clearing the browser cache. See if this works. If not, check your sugarcrm.log (or suitecrm.log) on the server and see what errors may be showing at the end of it. There may be a database error.
If not, which module is this dashlet for?
3 years ago
Which edition of SecuritySuite are you currently on?
3 years ago
I needed to restore the files in the upload folder. It looks like I have now a mix of booth. Files from 3.1.18 in the system and in the module loader overview the 3.1.21
I run the steps many often: Run a Quick Repair & Rebuild and execute any SQL generated Run Rebuild Relationships Run Repair Roles
Br
3 years ago
Here is the failure in the suitecrm.log:
Wed Oct 28 09:08:34 2020[24113][d4387e9f-1c27-f2c5-56fe-5b5eed2be4f3][FATAL][172.16.25.232][][GET]Mysqli_query failed. Wed Oct 28 09:08:34 2020[24113][d4387e9f-1c27-f2c5-56fe-5b5eed2be4f3][FATAL][172.16.25.232][][GET] Query Failed: SELECT project.id , project_cstm.account_id1_c , project.assigned_user_id , project.modified_user_id , jt0.name tg_projects_firma_c , project.name , project.status , project.estimated_start_date , project.estimated_end_date , jt1.user_name assigned_user_name , jt1.created_by assigned_user_name_owner , 'Users' assigned_user_name_mod, project.created_by FROM project LEFT JOIN project_cstm ON project.id = project_cstm.id_c LEFT JOIN accounts jt0 ON project_cstm.account_id1_c = jt0.id AND jt0.deleted=0 LEFT JOIN users jt1 ON project.assigned_user_id=jt1.id AND jt1.deleted=0
AND jt1.deleted=0 where (( (project.assigned_user_id IN ('ad316445-0e7c-fdc1-4837-5e09cdd56521') OR id in (select record_id from securitygroups_additionalusers where deleted = 0 and module = 'Project' and user_id in ( 'ad316445-0e7c-fdc1-4837-5e09cdd56521' )) ) )) AND project.deleted=0 ORDER BY project.estimated_start_date ASC LIMIT 0,6: MySQL error 1052: Column 'id' in IN/ALL/ANY subquery is ambiguous
It seems that the module name is necessary bevor the column id.
I have the same issue in the Dashlets of opportunities, calls, ... whenever I want to filter of an assigned user
3 years ago
Thanks. This is exactly what i needed. Digging into it and I'll report back here shortly.
3 years ago
Here is a temporary, quick fix to get your dashlets back up. This was introduced in 3.1.20 and assumes that a certain variable is set. It's always interesting to see something work well in most every where with SugarCRM/SuiteCRM and then have a single case that things break down. I apologize for the inconveniences heree.
Edit /include/generic/SugarWidgets/SugarWidgetFieldname.php
Look for the code block around line 244 that starts with: /* BEGIN - SECURITY GROUPS - additional-users */
Comment out the whole code block and save. Your dashlet filters will now work. A permanent fix will be available soon.
Thank you!
3 years ago
Thank's. That helps me at the moment.
3 years ago
A new 3.1.22 version is now available for download that fixes this issue. Thanks again for reporting this!
3 years ago
The fix works for me. Thank you very much for your fast solution.