We use a CSV import process every quarter to import aggregate data for some countries. We recently upgraded to 126.96.36.199-SNAPSHOT, and the Import/Export app no longer seems to be accepting our CSVs.
I’ve figured it out…If you have “require data elements to be part of data Set" checked, you are unable to import any data, regardless of if the data elements you’re trying to populate are in data sets. I think this is a bug. I’ve documented it in Jira.
@kstankevitz. Many thanks for the bug report. We’re discussing this internally and will work on fixing. We’re seeing a bit of confusion around the “require data elements to be part of data set” property, so let us know if you enabled this on purpose and if you would expect it to function differently.
Hi @tzemp - I think the use case being discussed on Jira makes sense for how we would use this feature - “prevent accidentally importing data for a data element that is no longer used and therefore no longer assigned to any data set”
But now that I think about it… this might actually be the default behavior… I’m not sure if it would let you import data for a DE that is not in a dataset, given that it wouldn’t be able to identify the relevant periods or AOCs for the DE…