So does the me.ui.getIndex() always return the correct row index while removing a record from the table?
We are seeing some erratic behavior when the table is paginated. The index returned is different from the actual row we are trying to delete.
Our code looks like this:
The UI getIndex() returns the index of the user interface. This will be in the order the UI’s are drawn. If the Table is Paginated, the rows may be drawn out of order as the user clicks the page buttons.
You may want to look at getRowForView() and getRecordIndex() on the Table JS documentation:
Calling view.getRow(me).getData() will return the data for that row which can be passed to getRecordIndex().
However, the Table does include a built-in Delete button configuration option.