dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

Actually, I was mainly thinking about the logs. There was nothing of
much of interest at all in the log file that Roger posted, which is why
I created a bug and not a blueprint.

After messing a bit on my own machine, I got a more informative message:

"Caused by: org.h2.jdbc.JdbcSQLException: NULL not allowed for column
"NAME"; SQL statement:"

So the problem had nothing to do with IDs in this case, but seems to be
caused by a blank name, which was interpreted as NULL.

But would it not be feasible to pinpoint the place in the file that
caused this? Would not the information be readily available? I am
thinking primarily for the log, which is often too opaque and brief to
be really useful, and it's a hassle to step through these big DXF files
with thousands of orgunits.

-- 
missing-feedback-on-import-failure
https://bugs.launchpad.net/bugs/675527
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: New

Bug description:
When a DXF import fails, the user should get feedback on which XML element causes the failure, ideally with the line in the import file.