Hi Devs Please ignore, we've figured a way around this problem (metaData.ouHierarchy makes the lookups possible) but we have a new issue. In the [api/analytics/events/aggregate] JSON output metaData.names collection does not include header field names, e.g."pe": "Period", "ou": "Organisation unit ","dx": "Data" are all missing.
Greg On Tue, Mar 24, 2015 at 10:23 AM, Greg Rowles <greg.row...@gmail.com> wrote: > Hi Devs > > We've picked up an inconsistency between Event aggregate analytics (API) > and the regular aggregated analytics (API). JSON output for the latter > (when requesting '&hierarchyMeta=true&displayProperty=NAME') includes > metaData.ouNameHierarchy but not for the event aggregate analytics API call. > > Regards, > Greg > > -- > *Health Information Systems Program - South Africa* > *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - - - > - * > Mobile : 073 246 2992 > Landline: 021 554 3130 > Fax: 086 733 8432 > Skype: gregory_rowles > -- *Health Information Systems Program - South Africa* *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - - - - * Mobile : 073 246 2992 Landline: 021 554 3130 Fax: 086 733 8432 Skype: gregory_rowles
_______________________________________________ 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
