Hi Victor,
Thanks for pointing this out. The "default" dataelementcategoryoption
should also have a null userid. I have now updated the trunk code to check
for this, and also updated the latest versions of 2.18 and 2.19. Hopefully
this will avoid further errors of this type (if people use the late
Hi Jim,
thanks for the explanation. To verify if it was a configuration error,
we have created a fresh dhis instance for versions 2.18 and 2.19, and
in both cases the initial value of publicaccess for "default"
dataelementcategoryoption is "--". Maybe it has been disconfigured
at some time.
I
Victor, thank you for the very good analysis. Do you know how your
"default" dataelementcategoryoption came to have publicaccess of "--"?
I would expect this to be a configuration error. Your fix sounds right.
The SQL code you refer to is critical when using a non-default category
combination
Thanks for all your help, the bug is related to java code and it's been
noticed to DHIS community in order to create a bug fix and release
another war file. From my side i am limited to a BAO dashboard. Thanks
once again and we are awaiting for the release of this war file
--
You received this bu
4 matches
Mail list logo
