Re: [Dhis2-users] API 2.25: Return Full Property Set

[Ocaya Stephen]

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 using xml format ( if ok with U)
2. You will need to take back missing properties within your codes (
probably your previous work around)






On Dec 16, 2016 15:33, "Uwe Wahser"  wrote:

> 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 also think that it is not a DHIS issue and that the kettle converter
> should be able to do that. But DHIS developers are usually more responsive
> :-)
>
> I was hoping that it wouldn't be a big deal, as it works with csv.
> Implementing it as a parameter would also give the choice of using that
> feature if needed, thus avoiding inflated payloads per default.
>
> Anyway, I think I'll enjoy our Xmas party now. Maybe I that gives me
> better ideas on Monday :-D
>
> Thanks for looking at it,
>
> Uwe
>
>
>
> Sent with AquaMail for Android
> http://www.aqua-mail.com
>
> On 16 December 2016 12:54:17 Jason Pickering 
> wrote:
>
>> 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 in
>> the recent past.
>>
>> Maybe you should try and use CSV?
>>
>> https://play.dhis2.org/demo/api/organisationUnits.csv?
>> paging=false=level:eq:3=name,comment
>>
>> does produce an extra column (with NULLS).
>>
>> From the R standpoint (as well as other languages I think), its really up
>> to you to parse the payload as you need it, but its handled quite easily
>> for this case in R. Other times, the nested lists need to be flattened, if
>> that is what you require, but I do not see this as  DHIS2 issue really. It
>> would make little sense to include all of these NULLs where they do not
>> exist, as it could drastically increase the size of the payload. That is
>> why they are not included, except where not null.
>>
>> [image: Inline image 1]
>>
>>
>>
>> On Fri, Dec 16, 2016 at 10:41 AM, Uwe Wahser  wrote:
>>
>>> Hi Jason,
>>>
>>> simple example:
>>> https://play.dhis2.org/demo/api/organisationUnits.json?pagin
>>> g=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 created for the example), for all the other I
>>> only get the name property:
>>> [{"name":"Badjia","comment":"This is a comment."},{"name":"Bagruwa"},
>>> {"name":"Baoma"}...]
>>>
>>> Converting this package in kettle would result to an error message that
>>> 50 (or whatever) instances of name were found, but only 1 instance of
>>> comment. kettle expects always the complete set of properties for all
>>> objects. Not sure how R or others handle this ...
>>>
>>> If there was a query parameter like returnNull=true , that could give
>>> back the null properties like {"name":"Bagruwa","comment":""}, it would
>>> be possible to work with these packages. Actually I had expected this to be
>>> the default behaviour, when specifying fields.
>>>
>>> Best regards,
>>>
>>> Uwe
>>>
>>> ---
>>>
>>> > Jason Pickering  hat am 16. Dezember
>>> 2016 um 12:05 geschrieben:
>>> >
>>> >
>>> > 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 object itself (e.g. email, comments of
>>> organizationUnits)
>>> > > are still left out.
>>> > >
>>> > > The floor is open again for other suggestions :-)
>>> > >
>>> > > Regards, Uwe
>>> > >
>>> > > > Uwe Wahser  hat am 16. Dezember 2016 um 10:24
>>> > > geschrieben:
>>> > > >
>>> > > >
>>> > > > 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.
>>> Dezember
>>> > > 2016 um 10:13 geschrieben:
>>> > > > >

Re: [Dhis2-users] API 2.25: Return Full Property Set

[Uwe Wahser]

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 also think that it is not a DHIS issue and that the kettle converter 
should be able to do that. But DHIS developers are usually more responsive :-)


I was hoping that it wouldn't be a big deal, as it works with csv. 
Implementing it as a parameter would also give the choice of using that 
feature if needed, thus avoiding inflated payloads per default.


Anyway, I think I'll enjoy our Xmas party now. Maybe I that gives me better 
ideas on Monday :-D


Thanks for looking at it,

Uwe





Sent with AquaMail for Android
http://www.aqua-mail.com


On 16 December 2016 12:54:17 Jason Pickering  
wrote:



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 in the
recent past.

Maybe you should try and use CSV?

https://play.dhis2.org/demo/api/organisationUnits.csv?paging=false=level:eq:3=name,comment

does produce an extra column (with NULLS).

