Checkbox

The Checkbox field is on or off (technically, that means true or false, so-called Boolean). Its meaning depends on the label e.g. Checkbox "PermissionDenied" ✔ means permission denied, whereas checkbox "PermissionApproved" ✔ means permission granted, although the checkbox in both cases has the same value (true), the understanding is different based on the label.

Checkbox Overview

Icon
Checkbox Off (Disabled)
Checkbox On (Enabled)
Checkbox read-only display
Behavior
Examples	"Release Signed" to denote whether a release has been signed or not for the photo in question.
Usage considerations	The search does not search for the label, but only the value which is true/false for a checkbox. The same applies to filters, where checkbox values are shown as true/false. Here the filter name should mirror the checkbox label to give some indication of what true/false refers to. An issue of checkboxes is the missing NULL state. When searching for checkbox = false, this will deliver all content items which have the checkbox set to false or have not been set at all. If the checkbox is "legally approved" then false could mean not approved or not yet checked for approval, a combination of checkboxes (checkbox1: legal approval done, checkbox2: legally approved) brings clarity.

Checkbox Value Handling

Picturepark Setup Example	Layer: Corporate Information (ID: CorporateInformation) Field: Legally approved (FieldId: legallyApproved)
Fieldpath	corporateInformation.legallyApproved
Advanced searches	Page: Search: Find Items with Checkbox Values (Solutions) — This will find all content items with the checkbox legally approved set to true. _exists_:corporateInformation.legallyApproved:true This will find all content items with checkbox legally approved set to false or checkbox not set. _exists_:corporateInformation.legallyApproved:false advanced-queries advanced-search checkbox solution examples
Use in Display Pattern	Page: Display Pattern: Checkbox (Solutions) — Show a message “This is approved!” when a checkbox (Id: legallyApproved) on a Layer (Id: corporateInformation) is checked. {% if data.corporateInformation.legallyApproved == true %} This was approved! {% endif %} solution examples display-pattern field checkbox
Returned field value	True / False Please note Picturepark does not have a NULL state for checkboxes, which would indicate that the checkbox was never updated. Please consider displaying information based on the checkbox value instead of just showing the value e.g. if true, show "it works".

Checkbox Field Settings

Name	The label of the checkbox, which basically determines whether the checkbox must be switched on or off. Label: Approved, requires checkbox to be enabled for approval Label: Not approved, requires checkbox to be disabled for approval
ID	The ID field is the ID of your field, which is used to link to this field. The field ID is always lowercase. The field's ID is set when creating a new field using camel casing. You need the field ID for the configuration of filters or display patterns. The ID is automatically created from the name you insert: Example: You insert the field name "My NeW fielDs #1 Purpose? Automatic Id: myNeWFielDs1Purpose You can open the Display Pattern Editor to see the JSON of a Content Item.
Sortable	The Sortable field setting defines if Picturepark uses the values of those fields for sorting List Items (in Lists). Sorting of contents based on fields in a Layer is possible via the channel configuration, which only considers fields marked as sortable. All fields except for Geo Point and Relationship fields are sortable. This can be changed after field creation.
Include in filters	The Include in filters field setting allows the field to be added as a filter for content (see Channels Configuration) and the field values to be edited in the Batch Editor (indexed fields). Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit and by testing your common search scenarios - too many values will not automatically result in better search results. Will always have included in the search and filters set to true per default on creation. You can change this if you don't want to use the checkbox in channel filters.
Include in search	The Include in search field setting determines whether or not the field's values should be considered in content browser simple search operations. If this option is not enabled, the search does not consider the values of the field in search operations. This can be useful, for example, if the field is used for internal discussions or work directives that you don't want to affect the search results. Picturepark checks those settings against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search boosting them, you may revisit this idea based on your subscription plan limit. The simple search in the content browser cannot be used to find true or false values. In such a case, we recommend using an advanced search or adding a channel filter.
Boost value	n/a