← Back to team overview

dhis2-devs team mailing list archive

Re: [Bug 1400085] Re: Detailed metadata export doesn't export catoptcombos

 

Yes in the same ballpark of the trickiness of moving the category model
(particularly bits of it) between systems.  But I think this bug is quite
particular.  The export is 90% correct just the pesky categoryoptioncombos
are left out.

On 7 December 2014 at 20:47, Pierre Dane <pierre@xxxxxxxxx> wrote:

> or at least related
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1400085
>
> Title:
>   Detailed metadata export doesn't export catoptcombos
>
> Status in DHIS 2:
>   New
>
> Bug description:
>   When you select a dataelement group in "Detailed Metadata Export" and
>   you export with dependencies, all datelements and categories and
>   categoryoptions are exported correctly.  The resulting metadata file
>   can be correctly imported into another blank system.
>
>   But there are no categoryoptioncombos.  So you cannot export/import
>   data for those dataelements.
>
>   The use case is that system A has a datelementgroup of dataelements
>   for which it needs to submit data periodically to system B.  For this
>   the categoryoptioncombos need to match.
>
>   Affects 2.16 rev 16576 and probably trunk.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dhis2/+bug/1400085/+subscriptions
>

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

Title:
  Detailed metadata export doesn't export catoptcombos

Status in DHIS 2:
  New

Bug description:
  When you select a dataelement group in "Detailed Metadata Export" and
  you export with dependencies, all datelements and categories and
  categoryoptions are exported correctly.  The resulting metadata file
  can be correctly imported into another blank system.

  But there are no categoryoptioncombos.  So you cannot export/import
  data for those dataelements.

  The use case is that system A has a datelementgroup of dataelements
  for which it needs to submit data periodically to system B.  For this
  the categoryoptioncombos need to match.

  Affects 2.16 rev 16576 and probably trunk.

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


References