dhis2-users team mailing list archive

[sumudu weerasinghe <sumuduw00@xxxxxxxxx>]

Hi Robin,
I had the same issue as you said . I did it following way , but it may not
be the correct way

   - build one aggregate query and save
   - go to database and find *caseaggregationcondition* table
   - identify how it identify DE
   - you can populate all query builders just in a excel sheet ( i will
   attach my sample excel sheet it contain 364 A.Q. Builders)
   - upload into database table *caseaggregationcondition, *as CSV file  ,
   It works for me well

some time this may help you.

@Lars answer  i have some problem

   1. is it able to use attributes in event reports ?
   2.  is it possible to save this values into a  form in aggregate side
   (eg.Monthly return form) ?

Best Regards
Sumudu


On Wed, Jul 23, 2014 at 11:58 AM, Lars Helge Øverland <larshelge@xxxxxxxxx>
wrote:

> Hi Robin,
>
> in fact the organisation unit dimension should not be part of the
> aggregation queries - you can set one aggregation query to run for any
> number of org units. You could create the gender and disease type as
> categories + category options. However you are right that to populate all
> variations of this data element you would need 2 x 5 aggregation queries.
>
> That said, in version 2.15 and 2.16 you have better support for doing
> aggregated analysis without using aggregation queries. The "event reports"
> app lets you create pivot tables and specify queries directly for
> aggregated data, and you can similarly create charts through the "event
> visualizer" app, which can then be included directly in the dashboard
> together with the routine data charts. Have a look at those apps on the
> /dev <https://apps.dhis2.org/dev> instance - the queries can be specified
> on the left side panel e.g. under the "data" tab.
>
> These apps are backed by the event analytics web api resource (docs
> <https://www.dhis2.org/doc/snapshot/en/user/html/ch32s22.html>). Our
> medium-term plan is to phase out the current aggregation queries function
> by instead linking routine elements with such event analytics queries.
>
> Now conceptually you would still have to define a query per such data
> element + category option combination - it isn't really trivial to convert
> events into aggregated data elements "auto-magically".
>
> best regards,
>
> Lars
>
>
>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>

Attachment: TOTAL 364AQ.xlsx
Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet