We are encountering a bug with Mandatory Data Elements in the Capture App (versions 105.2.5–105.2.9). The last version where everything worked correctly was 105.2.4.
In our Tracker Program, within a specific Program Stage, we configured Program Rules (PRs) to hide certain DEs depending on the OrgUnit (OU) and make them mandatory for others.
PR1 checked whether the OU belonged to the specified OU group.
If it did not, the DEs were hidden.
PR2 then made those DEs mandatory when applicable.
However, starting from 105.2.5, even when those DEs already have values, the Capture App still displays the error message: “This field is required.”
Has anyone else experienced this issue with conditionaly mandatory DEs in Capture App (versions 105.2.5–105.2.9)?
Any guidance, workarounds, or confirmation would be greatly appreciated. Thanks in advance for your support!
Not sure at all if this is related, but I recently faced an issue with a program stage with a validation strategy “On update and insert” where the capture app was acting similarly to what you showed with one of the latest version of Capture Web App on server version 2.41.
I did not have much time to test older versions, but I saw that the problem was not happening after updating the validation strategy to “On complete” through API.
After this change, i was able to edit, save and complete the event.
Do you knwo which validation strategy you used for this program stage?
I did not take time to report this issue, but would be intersted to know if this may be related.
