Anyone else have the Selected=1 issue, which means on your records, it will show as selected:1 as if something is already checked. This causes the inability to update any records.
The only way I can seem to resolve is to clear my browsing history/cache, and then kill all sessions of Chrome. I also typically need to kill my google extensions.
Any ideas? This is affecting all users within our company at different locations and on different networks/machines.
Can you post a screenshot?
If you select any record in SuiteCRM, it will show as selected and say the amount that is selected. Mine shows as having an item selected, with nothing being checked. If that happens, I can’t update any record as it won’t save. I realized google extensions on chrome for some reason seems to cause the conflict but other things might as well. So if we clear browsing history/cache/sessions, and go back into SuiteCRM, nothing is preselected and it works.
It’s really odd. No idea why we seem to be the only group having the issue. I manually selected something to show what I mean since I cleared my cache so it’s not selecting by default now, but it shows exactly like that automatically with no selections.
Here is another showing nothing is selected, but it still shows as selected. When this happens, we can’t make any updates to anything.
Are we the only people with this issue? I wonder if its something server side causing the issues, since this is affecting all of us in the company on different networks/browsers/computers.
Our CRM is hosted on a linux shared server on 1and1. Everything else works fine.
Any ideas any SuiteCRM experts? Please!! 
Really need to get this resolved and not sure where to start 
Hello,
I haven’t yet brought this up because I’m testing and working out other issues. The new interface so far has compatibility issues. It appears it was developed with FF in mind. So far, compatibility is best with the Gecko engine (Firefox, etc.) I’ll see if I can reproduce the issues today and report back.
======
Had to come back and do a quick edit. I see what’s happening. Record one (1) is defaulted. I’ll look into it today. I came across this issue in JQuery documentation: Webkit (Chrome) vs. Trident (IE) vs Gecko (FF). I’ll run some tests today and report back.
Thank you,
– MMS
Excellent, thank you very much for your assistance!
Hello,
RE: Selected=1 issue? HELP NEEDED!
It’s not a browser issue although there are some new changes with the themes. Reviewing the layout from the screenshot reveals the account you’re using isn’t admin and if I’m mistaken I apologize.
A couple of things, the issue could be (i) with a recently installed module because the selection is defaulted to record 1. Following-through in the Chrome console does show some issues where I would question SalesAgility, but nothing that would render or manipulate the default selection in this way. (ii) Some form-fillers can render a selection including Chrome , but it appears different in this case. (iii) Administrators and other users could’ve installed modules which would’ve affected the network in whole and the installation of modules require administrator access unless otherwise adjusted.
Now the real technical stuff. It appears also as an orphaned record meaning a problem with the database where a record was mis-applied (saved without relating to a Key.) Losing a WI-FI connection or internet connection can also cause this. Create a back-up before applying the next steps. You can view the log for errors by navigating to the Administrator section, System Settings, scroll to the bottom and click on view log. Otherwise you’ll need to navigate the framework via SSH. In the Administrator section, choose Repair and please try:
(i) Quick Repair and Rebuild
Check the results –
(ii) Rebuild Config File
Check the results –
(iii) Rebuild Relationships
Check the results –
I would express something about webhosts, unless an actual platter or server block is purchased from the host service provider, it will always exist as a container on a shared server. There’s nothing wrong with this until expressed permissions and access is needed and then it’s often an issue. Be advised that, you may not have the necessary access to correct the problem, but attempt the above steps first before sounding the alarm.
Thank you,
— MMS
Thanks for the assistance. I have done Quick Repair and Rebuild, Rebuild Config File, and Rebuild Relationships after noticing this issue, without resolution. I am currently trying to system with AJAX disabled for all modules to see if that helps for some reason.
My account is a System Administrator account.
Could a 3rd party module perhaps cause this? I know I added Super-Timesheet version 5.8.0 since launch. I have some others but I’m pretty positive I added them after I started noticing the issue. They include Dynamic Dropdown, QuickCRM Mobile Basic and SugarCRM Desktop Notification.
Does the fact that clearing the Google cache and killing existing sessions of Chrome temporarily resolving the problem say anything to the possible causes by any chance?
Hello,
RE: Selected=1 issue? HELP NEEDED!
Well last night I wondered about specific issues being the cause. Just performing follow-up on responses I noticed there could’ve been some issues with Chrome because Chrome has a built-in form filler that, at times act like a macro. On some websites, Chrome would attempt to pre-process form submissions resembling a Macro. I’ll research the information and report back. I doubted the repair processes would be of use because I noted on another issue they are not and it appears to be using SQLite not MySQL (another dilemma.)
Thank you,
— MMS
Hello,
RE: Selected=1 issue? HELP NEEDED!
Right-away you do have one (1) incompatibility: Super-Timesheet. I included documentation on the issue.
I can’t test the Desktop Notification and the other two: Drop-down and Mobile doesn’t cause any issues.
Thank you,
— MMS
[quote=“mariostevenson” post=19008]Hello,
RE: Selected=1 issue? HELP NEEDED!
Well last night I wondered about specific issues being the cause. Just performing follow-up on responses I noticed there could’ve been some issues with Chrome because Chrome has a built-in form filler that, at times act like a macro. On some websites, Chrome would attempt to pre-process form submissions resembling a Macro. I’ll research the information and report back. I doubted the repair processes would be of use because I noted on another issue they are not and it appears to be using SQLite not MySQL (another dilemma.)
Thank you,
— MMS
I did see that thread earlier, however I wasn’t sure if that confirms issue since they say it’s compatible with Sugar 6.x, which SuiteCRM is based on Sugar 6.x, so I assumed it would. However I can disable SuperTimesheet and see if the problem goes away.
Hello,
RE: Selected=1 issue? HELP NEEDED!
Your current SCRM version should be Version 7.2.0 Sugar Version 6.5.20 (Build 1001) which Super-Timesheet declares the 7.x version having incompatibilities. Some of the issues are AJAX related. If you could report back the result because the documentation does declare uninstalling and then reinstalling the plugin may resolve the issue.
Thank you,
— MMS
So today I realized disabling AJAX made no difference, so I finally went ahead and disabled SuperTimesheet after I got the Selected:1, and after I cleared the cache, it went away (normally I would need to clear cache and kill all chrome sessions, I didn’t need to after disable).
Only time will tell if this truly resolves it though. I will monitor the next few days and see if it pops back up. If it doesn’t, SuperTimesheet was the issue!
Still no luck resolving this. It wasn’t SuperTimesheet causing the issue as it came back after it was uninstalled.
