Hi Zoe,

Multi-select custom fields are not stored in the ticket_custom_field table. Instead, each multi-select custom field is synced to its own dynamically-named table with the format ticket_field_{field_name}, where {field_name} is the lowercase version of the field's raw title. This approach supports the many-to-many relationship required by multi-select fields, since each ticket can have multiple selected values for a single field.

Example: If you have a multi-select field named "product_categories", you will find its data in the table ticket_field_product_categories. The structure of these tables includes:

• field_id: Primary key

• ticket_id: Primary key

• index: Primary key (position of each selected value)

• value: The actual selected value

This design is intended to allow proper normalization and querying of multi-value fields. You can locate multi-select field data in these dedicated tables, rather than in ticket_custom_field.

If this is not what you see, please let us know.

Thanks,

Shiva