dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

On Thu, Dec 10, 2009 at 12:38 PM, Ola Hodne Titlestad
<olatitle@xxxxxxxxx>wrote:

> 2009/12/10 Lars Helge Øverland <larshelge@xxxxxxxxx>
>
> > Not entirely correct but there is a bug. The problem appears when you
> > want to crosstab on dimensions which have no fixed options, but rather
> > report parameters/relative periods. One example: You don't select any
> > periods but relative periods and you don't select any orgunits but the
> > parent orgunit report parameter. Then it is impossible to know the names
> > of the columns of the table as it will vary with which periods/orgunits
> > you select through the parameters.
> >
> > This is a bit tricky. Do we want to select report params and run the
> > table everytime we want to export it?
> >
> >
> So the difficulty is to define a custom view (display properties icon) on a
> report table that not really exists or that changes form every time new
> parameters are chosen?
>
> Every time we run a report table and put in the parameters the database
> table is recreated and that table works fine always.
>
> Why can't we then just export the default view (same as the recreated
> database table) every time the report table (incl. cross tabbed parameters)
> has been modified? At least then we are able to support Excel and CSV
> exports, which is an important feature.
>
> If someone wants to do custom design (reorder, rename, hide columns) of a
> report table then that user will also be aware of the fact that if the
> report tables is set up to have dynamic number of columns and headings
> (anything else than data elements or indicators crosstabbed on columns)
> then
> the design will have to change and be redone every time new parameters are
> chosen. This can be commented in the UI as well. I think that is
> acceptable.
> No one can custom design a table that doesn't exist (or for which we do not
> know the number of columns or their headings) anyway.
>
>
Yes this understanding is right and it should be possible to implement. Its
just that the current implementation is based on the ReportTable object, not
the database report table, so will have to think a bit of a way to do it...

-- 
Report table exports/views do not show columns or values when not cross-tabbed by data element
https://bugs.launchpad.net/bugs/494413
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: Triaged

Bug description:
Report tables -> any report table with orgunit and/or period set as cross-tab dimensions while data element is not cross-tabbed

The view or export of report tables only seem to work properly for tables that have data elements as one of the cross-tabbed dimensions.
If data element is not cross-tabbed then the cross tabbed columns are not shown at all and therefore no values either.