Hi Team,
We have an app with multiple forms, and I use cases on this app. One of
the forms we fill every month for the same case. However, I notice that if
some questions are skipped (due to display logics), instead of retaining an
empty value, it retains the value that was last filled against this
question in the case. Is this an expected behaviour? How do I handle
this? Please note that on this form we are not loading any value to the
case, and we are only saving to the case.
To elaborate this with an example:
I have an app with multiple forms and we are using cases. The following
are two examples of the forms:
- Assessment Form
- Recommendations Form
On the assessment-form, I have a question on the "priority_need" (a single
select question) and followed by a "specify_need" (a text question). The
"specify_need" would be displayed if the "priority need" is selected as
"2". This form is expected to be filled every month for each
case/participant. In the case configuration, we save the "specify_need"
question, and do not load any cases to this form.
On the recommendations form, we are loading the value "specify_need" and
based on the value inside it, we display the appropriate questions. We
found that the "specify_need" is loading with an empty value, if that
question was skipped in the assessment form for the first time. This is
fine. However, if we have already filled a value for "specify_need" for
this case for this month, and then if it is skipped during next month, it
is still showing to the previous value (instead of keeping it as empty as
during this month this quesiton is skipped). Is this an expected behaviour
or am I making any wrong configurations? How do we handle this kind of
requirements?
Your kind guidance is highly appreciated.
Warm Regards,
Jeffrey
Jeffrey,
This is expected behavior, we intentionally don't update values directly
tied to questions which are Skipped in the form, since the user didn't
express an answer to the question.
If you want a value to be either set to a question's value or be blanked
out if it isn't asked you can create a Hidden Value which is set to the
value of the question, and set the case update to be set to the Hidden
Value. The hidden value won't be "skipped", so it will normalize to the
correct outcome.
-Clayton
ยทยทยท
On Mon, Jan 4, 2016 at 10:47 PM, Jeffrey Jose wrote:
Hi Team,
We have an app with multiple forms, and I use cases on this app. One of
the forms we fill every month for the same case. However, I notice that if
some questions are skipped (due to display logics), instead of retaining an
empty value, it retains the value that was last filled against this
question in the case. Is this an expected behaviour? How do I handle
this? Please note that on this form we are not loading any value to the
case, and we are only saving to the case.
To elaborate this with an example:
I have an app with multiple forms and we are using cases. The following
are two examples of the forms:
- Assessment Form
- Recommendations Form
On the assessment-form, I have a question on the "priority_need" (a single
select question) and followed by a "specify_need" (a text question). The
"specify_need" would be displayed if the "priority need" is selected as
"2". This form is expected to be filled every month for each
case/participant. In the case configuration, we save the "specify_need"
question, and do not load any cases to this form.
On the recommendations form, we are loading the value "specify_need" and
based on the value inside it, we display the appropriate questions. We
found that the "specify_need" is loading with an empty value, if that
question was skipped in the assessment form for the first time. This is
fine. However, if we have already filled a value for "specify_need" for
this case for this month, and then if it is skipped during next month, it
is still showing to the previous value (instead of keeping it as empty as
during this month this quesiton is skipped). Is this an expected behaviour
or am I making any wrong configurations? How do we handle this kind of
requirements?
Your kind guidance is highly appreciated.
Warm Regards,
Jeffrey
--
You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.