Hi, It's true that there is no inheritance (which makes sense if for example you want to make a group like "Districts"). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me. On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO < octavio.glo...@barcelona.msf.org> wrote: > Hi all, > I am not sure if this is the normal behaviour, but seems that Organisation > Units do not inherit their ancestors Organisation Unit Groups. In our > case, most of the data belongs to leaf instances of our Organisation Units > Tree. Therefore, those terminal Organisation Units had to belong to all > their ancestors Organisation Unit Groups in order to use those groups as > analysis dimensions. Is that correct? > Thanks in advance, > Octavio. > > > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-users > Post to : dhis2-users@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-users > More help : https://help.launchpad.net/ListHelp > > -- Knut Staring Dept. of Informatics, University of Oslo Norway: +4791880522 Skype: knutstar http://dhis2.org
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : dhis2-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
