The Provider field limits its search to 50 before any filter by permissions are taken into account

[Dale Rigney]

Tested on evergreen 2.7

When you try to create an Invoice or Purchase order the provider field responds to the first character entered and displays a list of providers that start with that character. This list of providers is sorted alphanumerically, then limited to 50 before any other criteria such as work station and permission level are taken into account. This can result in a blank list when a consortium has over 51 providers that start with the same character and the 51st provider is the only provider that should display for the staff member/workstation. The list should apply the permission criteria and then apply the limit.

Here is snippet from the logs:
open-ils.pcrud.search.acqpro "8af1fd704726f45012505b011f5b52bb", {"active":"t","code":{"ilike":"r%"}}, {"order_by":{"acqpro":"code ASC"},"limit":50}

[Tiffany Little (tslittle)]

Noting that this is still an issue in 3.4.1. See now-duped bug 1895551.

[Britta Dorsey (bdorsey-isl)]

Seeing this issue (or something very similar) in 3.11.2, but it's not consistent.

We have a library that has 20 providers that all start with their shortname (MRNRV). When they use Create Invoice, the Provider list only shows the same seven providers. When we attempt to enter a provider that does not appear, we receive an invalid entry.

Another library has 16 providers that start with JFFCO and they are all visible under Providers when using Create Invoice.

[Carol Witt (carolwitt)]

As I mentioned I'd do at the August AIG meeting, I tested this on our development server after 3.13.3 was installed this week.

Using our test ACQ Administrator library account, Evergreen displays all of that library's providers and none from other libraries when using Create Invoice and entering the provider's first character, even when there are over fifty. Can anyone else confirm that?

However, it is displaying both active and inactive providers. I'd expect only active providers to be displayed. Is that new to 3.13.x?