From the R standpoint (as well as other languages I think), its really up
to you to parse the payload as you need it, but its handled quite easily
for this case in R. Other times, the nested lists need to be flattened, if
that is what you require, but I do not see this as  DHIS2 issue really. It
would make little sense to include all of these NULLs where they do not
exist, as it could drastically increase the size of the payload. That is
why they are not included, except where not null.

[image: Inline image 1]



On Fri, Dec 16, 2016 at 10:41 AM, Uwe Wahser  wrote:


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 created for the example), for all the other I
only get the name property:
[{"name":"Badjia","comment":"This is a comment."},{"name":"Bagruwa"},
{"name":"Baoma"}...]

Converting this package in kettle would result to an error message that 50
(or whatever) instances of name were found, but only 1 instance of comment.
kettle expects always the complete set of properties for all objects. Not
sure how R or others handle this ...

If there was a query parameter like returnNull=true , that could give back
the null properties like {"name":"Bagruwa","comment":""}, it would be
possible to work with these packages. Actually I had expected this to be
the default behaviour, when specifying fields.

Best regards,

Uwe

---

> Jason Pickering  hat am 16. Dezember 2016
um 12:05 geschrieben:
>
>
> 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 object itself (e.g. email, comments of
organizationUnits)
> > are still left out.
> >
> > The floor is open again for other suggestions :-)
> >
> > Regards, Uwe
> >
> > > Uwe Wahser  hat am 16. Dezember 2016 um 10:24
> > geschrieben:
> > >
> > >
> > > 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. Dezember
> > 2016 um 10:13 geschrieben:
> > > >
> > > >
> > > > Hi Uwe
> > > > Have a look here
> > > >
> > > > https://ci.dhis2.org/docs/master/en/developer/html/
> > webapi_metadata_field_filter.html
> > > >
> > > > and specifically the use of  the ?fields=:all paramater.
> > > >
> > > > Regards,
> > > > Jason
> > > >
> > > >
> > > > On Fri, Dec 16, 2016 at 7:58 AM, Uwe Wahser  wrote:
> > > >
> > > > > 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 to
> > create
> > > > > a tabular structure from the data (don't know the reason for
that).
> > > > >
> > > > > Is there a way to force the api to return the full 

Re: [Dhis2-users] Event Capture - Search for an event in all Events of the selected Program

[Antonia - Pro]

Hi Lars,
many thanks for your activity for the improvement of the Searching and
sorting of events in the Event Capture App
*JIRA (DHIS2-254) Search for an event in all Events of the selected
Program,  (DHIS2-149) Searching and sorting of events.*

Is it already ported to the c. 2.25? If not, when it is planned?

For our users this features are important. Gust yesterday the ask for this
improvements:

*I have some suggestions about Capture event Page face and data entry, *

*First Previews table sorting (incident date) field data in all pages,
descending sort better than ascending sort.*

*Why? Because the Users can see last his saved data i.e. always (last data
saved) preview on the user screen, so user know end work time!*



*Searching operation in any fields should be searching all pages at the
same time.*

*For example we want to find (Suha Samir) patient name, it must display
whit out we will search page by page. *

*According to print operation, when we will select (All) option it must
print all data saved in our data base ... please check it be carefully!*

*Hama Kh. Hama -  Qaladze Hospital*

Thanks
Antonia



