Hello,
just take care (as generally with back-referencing repeats):
- If the user goes back and deselects (or changes) any choice which was base of the repeat(index), the values get mixed-up wrong. See example below
- choice 1, 2, 3
- edit amount in repeat
- go back and deselect 2
System now automatically maps amount from 3 (banana) to 3 (orange). That would be wrong from data content.
(Exception, no mix-up if only the last item was deselected.)
This is a very general problem, as the KoBo back-reference is by index and not by static id-reference. The only solution we found so far to avoid such mix-up, is to control if the repeat_count rep. the referenced items changed, and force the user to delete (or reedit) first all references after the deselected element, before he can go on (or successfully validate)
Any better solutions would highly been appreciated.
A similar problem and mix-up happens for ex. if you have a (dynamic) HH roster and then repeating education data per person, And after entering education data, the user goes back and deletes a referenced person (but not the last one) in the HH roster…
Kind regards
-
- select 1, 2, 3 and enter amount
- select 1, 2, 3 and enter amount
- Now go back and deselect 2 (banana).
Data get mix-upped:
.
