We touched on the issue of reordering data yesterday in our discussion and I think I have a simple solution, at least for datasets where we can control how data is entered (i.e., Data Entry application, Survey123 forms, etc). Basically, I plan to create a RecordID in Survey123 (starting at 1 in the subform for every Activity) so that field can be used to track/sort the order in which records are entered into the Survey123 sub-form. I will then use this value (in place of the ROW_NUMBER operation) to populate RowID in the dataset _Detail when the data is imported into the back-end using a script.
In this way, the data will always be sorted by order of entry; so then, if we sort on d.RowId in the view, the data should be displayed in order of entry in CDMS. Right?
As such, I am requesting to include this clause (ORDER BY ActivityId, d.RowId) in the view expression and am hoping this can be included when views are created/recreated as a result of changes from the dataset creator feature.
Joe –
We touched on the issue of reordering data yesterday in our discussion and I think I have a simple solution, at least for datasets where we can control how data is entered (i.e., Data Entry application, Survey123 forms, etc). Basically, I plan to create a RecordID in Survey123 (starting at 1 in the subform for every Activity) so that field can be used to track/sort the order in which records are entered into the Survey123 sub-form. I will then use this value (in place of the ROW_NUMBER operation) to populate RowID in the dataset _Detail when the data is imported into the back-end using a script.
In this way, the data will always be sorted by order of entry; so then, if we sort on d.RowId in the view, the data should be displayed in order of entry in CDMS. Right?
As such, I am requesting to include this clause (ORDER BY ActivityId, d.RowId) in the view expression and am hoping this can be included when views are created/recreated as a result of changes from the dataset creator feature.