> -- Forwarded message --
> From: Lars Helge Øverland (JIRA) 
> Date: 2016-12-15 17:54 GMT+01:00
> Subject: [dhis2-issue] (DHIS2-254) Search for an event in all Events of
> the selected Program
> To: anto...@informa.pro
>
>
>   Lars Helge Øverland
> 
> *updated* [image: Improvement] DHIS2-254
> 
>
> DHIS 2  / [image: Improvement]
>  DHIS2-254
> 
> Search for an event in all Events of the selected Program
> 
> Change By: Lars Helge Øverland
> 
> Resolution: Done
> Status: Testing Done
> [image: Add Comment]
>   Add Comment
> 
>
> This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)
> [image: Atlassian logo]
>
>
>
> 2016-11-23 0:44 GMT+01:00 Antonia - Pro :
>
>> Actually when I make a search in the Event Capture window, the search is
>> limited to the only visible page of the events for the selected Program
>> (for the specific OrgUnit).
>> Probably the search is made on the client side.
>> It will be very useful if the search is made on the server side and the
>> output of the search are all events in the selected program, which meet he
>> search filter, not only in the visualized page.
>> For example, when an verification audit is done and some strange value is
>> found by the statistics, we have to find the event with this value to
>> correct or examine it.
>> When the events in the program are not too much, we can scroll the pages,
>> or make a biggest page with more than the default 50 events (200, 500). But
>> when the events are more than 10 000 or 50 000 it is inconvenient.
>> It will be more useful and faster  to make the search as a query with the
>> search filter to the server and than visualize the output result of the
>> query on the Event Capture window.
>> [image: Immagine incorporata 1]
>>
>> ...
>> [image: Immagine incorporata 2]
>>
>> I created an issue with the new JIRA for issue tracking, I hope I done it
>> well.
>>
>> DHIS 2
>> DHIS2-254 
>>
>> Thanks
>> Antonia
>>
>>  www.informa.pro - *Seguici su *LinkedIn
>> 
>> INFORMAPRO S.r.l. - via Luigi Rava 43,  Rome 00149 , Italy
>> tel. +39 06 5758926 <+39%2006%20575%208926>, fax +39  06 62207168, P.IVA
>> IT08095781004
>> Skype: informa_antonia.bezenchek
>> Eng. Antonia Bezenchek - CIO - ICT Engineer
>>
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Event Capture - Search for an event in all Events of the selected Program

[Antonia - Pro]

Hi Lars,
many thanks for your activity for the improvement of the Searching and
sorting of events in the Event Capture App
*JIRA (DHIS2-254) Search for an event in all Events of the selected
Program,  (DHIS2-149) Searching and sorting of events.*

Is it already ported to the c. 2.25? If not, when it is planned?

*I have some suggestions about Capture event Page face and data entry, *

*First Previews table sorting (incident date) field data in all pages,
descending sort better than ascending sort.*

*Why? Because the Users can see last his saved data i.e. always (last data
saved) preview on the user screen, so user know end work time!*



*Searching operation in any fields should be searching all pages at the
same time.*

*For example we want to find (Suha Samir) patient name, it must display
whit out we will search page by page. *

*According to print operation, when we will select (All) option it must
print all data saved in our data base ... please check it be carefully!*


Is the feature available

-- Forwarded message --
From: Lars Helge Øverland (JIRA) 
Date: 2016-12-15 17:54 GMT+01:00
Subject: [dhis2-issue] (DHIS2-254) Search for an event in all Events of the
selected Program
To: anto...@informa.pro


  Lars Helge Øverland

*updated* [image: Improvement] DHIS2-254


DHIS 2  / [image: Improvement]
 DHIS2-254

Search for an event in all Events of the selected Program

Change By: Lars Helge Øverland

Resolution: Done
Status: Testing Done
[image: Add Comment]
  Add
Comment 

This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)
[image: Atlassian logo]



2016-11-23 0:44 GMT+01:00 Antonia - Pro :

> Actually when I make a search in the Event Capture window, the search is
> limited to the only visible page of the events for the selected Program
> (for the specific OrgUnit).
> Probably the search is made on the client side.
> It will be very useful if the search is made on the server side and the
> output of the search are all events in the selected program, which meet he
> search filter, not only in the visualized page.
> For example, when an verification audit is done and some strange value is
> found by the statistics, we have to find the event with this value to
> correct or examine it.
> When the events in the program are not too much, we can scroll the pages,
> or make a biggest page with more than the default 50 events (200, 500). But
> when the events are more than 10 000 or 50 000 it is inconvenient.
> It will be more useful and faster  to make the search as a query with the
> search filter to the server and than visualize the output result of the
> query on the Event Capture window.
> [image: Immagine incorporata 1]
>
> ...
> [image: Immagine incorporata 2]
>
> I created an issue with the new JIRA for issue tracking, I hope I done it
> well.
>
> DHIS 2
> DHIS2-254 
>
> Thanks
> Antonia
>
>  www.informa.pro - *Seguici su *LinkedIn
> 
> INFORMAPRO S.r.l. - via Luigi Rava 43,  Rome 00149 , Italy
> tel. +39 06 5758926 <+39%2006%20575%208926>, fax +39  06 62207168, P.IVA
> IT08095781004
> Skype: informa_antonia.bezenchek
> Eng. Antonia Bezenchek - CIO - ICT Engineer
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] API 2.25: Return Full Property Set

