alternatives for while loop logic

Good day everyone,

As I’m unable to apply the logic of a while loop in the designer, I wanted to create a roster based on a categorical multiple-selection question, but my issue is that each category can only be selected once. What I was thinking was to map all the trips a person made during the day. So if someone leaves home, goes to work, and comes back—or leaves home, goes to work, returns home for lunch, and then goes out again—I run into the limitation that I can’t select the same categories multiple times. Would there be an alternative to select the category more than once?

I’m aware that I could use a numeric roster, but that doesn’t feel very intuitive, since people usually don’t know exactly how many trips they made in a day. I also considered a fixed roster, but that has similar issues: I wouldn’t know in advance how many trips there are, and I wouldn’t be able to restrict it properly using enabling conditions without running into circular reference problems (since the condition would have to be defined at the roster level).

I know I could also leave it as an open text field, but I’d prefer to avoid that because it could lead to measurement errors or make validation much harder.

So I feel like I’m very close with the multiple-selection approach, but I’m stuck on this limitation. Any ideas? Or would you suggest any other reasonable alternatives that would also be compatible in terms of usability?

What about having a list question that captures a short descriptions of trips and inside the trip roster a single-select categorical question records the trip type?

See “Public example User questions and common patterns” in public questionnaires, section “Activities journal” – that was possible until v5.25 and later discontinued due to problems that this approach has created.

Multiselect-triggered roster should be sufficient in this case (with a single-select for trip type inside the roster along with other details), as one wouldn’t need to invent the trip descriptions:

See also the “Time Use Module” (in public questionnaires) that I did for a discussion with ILO a couple of years ago:

As far as I know, they ended up not using it, but this example may demonstrate you some techniques on working with a sequence of activities in Survey Solutions (which just turn out to be trips in your case).