There are some issues with the DataTable checkbox behavior. If we select a row on one page (e.g., page 1) and then navigate to another page (e.g., page 2), we can’t uncheck that row anymore — not even using the global checkbox. To unselect it, we need to find the correct page and the correct row.
If an admin has 1,000,000 rows, they won’t be able to locate the selected row somewhere in the middle to uncheck it.
Another issue is that we can select a job, share the applications, and then delete that job. The other user who imports the application will see that a row is selected but won’t be able to uncheck it. Even worse, if the user doesn't have access to that job (due to authorization), the job still exists in the selection state, but they can’t see or uncheck it.
Users can end up spending a lot of time looking for a row they’ll never be able to see…
One possible solution could be for the global checkbox to indicate whether a row on the current page is selected.
There are some issues with the
DataTablecheckbox behavior. If we select a row on one page (e.g., page 1) and then navigate to another page (e.g., page 2), we can’t uncheck that row anymore — not even using the global checkbox. To unselect it, we need to find the correct page and the correct row.If an admin has 1,000,000 rows, they won’t be able to locate the selected row somewhere in the middle to uncheck it.
Another issue is that we can select a job, share the applications, and then delete that job. The other user who imports the application will see that a row is selected but won’t be able to uncheck it. Even worse, if the user doesn't have access to that job (due to authorization), the job still exists in the selection state, but they can’t see or uncheck it.
Users can end up spending a lot of time looking for a row they’ll never be able to see…
One possible solution could be for the global checkbox to indicate whether a row on the current page is selected.