Forums

Sorting sorts the values stored in the RecordSet. If you use any editor which does not update the underlying field in the RecordSet, sorting will take the original value, not the one seen on the screen, which has not been updated. When using your own editor, do not update the HTML but use method updateCell or updateRow to refresh both, the HTML and the underlying field. If several cells are being edited, you may opt to update the RecordSet directly and then just refresh the screen just in one go, to reduce the number of updates.

When the updated value of a field would make the row appear in a different order, DataTable will not reposition the row because there are several possible ways of handling it and it is up to you.

The first option, some would argue is a bug, is to do nothing, leave the record unsorted. Others suggest moving the records around is too distracting to the user and, since it will necessary take some time, a waste. This is what DataTable does.

The second option is simply to mark the column as no longer sorted which, in fact, is the case. To do that simply set sortedBy to null:

myDataTable.set('sortedBy',null);

I believe this should be the proper behavior, it leaves the row where it was, wastes no time resorting and clearly states that at least one row is out of place.

Besides, when receiving a click on a header of a sortable column, DataTable checks if it is already sorted and if so, it will simply reverses the order of the rows, which is much faster than resorting. The problem is that the misplaced row will remain in the same place to their neighbors, just reversed, and will not be re-sorted. Thus, setting sortedBy to null should be the correct behavior so that a new click on a header cell will really sort the records.

The final option is to resort the whole DataTable, which you are free to do after the new value of the field is saved. To do that, read and save the value of the sortedBy attribute somewhere, set sortedBy to null and call sortColumn using the values read from sortedBy.

sortedBy has two properties, the key of the sorted column and the direction. DataTable assumes only one column is sorted at any one time. If you set it to null or set its individual members to null, no column will be marked as sorted. Basically, what it does is to set the visual clues and servers as a status indicator to tell which column is sorted. Setting it will not actually sort anything, it will only make the user and the datatable that it is sorted by one specific column.