Dear All,
I am implementing some assessment tools in which one of the core activities is to create an action plan and assign a due date, which is mostly in the future.
We are running DHIS2 v40 and we wanted to use Android 3.0 or 3.1. Unfortunately, these app versions are giving errors when someone selects a future date during data entry.
When tried in Android Capture 2.9, with the same configuration, the future date, it works perfectly.
Hi @Fatsani! I am sorry you are experimenting some issues with the android capture app.
Do you think you could provide us some more information on the problem you are facing?, like for example, what kind of configuration you are using? is it a tracker program or an event program? does it occur when scheduling events or creating new events? what is the error being displayed? all extra details you provide will help us pinpoint the issue faster.
Thank you in advance!
Xavier.
Hi @Xavi
It is a tracker program where some TEI attributes and data elements have future dates as possible inputs.
Error for TEI Instance with this configuration.
The same error for data elements.
With this configuration
Hi again @Fatsani, I have just tested and replicated this and it is indeed a bug on our side.
It is being flagged as an error incorrectly. I have created a bug in Jira to resolve this and it will be resolved in the next minor patch release (3.1.1) which is planned for beginning of January. You can track the progress here.
As a workaround for now when validating the form and the save dialog pops up, if you tap on “not now” it will still save the value and sync correctly, when entering the form again it will not display as an error anymore, unless it is modified again.
Unfortunately this will not work when creating a new TEI, as you cannot create a new tei with errors in the form, meaning that the “not now” button will not be there. So if you have any TEI attributes with future dates you will have to enter a past date to create the TEI and then edit it afterwords, once the TEI is created it should allow you to save the form with said error and also sync correctly.
Thanks for bringing this to our attention!
Best wishes,