[Jason Pickering]

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 in the
recent past.

Maybe you should try and use CSV?

https://play.dhis2.org/demo/api/organisationUnits.csv?paging=false=level:eq:3=name,comment

does produce an extra column (with NULLS).

>From the R standpoint (as well as other languages I think), its really up
to you to parse the payload as you need it, but its handled quite easily
for this case in R. Other times, the nested lists need to be flattened, if
that is what you require, but I do not see this as  DHIS2 issue really. It
would make little sense to include all of these NULLs where they do not
exist, as it could drastically increase the size of the payload. That is
why they are not included, except where not null.

[image: Inline image 1]



On Fri, Dec 16, 2016 at 10:41 AM, Uwe Wahser  wrote:

> 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 created for the example), for all the other I
> only get the name property:
> [{"name":"Badjia","comment":"This is a comment."},{"name":"Bagruwa"},
> {"name":"Baoma"}...]
>
> Converting this package in kettle would result to an error message that 50
> (or whatever) instances of name were found, but only 1 instance of comment.
> kettle expects always the complete set of properties for all objects. Not
> sure how R or others handle this ...
>
> If there was a query parameter like returnNull=true , that could give back
> the null properties like {"name":"Bagruwa","comment":""}, it would be
> possible to work with these packages. Actually I had expected this to be
> the default behaviour, when specifying fields.
>
> Best regards,
>
> Uwe
>
> ---
>
> > Jason Pickering  hat am 16. Dezember 2016
> um 12:05 geschrieben:
> >
> >
> > 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 object itself (e.g. email, comments of
> organizationUnits)
> > > are still left out.
> > >
> > > The floor is open again for other suggestions :-)
> > >
> > > Regards, Uwe
> > >
> > > > Uwe Wahser  hat am 16. Dezember 2016 um 10:24
> > > geschrieben:
> > > >
> > > >
> > > > 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. Dezember
> > > 2016 um 10:13 geschrieben:
> > > > >
> > > > >
> > > > > Hi Uwe
> > > > > Have a look here
> > > > >
> > > > > https://ci.dhis2.org/docs/master/en/developer/html/
> > > webapi_metadata_field_filter.html
> > > > >
> > > > > and specifically the use of  the ?fields=:all paramater.
> > > > >
> > > > > Regards,
> > > > > Jason
> > > > >
> > > > >
> > > > > On Fri, Dec 16, 2016 at 7:58 AM, Uwe Wahser  wrote:
> > > > >
> > > > > > 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 to
> > > create
> > > > > > a tabular structure from the data (don't know the reason for
> that).
> > > > > >
> > > > > > Is there a way to force the api to return the full property set,
> > > e.g. a
> > > > > > secret flag? I'd actually expect to get the full list - even if
> the
> > > > > > property is NULL -, at least when I specify a list of properties
> in
> > > the
> > > > > > field-filter ...
> > > > > >
> > > > > > Of course, I could also ask the kettle-guys to be a bit more
> > > flexible, but
> > > > > > normally they are not as agile as the DHIS2-DEVs ;-)
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Uwe
> > > > > >
> > > > > > ___
> > > > > > Mailing list: https://launchpad.net/~dhis2-users
> > > > > > Post to : dhis2-users@lists.launchpad.net
> > > > > > Unsubscribe : https://launchpad.net/~dhis2-users
> > > > > > More help   : 

Re: [Dhis2-users] API 2.25: Return Full Property Set

