I am trying approach 2 below because I don't have access to the system
generating the export file. Which tables should I mess around with?
Regards,
Moses
On Wednesday, 18 November 2015, Lars Helge Øverland
wrote:
> Some approaches:
>
> 1. Set the code property on all category option combos on
Some approaches:
1. Set the code property on all category option combos on both sides to be
the same. Then import the data using the import option /
property: categoryOptionComboIdScheme=CODE
https://www.dhis2.org/doc/snapshot/en/developer/html/ch01s12.html#d5e1541
2. Manually set the category o
Sorry, The import file is coming from a 2.19 system into a 2.20 system.
Previous, it was an import file coming from a 2.14 system to a 2.14 system.
The import file from a 2.14 system did not explicitly include the
attributeOptionCombo.
Now that the 2.19 export file is coming with the attributeOpti
Hi Moses,
On Mon, Nov 16, 2015 at 10:00 AM, Moses Marimo wrote:
> I have a system that I migrated from from DHIS2.14 to 2.20. In the 2.14,
> there was no attributeOptionCombo in the export file. The Datavalue table
> was populated with a default value of 15 in the attributeOptionComboID
> colu
I have a system that I migrated from from DHIS2.14 to 2.20. In the 2.14,
there was no attributeOptionCombo in the export file. The Datavalue table
was populated with a default value of 15 in the attributeOptionComboID
column.
After migrating the system, the export file from a 2.20 system now comes
Dear DHIS2 Users,
I recently upgraded two systems from 2.14 to 2.18. These two system
exchange data through XML import-export of data.
After the upgrade, I noted that data import stopped work. Infact, the
import will not throw any errors, but no data will be imported. On closer
examination, I not
6 matches
Mail list logo
