Columns are alphabetized by header name when a secondary instance is built. This hasn't been noticeable since secondary instances haven't been exposed anywhere without each value being pulled out explicitly. The new map appearance on select_ones shows additional properties in order from the XForm and it would be ideal for that order to reflect user intent.
Steps to reproduce the problem
Convert a form with a select that becomes a secondary instance (e.g. this one). Notice that in the XForm, node names are ordered alphabetically.
Software and hardware versions
pyxform v1.9.0 and prior
Problem description
Columns are alphabetized by header name when a secondary instance is built. This hasn't been noticeable since secondary instances haven't been exposed anywhere without each value being pulled out explicitly. The new
mapappearance onselect_ones shows additional properties in order from the XForm and it would be ideal for that order to reflect user intent.Steps to reproduce the problem
Convert a form with a select that becomes a secondary instance (e.g. this one). Notice that in the XForm, node names are ordered alphabetically.
Expected behavior
The order of columns is preserved.
Other information
Tangentially related to https://github.com/XLSForm/pyxform/issues/590