getodk / getodk/docs

Warn about dangers of dynamic repeat

Open
#1,464 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
58
Forks
160
Avg merge
5d 11h
Merged PRs (30d)
12

Description

One caveat with dynamic repeats is that if you go back and modify what was selected (either edits in Collect before sending or during edits on Central), the data inside the repeat is discarded when you change the selection. Ordering also changes.

In general, it's good to add an explicit hint in the select to warn users of this behavior and/or have a trigger that clears some required values if the select changes so users can't proceed without the updated data.

Contributor guide

Open the contributing guide

Research direction

Start by locating the Sphinx documentation covering dynamic repeats, selections, and edits in Collect or Central. Document the data-loss and ordering caveats, and clarify whether the expected result is a warning in the select documentation, guidance about clearing dependent values, or both.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.