Comment 11 for bug 1758381

This needs more work, as it breaks the grid if the user does one of the following:

- scan more items than the current row count limit
- reduces the row count limit to less than the number of items that have been scanned to date

There are at least two problems:

- The forceOrder processing makes $scope.item end up with as many rows as are in the pending list, not number of rows that are desired for display. The extra undefined objects in the array break the grid.
- Even if we try to fix the first problem, the fielder call doesn't guarantee that we'll get back all of the copies we're looking for, as it passes the ids of all of the copies in the pending list, but relies on the DB query's limit and offset clauses to return the desired copies; however, there's no guarantee that they'll match up.