Single Checkbox Fields Should Not Have Null Values / Create a Boolean field

Status: Idea Submitted

Background:

Per the Hubspot knowledge base, Single Checkbox fields only store 2 options.

This is not true however, as it can be set as a null value. This makes it no different than a dropdown select field but with limited options.

This issue is further proven by the fact that single checkbox field appears as a dropdown in the record UI as it can not be a checkbox if null values are available.

Solution 1:

I propose that hubspot set the Single Checkbox field as a boolen value of yes/no as defined in their knowledge base and create a merging tool upon release that allows system administrators to choose whether their existing single checkbox fields should change to the new “single checkbox field” field type or be merged into a dropdown select field.

Solution 2:

Alternatively, a new boolean field with options to make it appear as a radio button or checkbox would fix this issue.

Solution 3:

Add an option to the dropdown select and single checkbox fields where the field can be set to a default value and where it could be set to manditory.

Who: System Administrators

Goal: Have boolean yes/no fields

Value: Keeps data integretity by having the correct value options for fields. Creates uniformity of properties between UI records and forms.

Examples:

Microsoft Dynamics

Dynamics.JPG

SAP B1 uses valid values which is the same as a dropdown select field with options to set a default value and to make the field manditory.