#88472Table with mm relation, unable to use ###CURRENT_PID### on relation if parent is unsaved
Description
Hey,
I’m using the following TCA configuration to get a mm-relation:
// ...
"rental_fees" => [
"exclude" => true,
"label" => "LLL:EXT:my_portal/Resources/Private/Language/locallang_db.xlf:tx_portal_domain_model_flat.rental_fees",
"config" => [
"type" => "select",
"renderType" => "selectMultipleSideBySide",
"foreign_table" => "tx_portal_domain_model_rentalfee",
"foreign_table_where" => "AND {#tx_portal_domain_model_rentalfee}.{#pid} = ###CURRENT_PID### AND {#tx_portal_domain_model_rentalfee}.{#hidden} = 0 ORDER BY tx_portal_domain_model_rentalfee.startdate",
"size" => 5,
"MM" => "tx_portal_flat_rentalfee_mm",
"maxitems" => 1,
"minitems" => 1,
"fieldControl" => [
"addRecord" => [
"disabled" => false,
"renderType" => "addRecord",
"options" => [
"title" => "Neuen Datensatz hinzufügen",
"setValue" => "append",
"pid" => "###CURRENT_PID###"
],
],
]
],
],
// ...
Everything is working fine on already saved “flats”, but If I add a new one and want to add my rentalfee first, the “new to save” rentalfee isn’t added to the ###CURRENT_PID###.
When checking the developer tools, it’s definitely set (check the attached screenshot for information).
Thanks for reading, have a nice day.
- Julian
Reviews 1
Related issues 1
History 67
-
Gone With the Wind changed Related to #84208 <span data-processor="relativetime" data-value="2019-06-03T08:48:19+00:00" > 06/03/19, 08:48 </span>
-
Gone With the Wind changed Related to #84208 <span data-processor="relativetime" data-value="2019-06-03T08:48:48+00:00" > 06/03/19, 08:48 </span>
-
Gone With the Wind changed
Related to #84208<span data-processor="relativetime" data-value="2019-06-03T08:48:57+00:00" > 06/03/19, 08:48 </span> -
Gone With the Wind commented <span data-processor="relativetime" data-value="2019-06-03T08:51:50+00:00" > 06/03/19, 08:51 </span>
I am “suffering” from this problem, too. In a Slack chat, Benny Mack meant that this is a bug: vars like ###PAGE_TSCONFIG_ID### are simply not evaluated…
-
Christian Eßl changed category <span data-processor="relativetime" data-value="2019-10-01T20:26:47+00:00" > 10/01/19, 20:26 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 96340 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-03T05:11:24+00:00" > 10/03/26, 05:11 </span>
When using just the default settings, it’s working fine.