[Uwe Wahser]

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 created for the example), for all the other I only 
get the name property:
[{"name":"Badjia","comment":"This is a 
comment."},{"name":"Bagruwa"},{"name":"Baoma"}...]

Converting this package in kettle would result to an error message that 50 (or 
whatever) instances of name were found, but only 1 instance of comment. kettle 
expects always the complete set of properties for all objects. Not sure how R 
or others handle this ...

If there was a query parameter like returnNull=true , that could give back the 
null properties like {"name":"Bagruwa","comment":""}, it would be possible to 
work with these packages. Actually I had expected this to be the default 
behaviour, when specifying fields.

Best regards, 

Uwe

---

> Jason Pickering  hat am 16. Dezember 2016 um 
> 12:05 geschrieben:
> 
> 
> 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 object itself (e.g. email, comments of organizationUnits)
> > are still left out.
> >
> > The floor is open again for other suggestions :-)
> >
> > Regards, Uwe
> >
> > > Uwe Wahser  hat am 16. Dezember 2016 um 10:24
> > geschrieben:
> > >
> > >
> > > 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. Dezember
> > 2016 um 10:13 geschrieben:
> > > >
> > > >
> > > > Hi Uwe
> > > > Have a look here
> > > >
> > > > https://ci.dhis2.org/docs/master/en/developer/html/
> > webapi_metadata_field_filter.html
> > > >
> > > > and specifically the use of  the ?fields=:all paramater.
> > > >
> > > > Regards,
> > > > Jason
> > > >
> > > >
> > > > On Fri, Dec 16, 2016 at 7:58 AM, Uwe Wahser  wrote:
> > > >
> > > > > 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 to
> > create
> > > > > a tabular structure from the data (don't know the reason for that).
> > > > >
> > > > > Is there a way to force the api to return the full property set,
> > e.g. a
> > > > > secret flag? I'd actually expect to get the full list - even if the
> > > > > property is NULL -, at least when I specify a list of properties in
> > the
> > > > > field-filter ...
> > > > >
> > > > > Of course, I could also ask the kettle-guys to be a bit more
> > flexible, but
> > > > > normally they are not as agile as the DHIS2-DEVs ;-)
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Uwe
> > > > >
> > > > > ___
> > > > > Mailing list: https://launchpad.net/~dhis2-users
> > > > > Post to : dhis2-users@lists.launchpad.net
> > > > > Unsubscribe : https://launchpad.net/~dhis2-users
> > > > > More help   : https://help.launchpad.net/ListHelp
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jason P. Pickering
> > > > email: jason.p.picker...@gmail.com
> > > > tel:+46764147049
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~dhis2-users
> > > Post to : dhis2-users@lists.launchpad.net
> > > Unsubscribe : https://launchpad.net/~dhis2-users
> > > More help   : https://help.launchpad.net/ListHelp
> >
> 
> 
> 
> -- 
> Jason P. Pickering
> email: jason.p.picker...@gmail.com
> tel:+46764147049

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Sharing settings for data set reset when new org units assigned

[Shurajit Dutta]

Thanks Lars, will do

On Fri, Dec 16, 2016 at 3:06 PM, Lars Helge Øverland  wrote:

> Hi Nick,
>
> thanks for reporting and reproducing the issue. Can you please report it
> on JIRA  together with the exact steps for
> reproducing it?
>
> regards,
>
> Lars
>
>
> On Fri, Dec 16, 2016 at 5:34 AM, Shurajit Dutta 
> wrote:
>
>> Hi everyone,
>>
>> I notice that if I set up sharing settings for a data set, but then later
>> on assign this data set to new org units, all of the sharing settings for
>> the user groups I have selected for that data set are reset. I have tried
>> this on both 2.24 locally as well as 2.25 on play.dhis2.org/demo.
>>
>> Is this by design?
>>
>> Nick
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>


-- 
Shurajit Dutta
Health Information Consultant
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Sharing settings for data set reset when new org units assigned

[Antonia - Pro]

It happens to me the same thins with the s*haring settings of the favorites
in the Event Report tables*. On the ver. 2.22, we used before the settings
do not changed when change the name or overwrite the table, on the v.2.25
the sharing settings are reset on every change.


2016-12-16 10:01 GMT+01:00 Shurajit Dutta :

> Thanks Lars, will do
>
> On Fri, Dec 16, 2016 at 3:06 PM, Lars Helge Øverland 
> wrote:
>
>> Hi Nick,
>>
>> thanks for reporting and reproducing the issue. Can you please report it
>> on JIRA  together with the exact steps for
>> reproducing it?
>>
>> regards,
>>
>> Lars
>>
>>
>> On Fri, Dec 16, 2016 at 5:34 AM, Shurajit Dutta 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> I notice that if I set up sharing settings for a data set, but then
>>> later on assign this data set to new org units, all of the sharing settings
>>> for the user groups I have selected for that data set are reset. I have
>>> tried this on both 2.24 locally as well as 2.25 on play.dhis2.org/demo.
>>>
>>> Is this by design?
>>>
>>> Nick
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> l...@dhis2.org
>> http://www.dhis2.org 
>>
>>
>
>
> --
> Shurajit Dutta
> Health Information Consultant
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] API 2.25: Return Full Property Set

