Good day all,
We use a custom-developed handheld device to collect data at the community-level, which is then downloaded in a DHIS2-appropriate CSV format using an external program. The CSV file is subsequently imported into the DHIS2 instance using event import.
The external program creates a Tracker capture CSV file that populates the “Event date” column, but leaves the “Due date” column empty. This format has been using for at least 4 years without any problems.
We have recently upgraded our instance to 2.33.10, after which our event import failed and simply gave the message “Error”. Through a process of elimination we realised that the CSV requires the “Due date” column to be populated for the import to succeed after our most recent instance upgrade.
As it will be nearly impossible for us to update the external program that generates the CSV’s, is it possible to have the upgraded instance once again “disregard” the “Due date” column in the CSV?
Any guidance/advice/assistance would be greatly appreciated.