Hi Jasper,
okay. Compulsory data elements are not meant to block data entry form
submission.
Yes you could try using a validation rule. E.g. if this is numeric and is
supposed to be a positive value, you can create a validation rule saying
#{data element a} > 0
and then select "never skip" in
Hey Lars,
Thanks for the quick response!
We're actually running 2.22 here (as is the production Sierra Leone
national instance we're working in co-operation with I believe).
There seems to be some confusion with the functionality of compulsory data
elements though, in this previous thread you
Hi there,
1)
you are right, this was a bug that was fixed in 2.24. The problem is the
uniqueness constraint on data element + option combo which simply should
not be there.
dataelement_operand_unique_key
I have backported the fix to 2.23 as well now.
2)
Per now, the compulsory elements are
Hi all,
Any chance we could get a DHIS2 developer to respond to these issues with
compulsory data elements?
As I understand then, it seems to be two issues:
1.) Attempting to add data elements as compulsory to *certain* data sets
seems to result in a crash related to a uniqueness constraint
Hi Lars,
Regarding the Compulsory data element feature, it's still not been fixed. We've
tested on 2.22 and 2.23 with almost the result.
- From the 'Data Sets' screen in DHIS2
- Select a Data Set
- Right click it and then 'Edit Compulsory Data Elements'
- Attempt to add one of the
Hi All,
Am try to set certain data element as compulsory or mandatory in data set
but some reason the assigned compulsory data element does not seem to have
any effect on the data sets or forms. Forms or data sets can be completed
even though they contain compulsory data element. Is this a bug or
6 matches
Mail list logo
