Description
We have a form in which we collect data from participants. In this form they need, among other things, to fill in the size of their location and how this is used. They can select the types from a multiple select and for each selected item they need to fill in the size of the surface that is used. There is a constraint on this last field which states that the surface is larger than 50 m2 and smaller than the total size (example below).
We collect the submissions via the API. When a mistake was made, the user can update their submission and hit a button to recollect the submission. However, if the user does not change the selected items in the multi select or updated the surface, then the surface field for each item is missing when downloading the submission via the API.
the field with the constraint is missing after the update.
Example: A participant can fill in that their location is 14000 m2. On this location, there are plants of type A and B. A takes 5000m2 and B takes 6000m2.
Steps to Reproduce
- Create a form with the following questions:
- Some question (type unimportant)
- Total surface (type: Decimal)
- Entities (type: Multi-select)
- Surface entity (for each selected item) (type Decimal)
- The last question has the following constraint:
.>=50 and .<=${total_surface} - Save the form
- Enter a submission
- Edit the submission by updating the first question
- Retrieve the submission via the API
Expected behavior
Every answer is included in the retrieved submission
Actual behavior
The answers for Surface entity is missing
Additional details
Your environment, why you think this might be happening, or stuff you tried that didn’t work
- What should topics in this category generally contain?
- Do we need this category? Can we merge with another category, or subcategory?
