It's a design limitation issue, it's not a bug, and addressing it has implications on analytics, reports as well as way people will be assigning dataset to orgunits.
So it will probably come in next releases, but unlikely to be backported to previous system because of breaking changes that will be introduced along with the solution. On Mar 24, 2017 5:21 PM, "gerald thomas" <gerald17...@gmail.com> wrote: Dear All, We had been struggling with this issue along with other users and we haven't received much to conclude it. Please any help to close the subject? It is also on JIRA: https://jira.dhis2.org/browse/DHIS2-300. Kindly note that when our instance is on 2.22 the reporting rate was working fine. This issue occurs whenever we upgrade our system beyond 2.22. -- Regards, Gerald _______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : dhis2-us...@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
_______________________________________________ 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
