CMS dropdown filter autogenerate options is based on limited set of results

[camfindlay]

When working in the CMS and adding a Dropdown Filter based on a column in a dataset, for example "City", the list of auto populated options is only based on the first 100 rows of the data. This has the effect of excluding some legit values from the dropdown filter. From my understanding a return of 100 rows is a CKAN datastore api default unless the query specify a larger limit=. I don't this this should be infinitely big (may run into performance problems) but it would be good if this was a configurable option in the filter or event something that a dev could set in the SilverStripe config yaml. In many cases, 100 rows will be enough, for other cases you'll need much more. There are more than 100 Cities in NZ ;) Smallest effort might just be to set this to 1000.

[ScopeyNZ]

I think the long term fix for this issue would be to have a configurable maximum and some sort of validation state on the input for "too many options". It should then force you to input options manually.