Hello,
In one of our customers’ DHIS2 that we are integrating through the API we have a weird situation: we have org units we see through the API but not using the UX.
Specifically, there seems to be a lot of org units at the level 1 (top) while there should be only one (the country). The UI seems good, so I’m wondering if there is any sort of filtering by default on the UI and if so which one?
At this time, this means we can’t locate the “main/country” org unit through the API (we expect to find only one at the root level, which is not the case).
Any leads?
Thanks,
Martin
···
**Martin Van Aken - **Freelance Enthusiast Developer
the problem is usually that the user you are logged in as (the “current user”) is assigned to a single root org unit. You can check that through the API (user → organisationUnit) and the user app.
After this user was created, I guess someone has created additional org units through the API but got the “parent” org unit element wrong or simply omitted it. When an org unit has a null/missing parent, it effectively becomes a root org unit. Now since your user is assigned the original root, you cannot see those other root org units.
The solution is to move the “fake” root org units to their appropriate place in the hierarchy by modifying the org unit parent element.
Also, if you log in with a user with the ALL authority and go to the user app → create new user, you should be able to see those extra root org units.
Hello,
In one of our customers’ DHIS2 that we are integrating through the API we have a weird situation: we have org units we see through the API but not using the UX.
Specifically, there seems to be a lot of org units at the level 1 (top) while there should be only one (the country). The UI seems good, so I’m wondering if there is any sort of filtering by default on the UI and if so which one?
At this time, this means we can’t locate the “main/country” org unit through the API (we expect to find only one at the root level, which is not the case).
Any leads?
Thanks,
**Martin Van Aken - **Freelance Enthusiast Developer
Ok, thanks a lot. I understood the “multiple” root, but this explains why I have two different situation.
Regards,
Martin
···
On Mon, Feb 6, 2017 at 2:28 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Martin,
the problem is usually that the user you are logged in as (the “current user”) is assigned to a single root org unit. You can check that through the API (user → organisationUnit) and the user app.
After this user was created, I guess someone has created additional org units through the API but got the “parent” org unit element wrong or simply omitted it. When an org unit has a null/missing parent, it effectively becomes a root org unit. Now since your user is assigned the original root, you cannot see those other root org units.
The solution is to move the “fake” root org units to their appropriate place in the hierarchy by modifying the org unit parent element.
Also, if you log in with a user with the ALL authority and go to the user app → create new user, you should be able to see those extra root org units.
Hello,
In one of our customers’ DHIS2 that we are integrating through the API we have a weird situation: we have org units we see through the API but not using the UX.
Specifically, there seems to be a lot of org units at the level 1 (top) while there should be only one (the country). The UI seems good, so I’m wondering if there is any sort of filtering by default on the UI and if so which one?
At this time, this means we can’t locate the “main/country” org unit through the API (we expect to find only one at the root level, which is not the case).
Any leads?
Thanks,
**Martin Van Aken - **Freelance Enthusiast Developer