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.


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
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 (

Comments (9)

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

  2. Pete D says:

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

  3. tiwebber says:

    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?

  4. tomer.dgani says:

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

  5. MSDN Archive says:

    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.


  6. sagie says:

    is there a way to bypass this by creating a filter that "listens" to another filter and shows only the children of what is selected.

    for example – if we have a hierarchy of country,districts,cities and streets.

    we can store in a single filter the country, district and cities but not the streets.

    can we create another filter that returns the children of the city (or district) select in the first filter?

  7. Eric Monas says:

    On version 3 now of PPS .. this still doesnt seem to be addressed. Is the performance at least increased ?

  8. Brian says:

    A little off topic but…

    Is there anyway to 'deselect all,' by chance?

  9. Alvine Herry says:

    Thank you for this extremely brilliant blog! We really appreciate your blog post.  Thanks for sharing this type of blog. Your writing style is very good.

    <a href="">air filters delivered</a>