commcare
When making a hidden value question and filling in the Default Value with a question, CommCare gives me a warning.
What is the difference here between Default Value and Calculate condition? And why would a Default Value that references a question cause an error?
One way to accomplish this is by loading the label text in a hidden variable's Calculate Condition and then reference that variable later.
Add the label text to the Calculate Condition of a hidden variable question type. For example, my_label_text
You can drag and drop that hidden variable, my_label_text, into the label portion of the question:
You can then add logic to save my_label_text as a case property in the Case Management tab. In your scenario you may also want to add logic to save whether or not the question was answered properly.
If you're filtering cases, you want an expression that ultimately returns a set of cases. The first part of the expression, instance('casedb')/casedb/case, gives you all cases on the phone.
The expressions in square brackets then filter the cases by case type, parent (you're limiting to cases that are children of the "current" case, which is the one you selected from the case list), and open/closed.
[@case_type='Indicators']
[index/parent=current()/@case_id]
[@status='open']
The /[contractions_dur = 'low'] is what's throwing the error. The / says to go another level deep, but I suspect what you want is to just add the contractions_dur as a fourth constraint, on the same level as the others. So try dropping the slash: instance('casedb')/casedb/case[@case_type='Indicators'][index/parent=current()/@case_id][@status='open'][contractions_dur = 'low']
Best Answer
Great question! You seem like a swell dude.
The main difference between a calculate condition and default value is when the calculation will occur. Specifically, a default value will only be set once immediately upon opening the form. This is used primarily to load static values like case and session properties into the form.
Meanwhile, a calculate condition will fire multiple times during form entry (including at completion) so that its value always reflects the current state of the form accurately. This should be used for most purposes as calculates will be re-calculated based on answers given in the form.