Comment 3 for bug 1960674

Working with Christine to confirm this but, we came up with a database query that clarified the issue in our system.

SELECT ou.shortname, cr.label
FROM acq.lineitem li
JOIN acq.purchase_order po ON li.purchase_order = po.id
JOIN actor.org_unit ou ON po.ordering_agency = ou.id
LEFT JOIN acq.cancel_reason cr on li.cancel_reason = cr.id
ORDER BY li.id
LIMIT 100

Comparing the Lineitem ID is not 1 search sorted by the Lineitem ID with the query results, we saw 49 rows in the grid in the client. The grid was limited to 100 rows.

Our query results had 49 rows out of the 100 retrieved where the ordering agency matched the workstation location.

This result agrees with John's description:

"Essentially what seems to be happening is that the search is ignoring the working location and fetching everything in the system that matches the search terms. Then the part that displays the results is removing everything that doesn't match. It's not, however, updating row numbers."