unused/hidden read-only prefill fields trigger error #5124
Assignees
Labels
Milestone
Comments
LaurensBurger
added
triage
|
Refinement: Needs fixing indeed. |
joeribekker
removed
the
triage
10 tasks
vaszig
added a commit
that referenced
this issue
Mar 4, 2025
When a component (or its parent is disabled and hidden, the validation in the backend is triggered since there is no data for the specific key. This means, for our validator, that the data has been changed and raises an error.
sergei-maertens
added
the
needs-backport
vaszig
added a commit
that referenced
this issue
Mar 12, 2025
This ensures that if a field is prefilled but not hidden and the data is omitted from the submission data, the initial prefill data is persisted in the database. So, if a user clears a prefilled field that is read-only we make sure that this will not affect the real value of the variable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Product versie / Product version
3.x.x
Customer reference
DH, 's-Hertogenbosch
Omschrijf het probleem / Describe the bug
When a form has multiple field sets for a "uw-gegevens" step e.g:
And these field sets are hidden and the fields within (being dedicated for pre fill) are disabled: Trigger the "Je mag de prefill-gegevens niet wijzigen" error on "validate" call.
In this case the prefill did not return any value, and the field set is hidden because the user started the form with another authentication plugin.
As the fields that do not pass validation are not prefilled at all this should not occur.
Stappen om te reproduceren / Steps to reproduce
Form 749 on maykin test.
Start the form anonymous
Select: "Persoon"
Fill in fields and try to navigate to the next step.
See "validate" request.
Verwacht gedrag / Expected behavior
No response
Screen resolution
None
Device
None
OS
None
Browser
No response
The text was updated successfully, but these errors were encountered: