=== modified file 'src/docbkx/en/dhis2_user_man_web_api.xml' --- src/docbkx/en/dhis2_user_man_web_api.xml 2014-03-19 11:24:02 +0000 +++ src/docbkx/en/dhis2_user_man_web_api.xml 2014-03-19 18:44:22 +0000 @@ -4092,7 +4092,7 @@
- Tracked Entity Instances + Tracked entity instance query To query for tracked entity instances you can interact with the /api/trackedEntityInstances resource. This resource supports JSON, JSONP, XLS and CSV resource representations. @@ -4166,23 +4166,24 @@ Note that you can specify attributes with filters for constraining the instances to return, or attributes without filters in order to include the attribute in the response without any constraints. Attributes will be included in the response, while filters will only - be used as criteria. The following rules apply to the query parameters. + be used as criteria. + If specifying a query with no attributes or program, the attributes defined to be + displayed in lists with no program will be included in the response. The following rules apply + to the query parameters. At least one organisation unit must be specified using the ou parameter (one or many). - At least one of query and attribute parameters must be specified (one or both). - - Only one of the program and trackedEntity parameters can be specified (zero or one). - A query in its simplest form which will return all attributes in the response looks like + A query for all instances associated with a specific organisation unit can look like this: + api/trackedEntityInstances.json?ou=DiszpKrYNg8 + A query on all attributes for a specific value and organisation unit: api/trackedEntityInstances.json?query=wakiki&ou=DiszpKrYNg8 A query where the attributes to include in th response are specified looks like this: