IMO we should a allow a search within the facet view.
It should be a part of the control and implement for every facet.
This would be a mojor change I suspect and I do not know if it this is supported by the underlying API.

Is the 250 limit configurable or burned into code?

The plan to fix:

For any page that usese multiple columns (host to host, user to group, etc) we are going to do an <entity>-find instead of the batch command. So, from the users page, to list the users in the "ipausers" group it would be the JSON equivalent of "user-find --in-groups ipausers" We will also add a filter field at the top of the page. That way, if a group has more than 100 users, the web user can enter in filter criteria to cut down the list.

For associations that have only the primary key on them we will leave alone for now.

Removed the use of Bulk, as even with 250, there was a stack overflow issue. Instead, for group->user we will use a modified version of search. Multi-column facets elsewhere are reduced to a single column (hosts managed by and services->hosts, two facets lost there description columns.)

I made a quick stab at replacing the table with a search_widget, but there are two many differences between the search_facet and the association_facets that it basically breaks things. The amount of code needed to make them work together is significant.

Since the worst aspect of this is now mitigated, moving the remainder to the next release.

master: b01220c