Opal Custom Fields API

## Custom Fields Overview Custom Fields let you create custom inputs, the value of which can then be associated with a Moment, and allow your users to track dimensions based on your specific needs. - **[Custom Fields](#tag/Custom-Fields)**: An admin within a workspace can create a custom field to store new attributes on a [Moment](#tag/Moments/operation/CreateMomentV3). - **[Custom Field Types](#tag/Custom-Field-Types)**: The available types of custom fields which an admin can create, such as a Date input. - **[Moment Custom Fields](#tag/Moment-Custom-Fields)**: This resource lets one assign a ``value`` to the given Custom Field for the given Moment. Note that the expected attribute to use on this resource is determined by the [Custom Field Type](#tag/Custom-Field-Types) that the [Custom Fields](#tag/Custom-Fields) is based on. - ``text_value``: A primitive string - ``date_value``: An ISO8601 date-time - ``hash_value``: A JSON object for [Custom Fields](#tag/Custom-Fields) which store complex data structures ### Pairing Multiselect custom fields can be paired with [label sets](/api/documentation/v2#tag/Label-Sets) (`paired_label_set`), with the field’s options paired to the label set’s labels (`paired_label`). Once this pairing is established, the application will automatically do bidirectional syncing: choosing the multiselect’s options will apply the corresponding labels to the moment, and vice versa. Both systems are supported, and the syncing should behave seamlessly, but at some point we will sunset the label system in favor of custom fields. We encourage using custom fields for new development.