You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 29, 2021. It is now read-only.
We're using the (lovely) KoboToolbox to create XForms for a custom mobile app (not Kobo/ODK Collect), and want to use existing XForm groups to define both sections within a page (ie grouping related controls visually within a section) as well as defining pages themsleves. For the latter we can use the existing "Show all questions in this group on the same page" (aka form-list appearance) to define a new page. The problem is, this option is hidden in the KoboToolbox form builder GUI whenever your group happens to contain a subgroup; or, in our interpretation, a page containing sections.
It would deduce there is probably explicit code in dkobo to check for subgroups, and hide the parent group's form-list option in settings if any are found. Could we make a request not to do this? That is, allow users to add the form-list appearance to any group, irrespective of what that group contains (controls, subgroups, whatever), and instead let the client interpret the group appearance as they see fit? This should not break any existing deployments; because ODK Collect presently has no notion of sections-in-a-page there's probably few (or none?) existing forms that would be affected by this. Basically, its just adding the ability to set the form-list appearance on a group irrespective of what it contains (which you could do manually in the XForms XML anyway).