Closed samkanga closed 4 years ago
@samkanga could you give an example?
@moshthepitt let me upload a new value and share feedback on this.
@moshthepitt what is the estimated time within which an uploaded target value should reflect on the dashboard?
it pulls new targets every hour @samkanga
Cool. I am just past the 1 hour mark but I will give it a little more time and recheck this.
@moshthepitt I am at the 2 hours mark and the new target value of 555 is not showing. I however see a value that was uploaded yesterday 200 (see screenshot below). So its more of an issue of how soon it takes to see the updated values.
Will look into this
jurisdiction_id | val | serverversion | target
--------------------------------------+------+---------------+--------
40aee4db-1c05-4fdf-a984-612829d6900b | 200 | 1598881019465 | 200
40aee4db-1c05-4fdf-a984-612829d6900b | 666 | 1598551533633 | 666
40aee4db-1c05-4fdf-a984-612829d6900b | 1000 | 1598551337034 | 1000
40aee4db-1c05-4fdf-a984-612829d6900b | 1000 | 1598551260928 | 1000
40aee4db-1c05-4fdf-a984-612829d6900b | 789 | 1598551154119 | 789
40aee4db-1c05-4fdf-a984-612829d6900b | 900 | 1598549810589 | 900
40aee4db-1c05-4fdf-a984-612829d6900b | 555 | 1598437431779 | 555
40aee4db-1c05-4fdf-a984-612829d6900b | 777 | 1598436217645 | 777
40aee4db-1c05-4fdf-a984-612829d6900b | 876 | 1598351014887 | 876
40aee4db-1c05-4fdf-a984-612829d6900b | 819 | 1598349250450 | 819
40aee4db-1c05-4fdf-a984-612829d6900b | 777 | 1598349250450 | 777
40aee4db-1c05-4fdf-a984-612829d6900b | 900 | 1598349250450 | 900
40aee4db-1c05-4fdf-a984-612829d6900b | 111 | 1598349250450 | 111
40aee4db-1c05-4fdf-a984-612829d6900b | 900 | 1598349250450 | 900
40aee4db-1c05-4fdf-a984-612829d6900b | 111 | 1598349250450 | 111
40aee4db-1c05-4fdf-a984-612829d6900b | 555 | 1598332159787 | 555
40aee4db-1c05-4fdf-a984-612829d6900b | 111 | 1598324747731 | 111
40aee4db-1c05-4fdf-a984-612829d6900b | 111 | 1598277187123 | 111
40aee4db-1c05-4fdf-a984-612829d6900b | 819 | 1598167189807 | 819
40aee4db-1c05-4fdf-a984-612829d6900b | 900 | 1598167189807 | 900
40aee4db-1c05-4fdf-a984-612829d6900b | 777 | 1598159542960 | 777
40aee4db-1c05-4fdf-a984-612829d6900b | 900 | 1597657275755 | 900
@samkanga ^^ is what has been uploaded to this jurisdiction so far. The value that is used in the reports of 200 is the very latest thing uploaded.
You can verify this for yourself by running this query in SQL lab.
@moshthepitt not sure where the missing link is on this one. I have uploaded a new value to test this. Let's see how this goes and we can plan a way forward. In the meantime I will provide a screenshot of the present value uploaded of 566 as seen from the apk.
@samkanga we need to verify what the mobile app is using. There does not seem to be a value of 566 in the database.
@githengi share some insight on the setup of the android client. Trying to determine the missing link to the uploaded csv.
@samkanga @moshthepitt the settings used are the jurisdictions upload for targets. This is the values used on stage https://reveal-stage.smartregister.org/opensrp/rest/v2/settings/?identifier=jurisdiction_metadata-target&serverVersion=0
@Wambere could you please look into this? It seems that the Canopy DB has items that don't match the API e.g. https://reveal-na.smartregister.org/opensrp/rest/v2/settings/?identifier=jurisdiction_metadata-target&serverVersion=0 currently returns only 1 item.
@Wambere so the TODO is:
@moshthepitt this is updated
Thanks @Wambere. I will do another test and share some feedback on my findings.
@Wambere is it also updated for stage, and zambia prod?
@moshthepitt I'm getting an error updating stage. Some records have keys with 37 characters instead of 36. Is this intentional? should I update the table to allow this?
Please do not update the table. Share this so that the OpenSRP engineers can fix.
@moshthepitt , @Wambere I can confirm that I uploaded a new value against Namibia production and it has reflected on the dashboard. Thank you for the fix.
@samkanga just for clarity, this fix is not working on stage because of the issue I have raised above. Please follow up with the openSRP team to ensure that this is fixed
Closed because this was fixed.