#75017Search for relations in backend
Description
Hey there,
I’ve got a feature request for the TYPO3 backend list module: Search for relations.
An example:
I’ve got two tables: “car” and “manufacturer”.
Every “car” has a relation to the “manufacturer” (every car has one or more “manufacturer” for example).
Now, the backend user wants to list all cars from the manufacturer “VW” for example and search for “VW”.
-> This does not work until now
(This is a really unexpected and strange behaviour for the users…)
The reason is: the TYPO3 backend searches only in the table “car”, in fields with the TCA config type “text”, “flex” and “input” (see \TYPO3\CMS\Recordlist\RecordList\AbstractDatabaseRecordList::makeSearchString).
What do you think? Should there a feature like this? Will this feature be added to the core if I contribute it?
Regards,
Markus
Reviews 1
Related issues 6
- Feature #40689Filter for list-view
- Story #82206list module enhancements/bugfixes
- Bug #83261List View sorting by category is done by category id instead of titles
- Epic #93547Collection of problems with large sites
- Feature #98490Introduce PSR-14 event for DatabaseRecordList
- Bug #107796Add table in searchContraint for DatabaseRecordList
History 1720
-
Benno Flory commented <span data-processor="relativetime" data-value="2016-06-22T11:01:55+00:00" > 06/22/16, 11:01 </span>
We have the same requirement from current customers, e.g. orders <-> customers. Would be great to implement that asap…
If we want a workaround now, we would have to implement a custom backend module, right? -
Gerrit Code Review pushed patch set 1 for master to change 49341 status
NewUnder Review <span data-processor="relativetime" data-value="2016-08-03T12:46:57+00:00" > 08/03/16, 12:46 </span> -
Markus Hölzle changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2016-08-03T14:13:42+00:00" > 08/03/16, 14:13 </span>
-
Gerrit Code Review pushed patch set 2 for master to change 49341 <span data-processor="relativetime" data-value="2016-10-08T11:27:09+00:00" > 10/08/16, 11:27 </span>
-
Gerrit Code Review pushed patch set 3 for master to change 49341 <span data-processor="relativetime" data-value="2016-10-24T11:45:04+00:00" > 10/24/16, 11:45 </span>
-
Susanne Moog changed Sprint Focus
On Location Sprint<span data-processor="relativetime" data-value="2017-07-11T20:06:11+00:00" > 07/11/17, 20:06 </span> -
Markus Hölzle changed Related to #83261 <span data-processor="relativetime" data-value="2017-12-11T10:08:19+00:00" > 12/11/17, 10:08 </span>
-
Susanne Moog commented and changed status
Under ReviewNew <span data-processor="relativetime" data-value="2019-03-01T18:59:19+00:00" > 03/01/19, 18:59 </span>Review was abandoned.
-
Susanne Moog changed category <span data-processor="relativetime" data-value="2020-03-24T19:22:45+00:00" > 03/24/20, 19:22 </span>
-
Daniel Windloff changed Related to #82206 <span data-processor="relativetime" data-value="2020-09-01T23:04:50+00:00" > 09/01/20, 23:04 </span>
-
Jan Kornblum commented <span data-processor="relativetime" data-value="2024-05-28T11:37:42+00:00" > 05/28/24, 11:37 </span>
I think this still would be an important improvement! Especially if implementation also would optimize TCA “select” fields (selectMultipleSideBySide), to be able to filter items by their relations. I currently have to deal with ~30.000 “event” records which have <n:1> relations to “seminar” and “location”. Due to the missing possibility to search records by those relation columns, it is very hard to access specific records using the standard BE list module or to assign specific records to e.g. „ selectMultipleSideBySide“ fields :(</n:1>
-
Jan Kornblum changed Related to #93547 <span data-processor="relativetime" data-value="2024-05-28T17:58:12+00:00" > 05/28/24, 17:58 </span>
-
Benni Mack changed Tags ux-decision <span data-processor="relativetime" data-value="2025-04-01T13:14:55+00:00" > 04/01/25, 13:14 </span>
-
Markus Klein changed Related to #98490 <span data-processor="relativetime" data-value="2026-04-27T15:20:04+00:00" > 04/27/26, 15:20 </span>
-
Markus Klein commented <span data-processor="relativetime" data-value="2026-04-27T15:21:08+00:00" > 04/27/26, 15:21 </span>
We used to implement this in v11 with the hook
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'][DatabaseRecordList::class]['makeSearchStringConstraints']This allowed us to add SQL like `‘EXISTS (SELECT …)’` to the inner “OR” query.
Unfortunately, this was replaced with an insufficient event with https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-98490-VariousHooksAndMethodsChangedInDatabaseRecordList.html#breaking-98490-various-hooks-and-methods-changed-in-databaserecordlist.
One must now kind of search the querybuilder to replace the correct OR-constraints with the enriched one. :-( -
Markus Klein changed Related to #107796 <span data-processor="relativetime" data-value="2026-04-27T15:25:14+00:00" > 04/27/26, 15:25 </span>
-
Georg Ringer changed Duplicated by #104819 <span data-processor="relativetime" data-value="2026-10-22T18:12:18+00:00" > 10/22/26, 18:12 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-12T19:24:49+00:00" > 11/12/26, 19:24 </span>closing in favor of #40689
-
Georg Ringer changed Related to #40689 <span data-processor="relativetime" data-value="2026-11-12T19:24:58+00:00" > 11/12/26, 19:24 </span>
This part of the core should be migrated to doctrine before we can implement this feature (to avoid implementing this twice).
See #76259