Making the now internally stored child record sorting order externally accessible
r
robp
The user can now change the order of child records within a repeatable by drag-and-drop. The system stores this new sorting order only internally, so it cannot be retrieved from the database. It would be great to make this internally stored sorting order accesible as a new field in the data tables.
Katie Briggs
open
This is not the bug that I thought it was, so re-opening.
Katie Briggs
in progress
There is currently a bug on Android where you can reorder repeatable sections but it doesn't save the new order. This will be fixed soon. Is this the scenario that you are referring to?
r
robp
Katie Briggs, no it's not that. I was in contact with support, Ashwin and Christian knows about this issue.
Christian said: "The sorting order of repeatable sections isn’t stored as a visible field in the database. Instead, it’s managed internally by the system using the order in which the repeatable records are created. This ordering is preserved on the backend but isn’t exposed as a standard field unless explicitly tracked."
What I would like to see is that this internally stored sorting order (after a drag-and-drop edit) will be accessible as a field in the database.
Katie Briggs
robp: Thank you for the clarification!