Multi-Column report generating only one column

[Ezequiel]

I've followed the steps on this link http://www.telerik.com/help/reporting/advanced-creating-multi-column-reports.html
I tried in VS2010 and Telerik Report Designer.

But I keep getting only one column report.

I've also tried with a simple report, just listing some codes and I've got the same issue.

Attached all the screenshots of design and preview.

Thanks,
Ezequiel

[Steve]

Hi Ezequiel,

This is expected when you're viewing the report in Interactive mode i.e. per the documentation article you've referenced: "Multi-column report would be rendered as single-column when the report viewer is in Interactive view."

You should switch the report in Print Preview mode in order to render the report as multi-column. For your convenience I've attached your screenshots with instructions how to change the ViewMode.

Regards,
Steve
the Telerik team

[Bryan]

Did this work for you?  I was having exactly the same problem and switching to Print Preview mode just gave me 24 pages of the same SINGLE COLUMN presentation that NON-Print Preview mode was displaying.  It had NO EFFECT on the generated report.

Multi-column reporting does not seem to honor the "Column Count" setting on the PageSettings.

[Katia]

Hello Bryan,

Most likely the width of the report is larger that the width of the column - check the note in How to: Create a Multi-Column Report help article.
Test reducing the width of the Detail section or the report and page left/right margins defined in report's PageSettings. 

If the issue persists you can attach the problematic report in a support ticket so we can review it locally.


Regards,
Katia
Telerik by Progress

[Mark]

We are having the same issue.  First, the report layout in which we are trying to do this with, is inherited from a report class that has a Report Header, Report Footer and Page Header bands only, on Letter size page (which is inherited from Telerik.Reporting.Report. All those bands are 8" wide.  On the Inherited report layout, all we have is the Detail band with PageSettings.ColumnCount = 3, PageSettings.ColumnSpacing = 0.03in and any group by bands that are needed.  However, every time we run the report, only one column shows up.  If I re-inherit against with Telerik.Reporting.Report everything works fine, except we don't have our standard Report & Page Headers & Footers.  I have looked at the Parent class that seems to be the issue, but there isn't anything set in that class that would be changing the column count back to 1. In fact, there is nothing in the constructor of the Parent class except "InitializeComponent()".   Any help would be greatly appreciated.

 

Thanks-

[Todor]

Hello Mark,

The issue may be related to the width required by the content of the Report Header and Footer sections.
The Report Header will be fit at the beginning of the first column of the multi-column detail section, whereas the Report Footer will be placed at the bottom of the last rendered column, i.e. they will *not* be rendered across the entire page width. Therefore, if in one of these sections there is content (TextBoxes or other report items) with location surpassing the width of the detail column, this will force horizontal page break.
You may test fitting the content of the Report Header/Footer of the base report in a smaller area (taking into account detail column width of the inheriting reports).

I have attached a sample project mimicking the described approach that works correctly on our side.
If the problem persists you may open a Support ticket and attached the project for local investigation.

Regards,
Todor
Progress Telerik

[Mark]

This is really close. The problem is that the Report Header needs to be the width of the full page, not the column.  Our Report Header shows our user what filter criteria they picked for that report.  On a 3 column report, it would look really bad squeezed into the first column. Now, if there was a way to create two page headers, hiding one that was not needed after the first page, so I could have a Main Page Header, a Secondary Page header, then we could get this to work.   But, from what I am seeing, is that a Page Header can only exist once in a report.   I need to find another solution.  Was thinking sub-report, but I have not done them before.  So, I am going to look that way.  If you have any other ideas, please shoot them my way. I appreciate the help.

 

Thanks

[Todor]

Hi Mark,

You can test to add a Panel at the bottom of the PageHeader, where to place the content that is currently in the ReportHeader. The Panel can be made Visible with Conditional Formatting or Bindings only on the first page.

SubReport item cannot be placed in a PageHeader as it is a Data item, hence it will also be squeezed in a single column.

Regards,
Todor
Progress Telerik

[Mark]

[quote]Todor said:Hi Mark,

You can test to add a Panel at the bottom of the PageHeader, where to place the content that is currently in the ReportHeader. The Panel can be made Visible with Conditional Formatting or Bindings only on the first page.

SubReport item cannot be placed in a PageHeader as it is a Data item, hence it will also be squeezed in a single column.

Regards,
Todor
Progress Telerik

[/quote]

While I can use a Panel, and the Panel does GROW, but only grows as big as the PageHeader's height.  This poses another problem, while the Panel will GROW as needed, the PageHeader doesn't.  The PageHeader is a FIXED height. It can't grow or shrink based on content of what's in the header.  These issues are not just related to multi-column reports, this is the same issue for a standard report, but can be overcome by using the ReportHeader, however, since the ReportHeader is designed like a Group, on a multi-column report, we can't use the ReportHeader, becuase the width will be too small to display the information we need to display.  Note, the items that we need to display are the filter criteria for the report and the sort order of that data, which only needs to be present on the first page.  Since we cannot know what the user is going to pick for filter criteria, the field has to grow as necessary, therefor the band it is in, needs to grow as necessary, but for only page 1.  Again, this is really only an issue for Multi-Column reports, becuase the ReportHeader is only ever the size of the column.