[Jason Pickering]

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 object itself (e.g. email, comments of organizationUnits)
> are still left out.
>
> The floor is open again for other suggestions :-)
>
> Regards, Uwe
>
> > Uwe Wahser  hat am 16. Dezember 2016 um 10:24
> geschrieben:
> >
> >
> > 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. Dezember
> 2016 um 10:13 geschrieben:
> > >
> > >
> > > Hi Uwe
> > > Have a look here
> > >
> > > https://ci.dhis2.org/docs/master/en/developer/html/
> webapi_metadata_field_filter.html
> > >
> > > and specifically the use of  the ?fields=:all paramater.
> > >
> > > Regards,
> > > Jason
> > >
> > >
> > > On Fri, Dec 16, 2016 at 7:58 AM, Uwe Wahser  wrote:
> > >
> > > > 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 to
> create
> > > > a tabular structure from the data (don't know the reason for that).
> > > >
> > > > Is there a way to force the api to return the full property set,
> e.g. a
> > > > secret flag? I'd actually expect to get the full list - even if the
> > > > property is NULL -, at least when I specify a list of properties in
> the
> > > > field-filter ...
> > > >
> > > > Of course, I could also ask the kettle-guys to be a bit more
> flexible, but
> > > > normally they are not as agile as the DHIS2-DEVs ;-)
> > > >
> > > > Best regards,
> > > >
> > > > Uwe
> > > >
> > > > ___
> > > > Mailing list: https://launchpad.net/~dhis2-users
> > > > Post to : dhis2-users@lists.launchpad.net
> > > > Unsubscribe : https://launchpad.net/~dhis2-users
> > > > More help   : https://help.launchpad.net/ListHelp
> > > >
> > >
> > >
> > >
> > > --
> > > Jason P. Pickering
> > > email: jason.p.picker...@gmail.com
> > > tel:+46764147049
> >
> > ___
> > Mailing list: https://launchpad.net/~dhis2-users
> > Post to : dhis2-users@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~dhis2-users
> > More help   : https://help.launchpad.net/ListHelp
>



-- 
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+46764147049
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Sharing settings for data set reset when new org units assigned

[Knut Staring]

I really like the video, Nick. May not always be needed of course, but very
good way of documenting complex bugs.


On Dec 16, 2016 09:32, "Shurajit Dutta"  wrote:

> After further testing this seems to happen after I update an object. Have
> tried with category options, categories and data sets. I add sharing
> settings, change something (like the name field, or assign a new org unit,
> etc.) save/update the object and then sharing is reset. The user groups are
> still listed but all read/write settings are reset. This is all on
> play.dhis2.org/demo
>
> Small video here:
> https://drive.google.com/open?id=0B9cgz2MOOXtcQWR1ZHdKeks0ckE
>
>
> On Fri, Dec 16, 2016 at 2:17 PM, Knut Staring  wrote:
>
>> If that's correct (have not tested), it is a pretty critical bug
>>
>> On Dec 16, 2016 05:34, "Shurajit Dutta"  wrote:
>>
>>> Hi everyone,
>>>
>>> I notice that if I set up sharing settings for a data set, but then
>>> later on assign this data set to new org units, all of the sharing settings
>>> for the user groups I have selected for that data set are reset. I have
>>> tried this on both 2.24 locally as well as 2.25 on play.dhis2.org/demo.
>>>
>>> Is this by design?
>>>
>>> Nick
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>
>
> --
> Shurajit Dutta
> Health Information Consultant
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] Sharing settings for data set reset when new org units assigned

[Lars Helge Øverland]

Hi Nick,

thanks for reporting and reproducing the issue. Can you please report it on
JIRA  together with the exact steps for reproducing
it?

regards,

Lars


On Fri, Dec 16, 2016 at 5:34 AM, Shurajit Dutta 
wrote:

> Hi everyone,
>
> I notice that if I set up sharing settings for a data set, but then later
> on assign this data set to new org units, all of the sharing settings for
> the user groups I have selected for that data set are reset. I have tried
> this on both 2.24 locally as well as 2.25 on play.dhis2.org/demo.
>
> Is this by design?
>
> Nick
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp