Changing the limit on the number of items returned in a filter

Noticias externas — Thu, 17 Jan 2008 20:04:08 GMT

When not all records are shown in a filter, no message is displayed to the user, and the items will appear

re: Changing the limit on the number of items returned in a filter

Pete D — Thu, 17 Jan 2008 23:20:44 GMT

This has been bothering me since CTP 4 release. Thanks for the tip. Huge help!

re: Changing the limit on the number of items returned in a filter

tiwebber — Fri, 24 Oct 2008 19:00:19 GMT

We have about 4000 members in a hierarchy that we need to filter on with either a Tree or a Multi-select filter. I increased the default and tried it. It renders just fine with a list type filter but is very slow with tree or multi-select.

So we tried list type filters for all levels in the hiearchy but they cannot be related (cascading)!!! Aaargh. We upgraded to SP1 but still slow (>30 seconds). Again, list type filers are OK. Is the algorithm that renders tree and multi-select filters very broken?

filters "on demand" in SP2?

tomer.dgani — Tue, 24 Feb 2009 16:10:20 GMT

Is the way the filters load changed on SP2 already? Our filters loading time is much larger than the scorecard...

re: Changing the limit on the number of items returned in a filter

alysonp — Tue, 24 Feb 2009 21:22:33 GMT

List filters a simple HTML selection control. They will render quickly even with a large set of items.

Tree filters are more complex. The full selection set is sent to the browser along with hierarchy information and the tree is rendered by client-side JavaScript. This was improved for SP1 but this is still slow for large selection sets. This is the same for SP2.

Sorry.