Hi devs,
I believe we have already talked about this… So right now, it is difficult to know the org. units that are selected for a particular dataset/org. unit group/etc (see attached image).
I think you are going to change the behaviour of this… Is this something we could have in the following days? (it is a bit complicated to manage when you have more than 40.000 org. units in the system 
).
It will be nice to have this fix for 2.24 and 2.25.
Thanks
Jose
+1
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986|
busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
On 3 Nov 2016, at 11:07, Jose Garcia Muñoz josemp10@gmail.com wrote:
Hi devs,
I believe we have already talked about this… So right now, it is difficult to know the org. units that are selected for a particular dataset/org. unit group/etc (see attached image).
I think you are going to change the behaviour of this… Is this something we could have in the following days? (it is a bit complicated to manage when you have more than 40.000 org. units in the system
It will be nice to have this fix for 2.24 and 2.25.
Thanks
Jose
<image.png>
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
Hi Jose,
thanks, yup we are working on this and I understand the inconvenience.
Many of the devs are out this week, and so I cannot promise this in the next days, but will keep you posted.
best regards,
Lars
On Thu, Nov 3, 2016 at 12:07 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:
Hi devs,
I believe we have already talked about this… So right now, it is difficult to know the org. units that are selected for a particular dataset/org. unit group/etc (see attached image).
I think you are going to change the behaviour of this… Is this something we could have in the following days? (it is a bit complicated to manage when you have more than 40.000 org. units in the system
It will be nice to have this fix for 2.24 and 2.25.
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
–
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
Thanks Lars,
Waiting for your news then :).
Best regards
On Fri, Nov 4, 2016 at 10:48 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Jose,
thanks, yup we are working on this and I understand the inconvenience.
Many of the devs are out this week, and so I cannot promise this in the next days, but will keep you posted.
best regards,
Lars
On Thu, Nov 3, 2016 at 12:07 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:
Hi devs,
I believe we have already talked about this… So right now, it is difficult to know the org. units that are selected for a particular dataset/org. unit group/etc (see attached image).
I think you are going to change the behaviour of this… Is this something we could have in the following days? (it is a bit complicated to manage when you have more than 40.000 org. units in the system
It will be nice to have this fix for 2.24 and 2.25.
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
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
–