Creating a choice filter (with multiple conditions) through an if-statement

Hi Team,

While working in kobo to develop form, I face issues to keep multiple filters. In the Kobo, is there two option to keep filters,like
a=${q06} and b=${q07}
Here, filter a and filter b need to match to view the filter result of q09.

q06 ask Degree that achieved?
option:
School-level…1
Higher Edcuation …2
University Education …3

q07 ask, Area of work?
Farming …1
Business…2
Employment …3

q09 ask, activities what work daily
activity1…1
activity2…2
activity3…3
activity4…4
activity5 …5
activity6…6

here, when respondent responses 1 of q06 and 1 of q07, show activity list of 1-3 of question number q09.

Is there any provision to use the multiple-choice option here in kobo in this condition?

@peshal, is q06, q07 and q09 all select_one question type?

Yes, all are select_one question type.

OK, you could do it as outlined in the image shared below:

In the survey tab of your XLSForm:

In the choices tab of your XLSForm:

image

Data entry screen as seen in Enketo: when nothing is entered

Data entry screen as seen in Enketo: when condition 1 is satisfied

Data entry screen as seen in Enketo: when condition 2 is satisfied

Data entry screen as seen in Enketo: when condition 3 is satisfied

Data entry screen as seen in Enketo: _when neither of the conditions is satisfied

Reference XLSForm:

Choice Filter with If Statement.xlsx (12.7 KB)

2 Likes

Many thanks for the guidance of multiple filter development, Most of the issues has solved beside on
Problems in development.

Q. Education Types
A
B
C

Q. Capacity measurement
Capacity1
Capacity2
Capacity3
capacity4
capacity5
capacity6
capaicity7
capacity8
capacity9
capacity10

all the selection is a single selection

if the respondent answer education A, the capacity should show 1,2,3,4,5
if the respondent answer education B, the capacity should show 3,4,5,6,7
if the respondent answer education C, the capacity should show 6,8,9,10

I try to work to solve the issues based on your feedback of above, but I could not solve.

@peshal, if you look closely at the workaround provide above it should solve this issue too.