Repeat_count and being_repeat

User Support Data Collection
, ,
1

Hi
I work a lot with KoboToolbox and particularly XLSForms.

I want to bring to the attention of Kobo Community and Team on some issues within Kobo collect app which has to do with linking for example number of household members (type: integer) to the repeat_count column for being_repeat.

Assuming I enter household members to be 4 and I enter details of 3 member and I go back to correct the hh members to 3 and swipe forward the app still requires me to enter details of the 4th person before I can proceed. And also vice versa if i swipe to increase number of hh members the app doesn’t increase the begin_repeat slots.

I would be glad if this issue can be fixed or if there’s a way around it I would be glad to know.

2

Welcome to the community, @Josh_Hods! Would you want us to test this out in the Collect Android App?

3

Actually the post is what I experienced using the collect android app.

4

I believe this is strictly ‘working as designed’ (if not as desired…) in KoboCollect/ODK Collect. See #45 repeat-groups are not respecting the jr:count setting after a change to a lower value by mdudzinski · Pull Request #61 · getodk/javarosa · GitHub

Specifically note the last comment from the maintainer of Collect (upon which KoboCollect is wholly based): “This continues to be considered intended behavior.”

There is also some discussion of this issue here: Collect: Repeat instances not removed after repeat_count was reduced - #7 by Sjlver - Support - ODK Forum. Again, I note this has been a known issue in Collect for a while, but - because it would be non-trivial to fix (and doing so may result in undesirable data loss) - I dont expect it to change any time soon.

Please take a look at the above discussion threads above for possible ways to mitigate. In particular: “Hiding extra repeats when the repeat count is reduced”