dhis2-devs team mailing list archive

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

Public bug reported:

Found in v2.22

When uploading data (through a CSV file in our case) we used to be able
to load with a mixture of UIDs for data element, cat option combo and
Code for org unit.

Now after upgrading to v2.22 (rev 21297) this fails saying the code is
not found or not accessible. This is after setting the dropdowns for
whether each field is a UUID or code appropriately.

If we change everything to UUIDs the import works fine.

If we import via the API and specify which are codes e.g.
/api/dataValueSets?orgUnitIdScheme=code the import also works fine.

So it seems the web interface is now defaulting everything to either
UUID or codes rather than setting fields individually.

** 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/1586004

Title:
  Data import fails to match on codes through web UI (v2.22)

Status in DHIS:
  New

Bug description:
  Found in v2.22

  When uploading data (through a CSV file in our case) we used to be
  able to load with a mixture of UIDs for data element, cat option combo
  and Code for org unit.

  Now after upgrading to v2.22 (rev 21297) this fails saying the code is
  not found or not accessible. This is after setting the dropdowns for
  whether each field is a UUID or code appropriately.

  If we change everything to UUIDs the import works fine.

  If we import via the API and specify which are codes e.g.
  /api/dataValueSets?orgUnitIdScheme=code the import also works fine.

  So it seems the web interface is now defaulting everything to either
  UUID or codes rather than setting fields individually.

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