dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #03755
Re: Separate DHIS2 database to 2
Hi Thuy,
Have you seen the dataSetReport module? There you have two options to
generate reports - one for the selected orgUnit only and the other one for
the selected orgUnit and all its children, grandchildren, grandgrand.... or
generally all orgUnits below it. I am not sure whether this logic fits into
your requirement. But one thing is clear - without splitting your database
you can aggregate values from a collection of orgUnits and generate a
report. The collection of orgUnits can be obtained using the method Lars
suggested or even you can handpick any and make a group.
Thank you
Abyot.
2009/12/17 Lars Helge Øverland <larshelge@xxxxxxxxx>
>
> Hi, I agree with what Ola says, you should definitely not split your
> database because of this. I am not sure if it is feasible to involve report
> tables in excel reporting. In any case there is a method on
> OrganisationUnitService which allows you to get all children of a specific
> orgunit on a specific orgunit level:
>
>
> /**
> * Returns all OrganisationUnits which are children of the given unit
> and are
> * at the given hierarchical level. The root OrganisationUnits are at
> level 1.
> *
> * @param level the hierarchical level.
> * @param parent the parent unit.
> * @return all OrganisationUnits which are children of the given unit
> and are
> * at the given hierarchical level.
> * @throws IllegalArgumentException if the level is illegal.
> */
> Collection<OrganisationUnit> getOrganisationUnitsAtLevel( int level,
> OrganisationUnit parent );
>
>
>
> Lars
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References