When getting patched to a later v40, our 2.9.1.1 Android stopped accepting 0 OU Assignment for categoryOptions to mean “all” OUs, and instead took it literally for “no” OUs. This was fixed in the latest version of 3.3.1 android, so we wanted to test and see if we could use this instead assigning our (thousands) of Category options with (thousands) of OUs.
While function testing, we noticed that the OU layout in selection is flattened down; i.e. there is no Sub-County, Ward, Village Tree hierarchy, but only the lowest level OUs which are assigned to the program. The user is assigned to the Sub-County, and we were counting on the experience being the same to web Capture (and 2.9.1.1) where the OU hierarchy tree allows a filtered view of the lowest levels.
Just making sure we aren’t missing anything here? I didn’t see any cards up on Jira, and it would seem to be a big issue that it makes me wonder if I haven’t missed configuration somewhere.
Hello @matthew_boddie,
the v40 patch you mentioned is v40.10, isn’t it? I think you were impacted by this issue, which was solved in v40.11. So you have two options to workaround it:
Update to 3.3.1, which has a workaround for this issue.
Keep version 2.9.1.1 and update the server to v40.11.
Regarding the flattened orgunit tree, it was an intentional change because there were complaints about having a very big OU tree. But now it seems that the solution is not working in some cases, so it seems that we need to look for a better approach (see also this ticket).
Thanks @vgarciabnz for clarity on that not only 3.3.1 but also 40.11 would remove the issue for CO-OU assignment that we’re facing.
I can understand the intentional change on orgUnits, but unfortunately comes as a dealbreaker for us with teams on the ground. I’m sure it’s pie in the sky, but perhaps this comes to a preference that can be set up in the android settings app? Will have a look at the ticket.