webAPI JSON: (hierarchyMeta=true) outputs in Event Report VS Pivot Reports

Support - Assistance technique
1

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

2

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.rowles@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

3

Ok, I guess we can add this. For now you can loop through the headers and add them manually (: ) immediately after getting the response from the server.

···

On Tue, Mar 24, 2015 at 10:46 AM, Greg Rowles greg.rowles@gmail.com wrote:

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

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

On Tue, Mar 24, 2015 at 10:23 AM, Greg Rowles greg.rowles@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

4

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.

Hi Greg,

these header names (pe, ou, dx) are static so really not a need to include
them in the server response every time - I suggest you just include these
names directly in a map in your report/app.

cheers

Lars

···

On Tue, Mar 24, 2015 at 10:46 AM, Greg Rowles <greg.rowles@gmail.com> wrote:

5

Hi Greg,

we have added support for showHierarchy query param in event aggregate analytics now in trunk.

regards,

Lars

···

On Tue, Mar 24, 2015 at 9:23 AM, Greg Rowles greg.rowles@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

–

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

6

Hi Greg,

I have added the dimension names to the meta data names in trunk now.

regards,

Lars

···

On Tue, Mar 24, 2015 at 10:46 AM, Greg Rowles <greg.rowles@gmail.com> wrote:

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.