#106843Problem with FlexFormFieldValues with settings.something fields inside Fluid
Description
Scenario:
A FlexForm field defines two Sheets “A” and “B”.
Inside “A” there is a field called “settings.field_alpha“
Inside “B” there is a field called “settings.field_beta”
Now, inside a Fluid template I want to access one of those values:
{flexField.settings.field_alpha}
This triggers the error:
TYPO3\CMS\Core\Domain\Exception\FlexFieldPropertyException
Given id is ambigious since the field exists in multiple sheets and no sheet is defined.
The root problem is, that Fluid wants to first access “settings” (which is ambigious), and only then “field_alpha”.
In PHP code this would work without problems:
$flexField->get(‘settings.field_alpha’);
Workaround:
Use Fluid variables to “trick” Fluid and pass the sheet to distinguish the path:
<f:variable name="path" value="A/settings"></f:variable>
{flexField.{path}.field_alpha}
Solution:
The ideal solution would of course be to “teach” Fluid to access the full path identifier as a whole.
However, a new syntax would be required for that only to fix this one specific use case.
Another idea would be to allow only “settings” to exist in multiple sheets. If there are duplicate identifiers, the last one “wins”.
The key “settings” is standing out, as it is used for Extbase Settings and is available as a flat list in ActionController.
Allowing this exception would make it possible to access these values in normal Content Elements / Plugins as well.
Reviews 2
History 216
-
Gerrit Code Review pushed patch set 2 for main to change 89405 status
NewUnder Review <span data-processor="relativetime" data-value="2025-06-06T17:09:41+00:00" > 06/06/25, 17:09 </span> -
Gerrit Code Review pushed patch set 3 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T17:59:15+00:00" > 06/06/25, 17:59 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T18:35:38+00:00" > 06/06/25, 18:35 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T18:47:07+00:00" > 06/06/25, 18:47 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T19:30:15+00:00" > 06/06/25, 19:30 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T20:32:55+00:00" > 06/06/25, 20:32 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T20:54:28+00:00" > 06/06/25, 20:54 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T21:11:29+00:00" > 06/06/25, 21:11 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T21:22:29+00:00" > 06/06/25, 21:22 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 89405 <span data-processor="relativetime" data-value="2025-06-06T22:07:46+00:00" > 06/06/25, 22:07 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 89405 <span data-processor="relativetime" data-value="2026-04-22T06:33:57+00:00" > 04/22/26, 06:33 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 89405 <span data-processor="relativetime" data-value="2026-10-10T09:21:13+00:00" > 10/10/26, 09:21 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 89405 <span data-processor="relativetime" data-value="2026-10-19T09:30:19+00:00" > 10/19/26, 09:30 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 96901 <span data-processor="relativetime" data-value="2026-10-20T08:03:22+00:00" > 10/20/26, 08:03 </span>
-
Oliver Bartsch commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-20T08:10:11+00:00" > 10/20/26, 08:10 </span>Applied in changeset commit:ea44381f15a13c70abcdad39fa93f209ac12159e.
I think that was working before TYPO3 13.4.10. There was a change in the FlexFormSchema that handles sheets correctly. It seems accessing the variables as described does not work anymore now.
In our case, a solution just for the settings variable would also be enough :-)