revno: 16632
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Fri 2014-09-05 13:57:32 +0700
message:
minor
modified:
dhis-2/dhis-services/dhis-service-core/src/main/java/org/hisp/dhis/common/hibernate/HibernateIdentifiabl
Hi
I would like to share an SQL statement that would help you list all your
orgunits (code, coordinates, facility name, district, region, etc.) It is
tricky to query the same column "organisationunit.name" twice. Here is the
query:
SELECT ou.co
Hm, ok.. no we don't currently support that.
As a workaround, you could of course just do
?fields=:all,children[:all,children[:all]], i.e. :all,children[:all] for as
many levels as you have, its a bit of a hack, but it would work (if you add
too many, it will just be ignored)
If its only two, you
You mean children, or descendants? if you just want the full view of the
children of a few OUs you could probably get away with
?fields[:all,children[:all]] ?
--
Morten
On Fri, Sep 5, 2014 at 12:18 PM, Mahendra Kariya <
mahendra.kar...@thoughtworks.com> wrote:
> OK.
>
> So we need all fields f
On Fri, Sep 5, 2014 at 11:55 AM, Mahendra Kariya <
mahendra.kar...@thoughtworks.com> wrote:
> It looks like attributeValues field takes most of the time. We have around
> 6-7 custom attributes for each orgUnit. We don't need all of these. We only
> need the value of one particular attribute. Is th
revno: 16631
committer: Mithilesh Kumar Thakur
branch nick: dhis2
timestamp: Fri 2014-09-05 06:06:07 +0100
message:
local/in PBF work in progress
modified:
local/in/dhis-in-api/src/main/java/org/hisp/dhis/reports/ReportModel.java
l
revno: 16630
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Fri 2014-09-05 11:49:59 +0700
message:
more sharing tests, test for deletion, creation, usergroups, private objects,
etc.
modified:
dhis-2/dhis-services/dhis-
Do you need all fields? you could probably easily shave of a quite a few
bytes by only asking for the fields you need. We only support compression
on the /api/metadata endpoint (zip, gzip) and I would rather see
compression implemented in the caching server / proxy (nginx, lighty etc).
You can also
revno: 16629
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Fri 2014-09-05 10:07:24 +0700
message:
Minor fix
modified:
dhis-2/dhis-support/dhis-support-hibernate/src/main/java/org/hisp/dhis/hibernate/HibernateGenericSto
Hi Prosper
Date format was introduced together with calendar support in 2.16, but is
only supported in a few places where the date picker is used.
For 2.17 this also includes support for GIS, DV, PT, etc (support for this
has already been implemented in trunk/2.17), and hopefully there will also
revno: 16628
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Fri 2014-09-05 09:23:29 +0700
message:
minor test addition
modified:
dhis-2/dhis-services/dhis-service-core/src/test/java/org/hisp/dhis/common/SharingTest.java
Hi there,
As per the manual, the "average" option when defining data elements aggregates
by average over periods but sum over orgunits. This limits severely the
reporting possibilities, for instance when calculating the average person age
over multiple districts but I can think of many other ex
Hi Team,
Been testing calender setting changing from -mm-dd to dd-mm-
standard for Uganda date data entry, apparently it seems not be working on
the demo server 2.16.
I switched the calender setting tested with both individual records and
aggregate data, its not changing?
This is a bug
If you select a numeric data element, like "Age", you will see "Age 1",
"Age 2", "Age 3" etc in the table.
This is not the case for options as you make the option names yourself.
On Thu, Sep 4, 2014 at 5:58 PM, Prosper BT wrote:
> Thanks Jan,
>
> Understood.
>
> But for aggregate we are missin
Thanks Jan,
Understood.
But for aggregate we are missing the description of what is being
aggregated. i.e, If you pick a data element like ANC visit number with
Options 1, 2, 3, 4, 4+ you will only see the option with the respective
numbers, this works if you are working with one data element but
Yes, you are right.
*Text* attributes and data elements will explode the pivot table - that's
why we don't allow them to be dimensions (columns/rows) in the aggregated
mode.
On Thu, Sep 4, 2014 at 5:37 PM, Prosper BT wrote:
> Sorry ignore this,
>
> Had not realized I was running aggregates ins
Sorry ignore this,
Had not realized I was running aggregates instead of individual records
Apologies
On Thu, Sep 4, 2014 at 6:35 PM, Prosper BT wrote:
> Hi Team,
>
>
> Thanks for adding attributes into the program stages in the event reports,
> however all attributes are fixed to filter when
Hi Team,
Thanks for adding attributes into the program stages in the event reports,
however all attributes are fixed to filter when line listing data.
Line listing all data elements alongside the attributes helps in data
cleaning and exporting for further analysis.
Was this intended or its a bu
revno: 16627
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Thu 2014-09-04 20:03:35 +0700
message:
basic sharing tests + fixes
added:
dhis-2/dhis-services/dhis-service-core/src/test/java/org/hisp/dhis/common/SharingTest
revno: 16626
committer: Mithilesh Kumar Thakur
branch nick: dhis2
timestamp: Thu 2014-09-04 11:07:26 +0100
message:
local/in RBF work in progress
added:
local/in/dhis-web-maintenance-rbf/src/main/java/org/hisp/dhis/rbf/reportmanagem
revno: 16625
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Thu 2014-09-04 14:04:22 +0700
message:
fixes for sharing criteria
modified:
dhis-2/dhis-services/dhis-service-core/src/main/java/org/hisp/dhis/common/hibernate
21 matches
Mail list logo
