Hi Jason & Ocaya,
thanks for your input. Just to follow up: Kettle just released a new
version (7.0) last month. According to their forum it includes a fix for
the bug. Didn't have time to try this out, yet, but that seems to be the
solution then.
For the record: the xml api doesn't seem to
Dear Uwe,
This is a json issue. Recently i had guidance from lars that the xml
returns even the empty properties.
Apparently, suggestions in the link below talks of leaving out properties
with null values.
https://google.github.io/styleguide/jsoncstyleguide.xml
The only work around:
1. Try
Hi Jason,
It's not new - I had that problem already last year, but managed to work
around. Now I wanted to use more properties and the workaround doesn't
work for that.
I had decided against csv back then, but forgot why. Must have been a good
reason, because normally I prefer csv :-)
I
Hi Uwe,
OK, I sort of see the problem you have, but am pretty sure its not a DHIS2
problem. Are you saying that this is new behaviour, and it was not like
this before? I just checked an old instance I have which is running 2.17,
and it is exactly the same, so not sure this has changed any time
Hi Jason,
simple example:
https://play.dhis2.org/demo/api/organisationUnits.json?paging=false=level:eq:3=name,comment
What I'd expect would be a json package with name & comment for ALL
organisationUnits, even when the comment is NULL. What I get is a comment
property for Badjia (which I
Hi Uwe,
Could you give a specific example from the demo server with an API call,
and what is not working as you expect?
Regards,
Jason
On Fri, Dec 16, 2016 at 8:48 AM, Uwe Wahser wrote:
> Sorry, on a closer look it only seems to work for empty collections.
> Properties of the
Thanks a lot, Jason, I will try that. I tried 'fields=' expecting this would be
the same as 'fields=:all' , which is obviously wrong.
That's a very useful information - do you mind including it into the manual?
Regards, Uwe
---
> Jason Pickering hat am 16.
Hi Uwe,
I think the manual is correct, as it specifies how the paramater should be
called.
In general, we discourage actually using that "all" paramater, because
things can change from version to version (as you have noticed). Its better
to make explicit calls for the fields which you require for
Dear all,
I am having a bit of an issue when querying metadata from the api in json
format and further processing them in kettle (Pentaho DI): DHIS2 only returns
those properties in the json-package that are not NULL. However, the json
converter in kettle needs the full property-set in order
9 matches
Mail list logo