TYPO3 Core

May be also related to: #30354

Well I didn't find the right entry-point for a Core-Patch yet.

1. The ##REC_FIELD_[ ROW-FIELD ] is substituted within t3lib_befunc::exec_foreign_table_where_query.
2. The parsing of different Field-Types for TCA is done in t3lib_flexformtools.
3. Setting a "Dummy" Field within t3lib_flexformtools::traverseFlexFormXMLData (f.e.) doesn't work as t3lib_befunc is accessing the row using $TSconfig['_THIS_ROW']

Anyone having ideas how to solve this?

Of course I could also use an ItemProcFunc on EACH PROJECT I ever need this. But I really think there should be one place to solve this problem and this would be the Core to have a one-place solution that is working for all.

Since this issue/feature seems to be more complicated than I expected, I have to fall-back to itemProcFunc in FlexForm.

I believe we have to patch t3lib_BEfunc::exec_foreign_table_where_query()
as there the REC_FIELD's are substituted.

Too bad - there is no "row" argument used f.e. t3lib_transferdata::renderRecord_flexProc. Instead t3lib_BEfunc::exec_foreign_table_where_query() uses $TSconfig['_THIS_ROW'] build somewhere else.

1. Check if the current-field renderes is inside FlexForm (refer to t3lib_transferdata::renderRecord_flexProc).
2. Map all FlexForm-Values (of course we should respect lDEF and a possible localisation!) to the DB-Row temporarely (for Flex-Field rendering only).
3. May be t3 t3lib-Rendering needs a complete clean-up to have one Storage for the current row?

Any ideas or suggestions are welcome!