Dear devs, Will try to explain the following DHIS2 behaviour for tracker the best as I can... So, PSI has upgraded its servers from 2.20 to 2.22 like 4 months ago. One of the countries that is using Tracker Capture reported several weeks ago that sometimes they can not see the program enrollment when they open an entityinstance *previously stored and enrolled in 2.20*. Some of the entities instances are correctly displayed and the user can see the program enrollments, but for other entities they don't, the program just appears in the Report Widget (see the image below).
[image: Inline image 1] Also, our team says that at least they can use the Tabular Tracker Capture app (developed by James, who is also ccyed in this email), as the problem is not happening using that app (they are right) I tried to investigate a bit further, but I couldn't find a relationship for this (why the problem happens with some entities and not for others). Also, the following API call api/enrollments?ou=NC3WdxGafv5&trackedEntityInstance=V1XKLzar3YQ&ouMode=DESCENDANTS <https://www.psi-mis.org/api/enrollments?ou=NC3WdxGafv5&trackedEntityInstance=V1XKLzar3YQ&ouMode=DESCENDANTS> (where the OU is a root org. unit) returns a null enrollment for the "problematic" entites, however they always appear in the list of entities with active enrollments (also, really strage) [image: Inline image 2] I doubt very much that our users had unenrolled all these entities instances. I have no idea about the cause/s of this issue, and I can only think of: 1) Could it be a problem related to the the api/enrollments endpoint? or 2) Could it be a problem in the database related to the upgrade from 2.20 to 2.22 ? Please any ideas will be much appreciated. Many thanks Jose
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
