---
title: "Important: Form data transformation only maps submitted fields"
manual: "Academic Profiles Edit"
version: "main"
source: "Changelog/2.4/Important-FormDataTransformationOnlyMapsSubmittedFields.rst"
rendered: "2026-09-30T20:17:10+00:00"
---

# Important: Form data transformation only maps submitted fields {#important-ace-33-academic-persons-edit}

## Description {#description}

The frontend editing of `EXT:academic_persons_edit` maps submitted form
data transfer objects (`\FGTCLB\AcademicPersonsEdit\Domain\Model\Dto\AbstractFormData`
descendants) onto the domain models through the per-property factory
classes in `\FGTCLB\AcademicPersonsEdit\Domain\Factory\*`.

Until now these factories wrote **every** property on each request, so a
field that was not part of the submitted form was silently overwritten
with the empty default of the form data object, wiping already persisted
data. This is corrected: a property is now only applied when it was
actually sent within the current request.

To make this possible the following additions were made (all of them on
`@internal` classes that are not part of the public API):

-   `\FGTCLB\AcademicPersonsEdit\Domain\Model\Dto\AbstractFormData`
    carries the current request and the mapped argument name and exposes
    `wasPropertySentInRequest(string $propertyName): bool` to detect
    which properties were part of the submission. The request and argument
    name are provided by the new
    `\FGTCLB\AcademicPersonsEdit\Property\TypeConverter\AbstractFormDataConverter`,
    which is registered for all `AbstractFormData` based arguments in
    `\FGTCLB\AcademicPersonsEdit\Controller\AbstractActionController::initializeAction()`.
-   All factory classes (`Profile`, `ProfileInformation`, `Contract`,
    `Address`, `Email`, `PhoneNumber`) skip properties that were neither
    sent within the request nor registered as override. The existing
    `readOnly` / `disabled` validation configuration keeps precedence
    and continues to protect persisted data.
-   For the case where a property is not part of the request but still has
    to be written - for example when a PSR-14 event fills up data from
    another source before the transformation runs -
    `AbstractFormData` gained a per-property override store via
    `setPropertyOverride(string $propertyName, mixed $value)`,
    `hasPropertyOverride(string $propertyName)` and
    `getPropertyOverride(string $propertyName)`. Registered overrides
    are applied even when the property was not submitted.

Additionally
`\FGTCLB\AcademicPersonsEdit\Domain\Factory\ContractFactory::setValidTo()`
was fixed to evaluate the validation configuration of `validTo` instead
of `validFrom`.

## Impact {#impact}

The runtime behaviour of the frontend edit forms changes: submitting a
form no longer resets fields that are not contained in that form. Fields
are only written when they were part of the request or were explicitly
registered as override on the form data object. No public method
signature changed in an incompatible way.

## Affected Installations {#affected-installations}

Only installations that extend or replace the internal form data factory
classes or `AbstractFormData`, or that relied on the previous
"always overwrite" behaviour of the transformation, need to take the
changed behaviour into account. All other installations benefit from the
fix without any action required.

## Migration {#migration}

No explicit migration is required. Custom code that populates a form data
object outside of the request (e.g. within a PSR-14 event) and expects
the value to be persisted must register it via
`AbstractFormData::setPropertyOverride()` so the transformation
applies it despite the property not being part of the request.