Hi Uwe,
like you have observed, the Web API versioning applies to query parameters,
responses and most things, but not the metadata model entirely. This
because we currently do not have a "data transfer object" layer between the
DHIS 2 metadata model and what we render in the API. As a consequence
Hi Bob,
overriding categoryCombos sounds interesting - I will look at that later. Not
sure what that means in terms of transparency of the data later on, though ...
As an implementor/3rd party developer I'd expect of course that even if the api
has changed in the current version, that it will wor
The reason why there isn't a backward compatible api is because the
underlying model has changed to support overriding the categorycombo per
dataset. So a dataset no longer has dataElements, but dataSetElements.
The dataSetElement is a compound object consisting of both a dataelement
reference and
Thanks Uwe,
I have been trying to figure this out as well.
On 3 November 2016 at 04:04, Uwe Wahser wrote:
> just found the answer myself: it has to be
> https://play.dhis2.org/demo/api/dataSets/N4fIX1HL3TQ.json?
> paging=false&fields=dataSetElements[dataElement[id,code,name]]
>
> the other qu
just found the answer myself: it has to be
https://play.dhis2.org/demo/api/dataSets/N4fIX1HL3TQ.json?paging=false&fields=dataSetElements[dataElement[id,code,name]]
the other question remains: why cant I use the old syntax by adding 24 or 23 to
the url?
Regards,
Uwe
---
> Uwe Wahser hat am 3.
5 matches
Mail list logo
