dhis2-devs team mailing list archive

["Dave Palmer \(MSI\)" <david.palmer@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Discovered in v2.22

Using the event export function, selecting 'include descendants of
organisation unit'.

We could see events in the event reports for a level 6 org unit, for
which we wanted to export the events into CSV. Using the event export
function, we selected the level 3 org unit this level 6 org unit
belonged to and 'include descendants of organisation unit'. However, the
export did not include all the events we expected. E.g. for time period
2016-01-01 to 2016-05-31 we were missing events recorded on 2016-02-22


However, when narrowing the search... either selecting the level 5 org unit instead of the level 3 parent, or reducing the time period to 2016-02-01 to 2016-02-28, the events would appear in the export!

This is a serious issue stopping our users using the event export
function... since they are unsure as to what parameters to use to ensure
a reliable export.

** Affects: dhis2
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1580286

Title:
  Event export does not export all events when selecting 'all
  descendents'

Status in DHIS:
  New

Bug description:
  Discovered in v2.22

  Using the event export function, selecting 'include descendants of
  organisation unit'.

  We could see events in the event reports for a level 6 org unit, for
  which we wanted to export the events into CSV. Using the event export
  function, we selected the level 3 org unit this level 6 org unit
  belonged to and 'include descendants of organisation unit'. However,
  the export did not include all the events we expected. E.g. for time
  period 2016-01-01 to 2016-05-31 we were missing events recorded on
  2016-02-22

  
  However, when narrowing the search... either selecting the level 5 org unit instead of the level 3 parent, or reducing the time period to 2016-02-01 to 2016-02-28, the events would appear in the export!

  This is a serious issue stopping our users using the event export
  function... since they are unsure as to what parameters to use to
  ensure a reliable export.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1580286/+subscriptions