Dimitri,
Thanks for the response. I'm on SQL Server 2008 R2 SP2 and SharePoint 2010 SP2.
I'm now 99.99% sure that this is a memory/limits problem within either PerformancePoint or SharePoint.
I can now get the report in the dashboard to display IF I only select about half of the items in the new filter -- and it does not matter which half I select. At a certain point, if the number of filter items gets too high, the report appears to refresh
(very quick, no green circle) but the numbers in the report do not actually change. And if you go off of the dashboard page and go back in, the report does not render. Similarly if you select all of the items in the filter and hit apply, the SSRS
report does not render in the PerformancePoint dashboard.
I have now tested this using a PerformancePoint filter going against a SQL Server table and a PerformancePoint filter using a SQL Server Analysis Services dimension -- same result in either case. The filters work if: 1) make it a single value
selection (list tree for example) or 2) make it a multi value selection but when you are actually in the dashboard just select a few number of items. The filters do not work if: you hit select all and pick all the items -- the report either quickly
renders (but does not actually change based on what is selected) and if you click off the page and go back on, it does not render at all. This proves in my judgment that it is a PerformancePoint / SharePoint / IIS issue. My next step is to
open a support ticket.
I have 8 pages in the dashboard, 3 or 4 filters on each page, and one of the filters is large -- over 1,000 items to pick from. I'll assert that the combination of pages X filters X number of items in the filters eventually breaks it.
On a separate SSRS thread I did run in to a similar limit outside of a PerformancePoint dashboard involving an SSRS report running in integrated mode, fixed it by following the thread's answer and editing the
SharePoint web.config file. It would be great if there was a similar web.config entry to get around what seems to be a similar memory/limit problem in PerformancePoint.
--Bob
-
Marked as answer by
Alisa TangMicrosoft contingent staff, Moderator
Thursday, December 12, 2013 9:28 AM
-
Edited by
Bob Harford
Friday, December 20, 2013 3:23 AM