---
title: "Feature: #106972 - Configure searchable fields"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-106972-1750856721"
source: "Changelog/14.0/Feature-106972-ConfigureSearchableFields.rst"
typo3-version: "14.0"
typo3-major: 14
type: "feature"
issue: 106972
forge: "https://forge.typo3.org/issues/106972"
tags: ["TCA", "ext:core"]
rendered: "2026-09-28T19:48:07+00:00"
---

# Feature: #106972 - Configure searchable fields {#feature-106972-1750856721}

See [forge#106972](https://forge.typo3.org/issues/106972)

## Description {#description}

TYPO3 now automatically includes all fields of suitable types in
backend search operations, e.g., in the List module.

This eliminates the need for the previously used TCA `ctrl` option
`searchFields`, which has been [removed](https://docs.typo3.org/permalink/changelog:breaking-106972-1750856858).

Instead, a new per-field configuration option `searchable`
has been introduced. It allows integrators to fine-tune whether
a specific field should be included in backend search queries.

By default, all fields of supported types are considered searchable.
To exclude a field from being searchable, set the following in the
field’s TCA configuration:

```php
'my_field' => [
    'config' => [
        'type' => 'input',
        'searchable' => false,
    ],
],
```

Note that until `searchFields` is manually removed from your TCA, the
automatic TCA migration sets all suitable fields, which are not included
in the `searchFields` configuration, to `searchable => false` to
keep current behavior.

### Supported Field Types {#supported-field-types}

The following TCA field types support the `searchable` option and are
automatically considered in searches unless explicitly excluded:

-   `color`
-   `datetime` (when not using a custom `dbType`)
-   `email`
-   `flex`
-   `input`
-   `json`
-   `link`
-   `slug`
-   `text`
-   `uuid`

Unsupported field types such as `file`, `inline`, `password` or
`group` are excluded from search and do not support the
`searchable` option.

## Impact {#impact}

-   Backend search becomes more consistent and automatic.
-   No need to manually maintain a `searchFields` list in TCA.
-   Integrators have more granular control over search behavior on a field level.
-   Custom fields can easily be excluded from search using the `searchable` option.

## Migration {#migration}

If your extension previously relied on the `searchFields` TCA option,
remove it from the `ctrl` section and instead define `'searchable' => false`
on fields that should be excluded from search results.

No action is needed if the default behavior (search all suitable fields)
is acceptable.

## Example {#example}

```php
return [
    'columns' => [
        'title' => [
            'config' => [
                'type' => 'input',
                'searchable' => true, // optional, true by default
            ],
        ],
        'notes' => [
            'config' => [
                'type' => 'text',
                'searchable' => false, // explicitly excluded
            ],
        ],
    ],
];
```