dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

2 might be caused by translations for those elements. Import after
preview uses batch handlers and bypasses the translation stuff in the
service layer.

-- 
inconsistency in import/export module with preview option
https://bugs.launchpad.net/bugs/493514
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: Confirmed

Bug description:
I noticed some bugs related to the import export module :
1- when you want to preview during metadata import and then you click on import all, dhis does not import dataelement that are considered like "update" (see the attached log file)
2- I have exported data (a given dataset for a given facility and a given period) to a new and empty dhis2 db. In the new db I have edited the the values. The idea was to check whether dhis can import these edited value if I select preview option when I will import them back in the initial db. Unfortunately during this process(importing back into the initial db) a given set of the dataelements were shown like updates although I did not edit any dataelement.  So I did another export of the same dataset from the new database and it shown another set of dataelement as updates. The point is that dhis is not consistently matching the existing dataelements with the ones we are about to import. At least through the preview option.
3- I did the export data for a given dataset and a given period and facility. And when I tried to import the export file into the same db (the one the export file comes from), dhis was still saying considering some of the dataelement as updates.