We are testing an implementation of the latest android apk against 2.20 instance capturing aggregated data values weekly for a campaign dataset.
From our testing the following:
Capturing data on the apk posted data to DHIS2.
Running a dataset report and viewing the data in the UI and pulling a SQL view all showed consistent data values
Updating datavalues on the apk updated the datavalues in the datavalue table but did not update the datavalueaudit. Dataset report did not pull the updated values but still showed the first captured values even after clearing cache in every possible way. SQL view of the datavalue table shows that the data is updated.
Updating datavalues in the UI updated datavalues in the datavalue, datavalue audit table and the dataset report.
Is the fact that the datavalue audit table is not updated when editing values in the apk a bug?
Where does the dataset report pull data from if not the datavalue table and why is it not displaying the correct value – is this a bug?
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Did you run Analytics after you update the data values? This would be necessary to update your data set report.
Regards
- -
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986|
busoye@baosystems.com <mailto:busoye@baosystems.com> | http://www.baosystems.com <http://www.baosystems.com/> |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
···
On 12 Jul 2016, at 08:05, Elmarie Claasen <elmarie@hisp.org> wrote:
Hi all,
We are testing an implementation of the latest android apk against 2.20 instance capturing aggregated data values weekly for a campaign dataset.
From our testing the following:
1. Capturing data on the apk posted data to DHIS2.
2. Running a dataset report and viewing the data in the UI and pulling a SQL view all showed consistent data values
3. Updating datavalues on the apk updated the datavalues in the datavalue table but did not update the datavalueaudit. Dataset report did not pull the updated values but still showed the first captured values even after clearing cache in every possible way. SQL view of the datavalue table shows that the data is updated.
4. Updating datavalues in the UI updated datavalues in the datavalue, datavalue audit table and the dataset report.
Is the fact that the datavalue audit table is not updated when editing values in the apk a bug?
Where does the dataset report pull data from if not the datavalue table and why is it not displaying the correct value – is this a bug?
Regards,
Elmarie Claasen
<image001.png>
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org <mailto:elmarie@hisp.org>
Skype: elmarie.claasen52
This message and any attachments are subject to a disclaimer published at Home - HISP-SA <Home - HISP-SA. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org <mailto:disclaimer@hisp.org>and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
This message and any attachments are subject to a disclaimer published at Home - HISP-SA. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org <mailto:disclaimer@hisp.org> and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
