[Bug]: `currentRow` doesn't work correctly when the table is filtered about appsmith HOT 6 OPEN

Sure, thanks!

from appsmith.

from appsmith.

Hii @simonfvr ,
Can I work on this ticket?

from appsmith.

Yesterday I experienced an issue that probably is also related with this one:

• There's a table with data coming from a SQL query.
• This table is filtered and one row is selected.
• The data in this table is reloaded after performing a write SQL query (insert, update, delete).
• After this, the selected row changes, pointing to the index in the raw data, not in the filtered data.

I'll leave a video showing it.

Take into account that this doesn't happen when the read query is re-executed, only happens when a write query is executed (and this write query doesn't have to be related with the table).

from appsmith.

Video explanation

1. In the column "Invoice Number" appears the currentIndex for each row.
2. The row with currentIndex = 1 is selected, and it's still selected after reloading the data.
3. The data is filtered, and now the currentIndex = 1 is the first in the filtered data, let's say currentFilteredIndex = 0.
4. After reloading the data, everything is correct.
5. After performing a write query (delete data in a different table) the data is reloaded using exactly the same method as in step 4.
6. Now, currentFilteredIndex = currentIndex = 1, selecting the wrong row.

from appsmith.

I've also had this issue, where a max value validation for a field within a table is dependent on another value in the same row, using Max value = currentRow.columnName, where columnName contains an integer. Filtering removes all validation, allowing any number to be input

from appsmith.