We are using a tracker program allowing to schedule events in the future.
However, it can happen that the Android user directly enters an event without schedulintg first.
In this case, using Android App 3.1.1.1 (with DHIS2 2.41.3), the “sheduled date” remains empty after uploading to the server, when the event was created from android device.
If we try to edit the submitted event with Web capture app, we have an error message sying that scheduled date should be filled (but it is not possible to fill it afterwards using Web capture app).
If the event is created using the “Web capture app”, the scheduled date is filled in using the report date, and the problem does not happen.
You can reproduce this issue on play environonment with the child program:
Enter an event from Android device without sheduling it first.
Sync the event
open the event using web Capture App
Please see printscreen attached from play environment.
Thanks for the detailed post with the examples. The examples are very helpful; however, from the specific example you mentioned, isn’t the event ‘Baby Postnatal’ auto-generated with 6 days from from the start?
The expectation is that once the Birth event is created, the Baby Postnatal is auto-generated with a scheduled date as well. Which of these is true:
In the Android app, the scheduled date is generated but not synced
In the Android app, the scheduled date is not generated (unlike the web Capture app)
The event is not auto-generated in the Android app (unlike the web Capture app)?
Thanks for the follow up. I did not really test the “scheduling part” as my issue on my instance regards adding events without scheduling it before.
From what I understand, the issue is that the scheduled date is not filled in with report date when creating an event from Android app without shceduling it before.
The event sent to the server has a report date, and an empty scheduled date. This prevents from updating or saving the event from the web capture application as shown in the pictures previously sent.
This was not occuring when using older versions of the android app as I never faced it before while using the same configuration on my instance.
Thank you for the report. I was able to replicate it and I’ve asked the team to review it. I’ll be posting the jira ticket when I have more information.
thanks for reporting and for all the details, they were really helpful to identify the issue. It seems to affect only version v41 (v40 and downwards work fine).
I have verified that the former Tracker Capture web app allows the edition of those events, so you could use that application while we fix the issue.
FYI, I just tried to use Android App version 3.1.0 with Server on 2.41.3 and I obtain the same behaviour (Scheduled date sent empty to the server, and I need to set it using API to be able to modify the event in the Web Capture App as I can not modify it even using old Tracker Capture app).
We have another instance using 2.41.2, and it seems that the problem does not occur.
Do you believe the problem could be more related to the server side than to the Android app version?
thanks for all the details. They match what I have found so far: the Android app version does not matter that match because it has not changed the behavior; the difference is in the DHIS2 version.
We still need to confirm the way to solve it, I will keep you updated.
