I've been looking at this on a test VM and would like to get some of our people to look at it on a system with production data. In the meantime, however, I noticed a couple of issues.
- With this branch loaded (both with and without Mike's commit), I notice that if I change the pickup library for this grid, it doesn't automatically update to show holds for the new library. See the screencast of a test that was performed on a test VM that just had Cesar's portion of the work - https://drive.google.com/file/d/17oXj9ZX4GnMfCHDHzvlc9nyHj_CWBIe4/view
- On the test VM that has the latest branch with Mike's commit, I noticed that when I first retrieve the record holds interface, it lists all of the holds on the record, no matter what my row count is set at. I knew the most recent change would retrieve the data for all holds on the record, but I didn't expect it to display all at one time.
I've been looking at this on a test VM and would like to get some of our people to look at it on a system with production data. In the meantime, however, I noticed a couple of issues.
- With this branch loaded (both with and without Mike's commit), I notice that if I change the pickup library for this grid, it doesn't automatically update to show holds for the new library. See the screencast of a test that was performed on a test VM that just had Cesar's portion of the work - https:/ /drive. google. com/file/ d/17oXj9ZX4GnMf CHDHzvlc9nyHj_ CWBIe4/ view
- On the test VM that has the latest branch with Mike's commit, I noticed that when I first retrieve the record holds interface, it lists all of the holds on the record, no matter what my row count is set at. I knew the most recent change would retrieve the data for all holds on the record, but I didn't expect it to display all at one time.