Providing admins the ability to choose what we prefer would be even better. I don’t know how these sorts of small yet major changes get made, considering it affects internal documentation & training, user behaviour, etc. These are the sorts of things that should be raised with the CS Ops Product Council as well cc @ophirsw @sshroff agreed? @bradley @sarahmiracle @toddmassey @darshana.shah @rachelhibbardtmo ?

As an end-user I want a checkbox because as far as I’m concerned it’s checked or not checked.

As an admin, easily distinguishing between ‘not checked’ and ‘null’ is depressingly important. To that end the checkbox is a little less appealing unless that distinction can be clearly made. 

Get’s a bit more complicated in reporting - for a low volume object for end users to edit checkbox all the way. But as an admin again, seeing those nulls is critical. But users should have a consistent experience regardless.

I like @gunjanm ‘s idea of choice or some kind of personalization. Not sure the best way to do it but I’d hope there’s a clever way to solve for both use cases.

We Just rolled out the new C360 and have a number of check boxes our team inputs for attributes tracked.  It is not a good user experience for the true/false dropdown vs seeing the checkbox. Please work to update this option.  Thanks!

To add to this, we’re having issues with one of our data exports because of ‘null’ values in boolean fields. We have a default set to ‘false’ but somehow even on the old c360 a user was able to change it. Allowing users to select anything other than true or false to set the value seems more like a bug than a feature (especially in Horizon C360). cc @minh_phan 

+@Dheepak G, @ophirsw

+1 from Moveworks @aurelia_wollen 

Adding my support to this - it’s great to work with the true/false values on the backend but end users overwhelmingly prefer to view and interact with the checkboxes.

@Dheepak G @ophirsw @anirbandutta is there any update to this? On the new 360 experience users can now select one of three options: 

Can we at least have a middle ground where we can make “non” non-selectable or something? We want a True/False option for end-users to select, like they have on the legacy 360 layouts. 

A quick update on this thread, We are going to revert the display experience back to checkbox for boolean fields in the revamped 360 experience post our July Release. I will keep this thread updated on the exact dates for the same.