02-22-2016 05:48 PM
I'm noticing an issue in v18 Web Premium where in a field where you have a drop down list of multiple Yes/No items where there are checkboxes, it doesn't always have the checkmark even though you have selected it. The description or word that describes that checkmark/box is in the field itself, so it is set to YES but the box is missing the checkmark.
Using IE11, Windows 10.
02-23-2016 07:26 AM
02-26-2016 06:55 AM
Logged as Defect D-04280
We couldn't replicate this issue in Chrome.
Including the defect report:
APFW Multi-Select Dropdown Issue
Steps to recreate:
1. Browse to any contact Detail view
2. Change ID/Status field to select only 'contractor'
4. Refresh page
5. Change ID/Status to add Gate Keeper to the existing selection so both are selected
7. Refresh page
8. Click ID/Status dropdown
The 'contractor' checkbox appears checked The 'gate keeper' checkbox appears unchecked
Both checkboxes appear checked
ACT! (Full build): Act! Premium (Web) Version 18.0.501.0, Update 6
Operating System: All supported operating systems
Any additional information / Workaround:
Selecting another item in the dropdown after experiencing the missing checkmark, will replace the value of the missing item in the field heading. I.e. Field shows "Contractor;Gate Keeper", where the Gate Keeper checkmark is missing, selecting "Friend" results in the field showing "Contractor;Friend" and Gate Keeper disappearing.
Interestingly, we could only replicate this issue with the Gate Keeper option in ID/Status.
02-29-2016 09:54 AM
It's a commonly used name for a PA/receptionist who makes it very difficult (sometimes impossible) to get through to their boss who you need to speak to.
04-27-2016 06:16 AM
04-27-2016 06:43 AM
05-27-2016 11:55 AM
I see the issue still exists even with all the latest updates/fixes. What happens is that if you have several multi-select fields in a contact layout, sometimes, selecting one option in a multi-select field will blank out the entry in another multi-select field. Ironically, it doesn't happen consistently but happens frequently enough. I've been trying to pinpoint what the culprit might be but have been unsuccessful.
Do we have an update on this bug as it was previously mentioned and identified.
05-31-2016 04:39 AM