No, but I think I worked that particular issue out, I was slightly misunderstanding the original issue.
The dev needed an easy way to maintain 20 rows upon save, while the whole table is editable, but a row is not guaranteed to have data in it. Upon save, the only rows that were persisted were the rows with data in them. Using minRows and maxRows I am able to persist 20 rows, but now on the save call, the row with added data jumps up to the top. Persisting the index of the edited row is now my sticking point.