Public bug reported:
Using the latest version of 2.21 (8 April 2016), we have defined one
attribute called "Driver's License" as have data type Yes/No.
In the Tracker Capture form, this attribute is showing up with scrambled
radio buttons:
1. There are three buttons instead of 2
2. The words
Abyot,
That is a generic question:
In general, I would say that a null value should not be accepted for a
yes/no field - if you want to store "unknown", then create a data element
with those three options (Yes, No, Unknown).
In practice, you can deal with it in two ways:
- use a default choice
Dear all
MSF Spain is expanding the technical HIS team.
The position is based in Spain (Barcelona) with shorts visit to the field
for training and technical support.
Please see more details on the position and how to apply following this
link.
Public bug reported:
DHIS 2.21 when performing an analytics update, analytics fails, returning the
error:
---
* ERROR 2016-04-08 13:29:32,627 Unexpected error occurred in scheduled task.
(TaskUtils.java [taskScheduler-2])
Hi Calle,
Thank you for reporting.
I will fix for the display. We have three buttons because it allows to
reset a value. What will happen if the question of "Driver's License" is
not answered (neither yes nor no) ?
--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
Fixed :)
** Changed in: dhis2
Status: New => Invalid
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1567826
Title:
[api] /api/userSettings endpoint throws a null pointer
Status in DHIS:
Public bug reported:
Heya,
When requesting the userSettings endpoint for all userSettings, the
current version of trunk (Version: 2.23-SNAPSHOT, Build revision: 22650)
throws a Null pointer exception.
https://play.dhis2.org/dev/api/userSettings.json
Regards,
Mark
** Affects: dhis2
Thanks Morten, Jim, Abyot,
Abyot:
Is the point of restricting a super user moot though since the super user
has the *ability* to assign themselves to whatever they like? It feels like
an extra step that shouldn't be needed for a superuser.
But, if there is indeed a need for the functionality to
Perhaps it was just an oversight in the code, forgetting to check for the
"ALL" authority in addition to the particular authority?
I would certainly expect "ALL" to grant the same access as all authorities.
It would surprise me if there is any good rationale to make it otherwise.
On Thu, Apr 7,
Hi,
It was like that before I think I changed it because at some point
there was a discussion saying we have to be careful on granting blanket
access in tracker.
One could be a superuser, but does this really mean this user will have
access to clinical data, names and everything implicitly?
Hi Laura!
The error means that you have a variable named #{DatacheckCD4} that will be
populated with data. The problem with the variable is that when you created it
you configured it to get its value from data element X, but it seems that data
element X is no longer part of the program. Did you
11 matches
Mail list logo
