Adding Table to Report Slows To Point Report Can't Be Run

[Jessica Davis]

In my report, if I just place all the fields I need on the report in the body, the report runs fine.  If I put them in a table using the table wizard (because I want the fields laid out where they have lines between the rows and columns), the report will not run.  It just keeps thinking and thinking.  Is there a reason putting it in a table layout will slow it down as compared to just placing the fields on the report?

[Peter]

Hi Jessica Davis,

From the information you have provided, the reason for the delay is not obvious. Such slowdown can occur in a Table scenario when the same datasource is used for both the report and the Table item, and where the data is used without filtering the records. In such scenario the report will show NxN rows of data.

In order to be more concrete we need a sample project which demonstrates the problem. Please, send us a simple project (with dummy data) through the support system thus we can investigate the issue locally.

Best wishes,
Peter
the Telerik team

[Jessica Davis]

It will take me a little while to get a sample project together, but something that you said makes me think I am adding the table to the report incorrectly.  You said "A slowdown can occur in a Table scenario when the same datasource is used for both the report and the Table item".  My report has the table within the Detail Section of the report with two grouping sections.  So say for instance I have one datasource that includes the fields: Player's Team Name, Player's Position, Player's Name, Player's Stats.  I have the report's datasource set to that list.  And I have the report with two grouping fields:  Team Name and then Position.  Then inside the detail section, I have a table item that holds the Player's Name and Stats.  Is there a demo project that shows how you set up the datasource of the table item so that it points to the same datasource as the report and is only showing the records that are for that grouping.

[Peter]

Hello Jessica Davis,

Its really hard to give a performance considerations without a sample runnable report to test locally. However we have a few suggestions to try:

• We recommend to avoid using PageCount because it requires an additional pass to count all pages before the actual report rendering (i.e. it renders the report in the memory in order to count all pages).
• Another option is to reconsider the size of the data you need to display at once (by using DataSource parameters).
• Create a Table like layout in the Detail section as explained in Dynamic Layout (Dock and Anchor) help article. This is working for simple tables and in your case will improve the performance.

Reviewing the Performance Considerations KB article for other optimizations is highly recommended.

For further assistance we will appreciate if you send us a sample runnable project through the support system thus we can test its performance locally.

Kind regards,
Peter
the Telerik team