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

When not all records are shown in a filter, no message is displayed to the user, and the items will appear to be "cut off". In the example, below I added all the members from a hierarchy (about 1500 items). You can see that it's only displaying items through "F", rather than all the items. If you were to click all the plus signs and count the items, (which I don't recommend), you'd notice there were exactly 500 items in the tree.

clip_image002

There is a limit - it's 500 by default. If you need to change this limit, you can add a line to the 3 web.config files:
    <add key="Bpm.TreeViewControlMaxNumRecordsToRender" value="600" />
However, we aren't really recommending adjusting this setting too much larger, as there may be performance problems with the loading of the page. We are looking to address this after v1 by redesigning the way our filters load, to make it more "on-demand" than it is today. So, for now we recommend designing your dashboard so as to keep your filter tree items relatively small.
If what is being selected in the parameter could be implemented as security, that would be another approach, to bypass or limit the size of the parameter altogether

Note: as with any web.config file change, you have to make it in 3 places - by default:

SharePoint Site
C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config
Preview Site
C:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\PPSMonitoring_1\Preview
Web Service
C:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\PPSMonitoring_1\WebService

Keep in mind that the above paths are examples; the actual paths may vary by SharePoint site & Monitoring instance ("PPSMonitoring_1") name.

Greg Bernhardt (gregbern@microsoft.com)

Published 17 January 08 05:00 by alysonp

Comments

# Noticias externas said on January 17, 2008 12:04 PM:

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

# Pete D said on January 17, 2008 3:20 PM:

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

# tiwebber said on October 24, 2008 12:00 PM:

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?

# tomer.dgani said on February 24, 2009 8:10 AM:

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

# alysonp said on February 24, 2009 1:22 PM:

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.

Anonymous comments are disabled

Search

This Blog

Microsoft BI Sites

Syndication

Page view tracker