Whether this field is to be considered by the facet generator feature.
Default: true if a facet or multivalue facet field.

A regex indicating the date format, for some date type fields.
Example: %Y/%m/%d@%H:%M:%S%G

A description of the field.
Example: The date of creation of a given item

Whether Group By operations and Facet requests can be performed on the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether the field contains multiple values that form a hierarchy (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

Whether this field can be referred to in Coveo Cloud query syntax expressions.
Default: true

Whether the field can be included in the raw property of query results.
Default: true

Whether field values with differing accents should be considered distinct facet values.
Note: Applicable to field type STRING only.
Default: false

Whether the field is a dictionary field, which contains mappings of keys to values instead of a single value.
Default: false

A displayable label for the field when used by the facet generator.

Whether the field is free text searchable.
Note: Applicable to field type STRING only.
Default: false

Whether the field contains multiple values (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

The character to use as a value separator, if the field contains multiple values (see also the multiValueFacet property).
Example: ;

The name of the field, also referred to as the field identifier, or fieldId.
Note: Must match ^([a-z][a-z0-9_]{0,254})$
Example: Date

Whether to use the field in result ranking calculation only.
Notes:
- Has a significant impact on query performance.
- Applicable to field type STRING

Default: false

Whether to transform date and time string values into semicolon separated number of days/weeks/months/quarters/years since January 1st, 1900.
Note: Applicable to field type DATE only.
Default: false

Whether query results can be sorted based on the value of the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether to allow an item to match the query when the value of this field for this item stems from the same root as one of the query expression keywords.
Notes:
- applicable to STRING type fields only.
- Has a significant impact on query performance.

Default: false

Whether the field is a standard Coveo field.
Note: system option can not be set to true.
Default: false

The data type of the field.
See Field Types.
Allowed values:
- DATE
- LONG
- LONG64
- DOUBLE
- STRING

Whether to keep computed field data in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether to keep the data required to perform nested queries in memory.
Note: only applicable to fields which are faceted or multi-value faceted.
Default: false

Whether to keep the data required to execute operations on numeric and date fields in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether this field is to be considered by the facet generator feature.
Default: true if a facet or multivalue facet field.

A regex indicating the date format, for some date type fields.
Example: %Y/%m/%d@%H:%M:%S%G

A description of the field.
Example: The date of creation of a given item

Whether Group By operations and Facet requests can be performed on the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether the field contains multiple values that form a hierarchy (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

Whether this field can be referred to in Coveo Cloud query syntax expressions.
Default: true

Whether the field can be included in the raw property of query results.
Default: true

Whether field values with differing accents should be considered distinct facet values.
Note: Applicable to field type STRING only.
Default: false

Whether the field is a dictionary field, which contains mappings of keys to values instead of a single value.
Default: false

A displayable label for the field when used by the facet generator.

Whether the field is free text searchable.
Note: Applicable to field type STRING only.
Default: false

Whether the field contains multiple values (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

The character to use as a value separator, if the field contains multiple values (see also the multiValueFacet property).
Example: ;

The name of the field, also referred to as the field identifier, or fieldId.
Note: Must match ^([a-z][a-z0-9_]{0,254})$
Example: Date

Whether to use the field in result ranking calculation only.
Notes:
- Has a significant impact on query performance.
- Applicable to field type STRING

Default: false

Whether to transform date and time string values into semicolon separated number of days/weeks/months/quarters/years since January 1st, 1900.
Note: Applicable to field type DATE only.
Default: false

Whether query results can be sorted based on the value of the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether to allow an item to match the query when the value of this field for this item stems from the same root as one of the query expression keywords.
Notes:
- applicable to STRING type fields only.
- Has a significant impact on query performance.

Default: false

Whether the field is a standard Coveo field.
Note: system option can not be set to true.
Default: false

The data type of the field.
See Field Types.
Allowed values:
- DATE
- LONG
- LONG64
- DOUBLE
- STRING

Whether to keep computed field data in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether to keep the data required to perform nested queries in memory.
Note: only applicable to fields which are faceted or multi-value faceted.
Default: false

Whether to keep the data required to execute operations on numeric and date fields in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether this field is to be considered by the facet generator feature.
Default: true if a facet or multivalue facet field.

A regex indicating the date format, for some date type fields.
Example: %Y/%m/%d@%H:%M:%S%G

A description of the field.
Example: The date of creation of a given item

Whether Group By operations and Facet requests can be performed on the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether the field contains multiple values that form a hierarchy (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

Whether this field can be referred to in Coveo Cloud query syntax expressions.
Default: true

Whether the field can be included in the raw property of query results.
Default: true

Whether field values with differing accents should be considered distinct facet values.
Note: Applicable to field type STRING only.
Default: false

Whether the field is a dictionary field, which contains mappings of keys to values instead of a single value.
Default: false

A displayable label for the field when used by the facet generator.

Whether the field is free text searchable.
Note: Applicable to field type STRING only.
Default: false

Whether the field contains multiple values (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

The character to use as a value separator, if the field contains multiple values (see also the multiValueFacet property).
Example: ;

The name of the field, also referred to as the field identifier, or fieldId.
Note: Must match ^([a-z][a-z0-9_]{0,254})$
Example: Date

Whether to use the field in result ranking calculation only.
Notes:
- Has a significant impact on query performance.
- Applicable to field type STRING

Default: false

Whether to transform date and time string values into semicolon separated number of days/weeks/months/quarters/years since January 1st, 1900.
Note: Applicable to field type DATE only.
Default: false

Whether query results can be sorted based on the value of the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether to allow an item to match the query when the value of this field for this item stems from the same root as one of the query expression keywords.
Notes:
- applicable to STRING type fields only.
- Has a significant impact on query performance.

Default: false

Whether the field is a standard Coveo field.
Note: system option can not be set to true.
Default: false

The data type of the field.
See Field Types.
Allowed values:
- DATE
- LONG
- LONG64
- DOUBLE
- STRING

Whether to keep computed field data in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether to keep the data required to perform nested queries in memory.
Note: only applicable to fields which are faceted or multi-value faceted.
Default: false

Whether to keep the data required to execute operations on numeric and date fields in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether this field is to be considered by the facet generator feature.
Default: true if a facet or multivalue facet field.

A regex indicating the date format, for some date type fields.
Example: %Y/%m/%d@%H:%M:%S%G

A description of the field.
Example: The date of creation of a given item

Whether Group By operations and Facet requests can be performed on the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether the field contains multiple values that form a hierarchy (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

Whether this field can be referred to in Coveo Cloud query syntax expressions.
Default: true

Whether the field can be included in the raw property of query results.
Default: true

Whether field values with differing accents should be considered distinct facet values.
Note: Applicable to field type STRING only.
Default: false

Whether the field is a dictionary field, which contains mappings of keys to values instead of a single value.
Default: false

A displayable label for the field when used by the facet generator.

Whether the field is free text searchable.
Note: Applicable to field type STRING only.
Default: false

Whether the field contains multiple values (see also the multiValueFacetTokenizers property).
Note: Applicable to field type STRING only.
Default: false

The character to use as a value separator, if the field contains multiple values (see also the multiValueFacet property).
Example: ;

The name of the field, also referred to as the field identifier, or fieldId.
Note: Must match ^([a-z][a-z0-9_]{0,254})$
Example: Date

Whether to use the field in result ranking calculation only.
Notes:
- Has a significant impact on query performance.
- Applicable to field type STRING

Default: false

Whether to transform date and time string values into semicolon separated number of days/weeks/months/quarters/years since January 1st, 1900.
Note: Applicable to field type DATE only.
Default: false

Whether query results can be sorted based on the value of the field.
Default:
- false for STRING type fields.
- true for all other types of fields.

Whether to allow an item to match the query when the value of this field for this item stems from the same root as one of the query expression keywords.
Notes:
- applicable to STRING type fields only.
- Has a significant impact on query performance.

Default: false

Whether the field is a standard Coveo field.
Note: system option can not be set to true.
Default: false

The data type of the field.
See Field Types.
Allowed values:
- DATE
- LONG
- LONG64
- DOUBLE
- STRING

Whether to keep computed field data in memory.
Note: Cannot be enabled on STRING type fields.
Default: false

Whether to keep the data required to perform nested queries in memory.
Note: only applicable to fields which are faceted or multi-value faceted.
Default: false

Whether to keep the data required to execute operations on numeric and date fields in memory.
Note: Cannot be enabled on STRING type fields.
Default: false