Hi All,
I would like to have your advice on how to fix the following issues:
- The first point is that after the creation of users who are entering data through DHIS2 data capture, each of them has the following warning (409 conflict) when logging in the web interface mentioning that the user is not allowed to view the org unit with an org unit UID that I could not locate in the database (through SQL view). How to troubleshoot this issue?
-The second point is when using the reporting rate app, I am summarizing the report by the administrative commune level (level 5 in the org unit hierarchy). Instead of having 3 total of expected reports (red circle), the app is counting the level 5 itself so the total expected reports become 4 (as illustrated in the image below), which is false. Are there some parameters that I should set to fix this issue?
I am using DHIS2 2.19.
Thank you for your help.
···
Tantely Raminosoa
Data Officer
Management Sciences for Health
Antananarivo Madagascar
Mobile: 0321180040
E-mail: traminosoa@mikolo.org
Skype: traminosoa
Stronger health systems. Greater health impact.
www.msh.org
Thank you Lars for those information.
Regards,
Tantely.
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
···
On Thu, May 19, 2016 at 3:17 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Tantely,
–
On Thu, May 19, 2016 at 10:40 AM, Raminosoa Rabemanantsoa, Tantely traminosoa@mikolo.org wrote:
Hi All,
I would like to have your advice on how to fix the following issues:
- The first point is that after the creation of users who are entering data through DHIS2 data capture, each of them has the following warning (409 conflict) when logging in the web interface mentioning that the user is not allowed to view the org unit with an org unit UID that I could not locate in the database (through SQL view). How to troubleshoot this issue?
This could be related to a weakness which we just fixed. Can you please upgrade to latest 2.21 / 2.22 / 2.23 version and try again?
If you have a server-side cache (e.g. nginx) you could also clear that cache as an intermediate fix.
It’s quite strange that the org unit in the dialog is not in your database - can you double-check directly in the database?
-The second point is when using the reporting rate app, I am summarizing the report by the administrative commune level (level 5 in the org unit hierarchy). Instead of having 3 total of expected reports (red circle), the app is counting the level 5 itself so the total expected reports become 4 (as illustrated in the image below), which is false. Are there some parameters that I should set to fix this issue?
This depends on how you have assigned your data sets to org units. If you have assigned the data set to the org unit on the commune level if will be included in the number of expected reports. If you can un-assign the org unit form the commune org unit it will not be counted.
regards,
Lars
I am using DHIS2 2.19.
Thank you for your help.
–
Tantely Raminosoa
Data Officer
Management Sciences for Health
Antananarivo Madagascar
Mobile: 0321180040
E-mail: traminosoa@mikolo.org
Skype: traminosoa
Stronger health systems. Greater health impact.
www.msh.org
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@dhis2.org
http://www.dhis2.org
–
Tantely Raminosoa
Data Officer
Management Sciences for Health
Antananarivo Madagascar
Mobile: 0321180040
E-mail: traminosoa@mikolo.org
Skype: traminosoa
Stronger health systems. Greater health impact.
www.msh.org