When doing batch edits on a grid if you delete a row, the row is no longer visible in the grid but it is not actually deleted until users click the 'Save' button. This has led to some confusion for our users who delete the rows then navigate off the page w/o pressing save. They think they successfully deleted the rows but when they return to the grid the rows are still present. We have added logic when navigating away from the page that checks and prompts users if there are unsaved batch edit changes, but in case of deleted rows, when they look at the grid, there is no indication about the deleted rows so they are unaware that the rows were not actually deleted. We like the idea of not deleting the rows until the user presses the save button, but maybe the delete action should not remove the row from the grid and instead simply strike it out, or put a 'marked for deletion' flag or do something visual to keep the row on the grid but make it obvious that it has been marked for deletion. This way users will not be confused and will know that they must click the Save for the change to take effect.