I understand that I can never exceed the width of a report body, but I have more report items than a (Design View) page can hold and I don't know what to do.
To clarify, what is currently on the Design View page correctly becomes a longer display view, and becomes multiple printed pages. Just what I want.
The problem is that I've run out of vertical design canvas and I don't know how to fix that.
Now that we've identified the PBI-Desktop tag was erroneous, the problem domain is SSRS Report Builder/PBI Paginated Report Builder doesn't give you enough space to craft your report.
The right but wrong answer is to go into the Property menu of the Body and there you can change the Size of the report.
Here you can see me manually increasing the size of the report body but it's easier/more precise to work with the property window.
Why it's the wrong answer -> You're designing a paginated report - one designed to be pica perfect on your page. Now we're stuffing a 21.875 inch body of a report into an 8x11 page piece of paper. Viewing of it might be ok but when someone clicks print, what happens? Is it going to squish all of that into a single page? Will Page 1 of the report really span N pages? It's been too long since I've worked with SSRS to that level of precision and I really don't remember but do test early if printing is a crucial aspect of the report delivery.
Outdated PBI Desktop/Service answer in case someone else needs it
In Power BI Desktop, click in the background and under Visualizations go to the Format tab. Change the default page size to custom and I could create a 99999 pixel tall report but I doubt that's advisable
I have a report in Access that is from a checklist form for closing down projects. When the report is loaded, depending on the project type, certain labels and their combo boxes are marked as not visible. This is done using VBA and the visible property of each control. I have noticed that the report still includes these combo boxes and labels as blank white space. Is there a way to remove the white space?
I have set the detail and the overall report to can grow and can shrink. I am thinking about possibly using sub-reports to do this but I am unsure if it will work.
Edit: Another solution I am thinking about is building several different reports and using an if statement for the project type to determine which report to open but this feels excessive to me. This solution would report in at least 5 separate reports.
Controls don't take space in Microsoft Access. They are positioned at a certain, predefined position, on a report of predefined size. There are little dynamic things about it (yes, nicomp is right, the CanGrow property makes it a tiny bit dynamic).
If you really want, you can move up all controls below a control you're hiding by the height of the control you're hiding, assuming controls take up the full width of the page. To do that, you can use something like the snippet below (iterate through all other controls):
If MyHiddenControl.Top < MyOtherControl.Top Then
MyOtherControl.Move MyOtherControl.Left, MyOtherControl.Top - MyHiddenControl.Height
End If
And if you want to do it properly, add margins for controls and resize the report detail section too.
If controls don't take up the full width, it's considerably more difficult to dynamically organize your report.
I'm implementing a Gantt Chart in SSRS via the Horizontal Range Chart and notes I found here (http://pnarayanaswamy.blogspot.com/2010/09/range-bar-chart-gantt-chart-using-ssrs.html). I've successfully implemented the Gantt Chart plus some additions so it can span multiple pages (DynamicHeight based on # of rows). My problem is that no matter what I do, I end up with double blank pages at the end of the report. I.e. if my Gantt chart is 10 pages, I'll have 10 blank pages at the end.
Any ideas? It's most definitely not a margin issue, as I've removed everything from the report except the Gantt Chart and then made it 1" wide and still get the double-pages issue. It is always exactly double the # of pages it should be. I've turned on all borders to see if there are any dynamically expanding boxes that might cause this but nothing is showing up. I'm open to ideas from anyone who has experienced anything similar. This is probably rare, though, as charts don't typically span multiple pages.
Thanks for your help.
Rocky
Even though you've explored a lot of the options, this still sound like a width issue. certainly a width issue: have you checked the width of the "Body" (That's the name that will show in the Properties pane.) You can find this by clicking on a blank part of the report, the background, and then use the properties pane to alter the width (The Body Properties dialog doesn't have options to change this.) Another way of changing these is by dragging the border of the page around in the designer.
Make sure that the width of the Body is less than your page width minus margins. Those, as it sounds like you know, are set in Report menu -> Report Properties.
I have a report created in SSRS 2008 that I call from and display in an asp page using the ReportViewer Control. In the ReportViewer my report has an extra/blank page at the end, but when I export it to PDF my report is perfect!. Nothing gets off the page, margins and size are all fine, under 10.0 in for a landscape report. Any idea what could be causing this?
Short Answer: Try shrinking the vertical size of the Body so there is no whitespace below the last page item.
Long Answer: I had the opposite problem when using reportviewer to render a 1-page form letter. Reportviewer rendered it correctly (one page) in the browser, but the exported PDF added a blank page 2. The Body size in my .rdlc file was exactly 8.5 x 11 in. so I could see the margins. Shrinking the vertical size of the Body to remove the whitespace below the last item (9.8" in my case) fixed the problem. (The exported PDF still has a page size of 8.5x11.)
(Thanks jimconstable. I don't yet have the "reputation" to vote for answers.)
Is the report surface larger than the page? That will cause an extra page that might not be there in a pdf.
This is usually caused because some of your page items... text boxes, rectangles, lines, tables... fall outside of the margins. I usually work on rather complex reports and what I have to do is put boarders (with different colors) on each thing that has an edge near the right hand of the page.... then when you preview, you can tell by the colors which thing is overflowing. Then you can re-size the objects or the margins until nothing overflows and the extra page is gone.
This actually happens a lot with sub-reports. They can push over textboxes, rectangles, lines... anything... that are placed to the right of them.
This can be an incredibly frustrating problem but I highly suggest adding colored borders to your report objects until you find what is spilling over. Sometimes - it can even be the canGrow property or it can be just white space left below your lowest report object so be sure to drag the bottom of the report body almost all the way up to the lowest object on your report (sometimes if the report body touches the lowest item that item's content can be cut off though, I always leave a little space, about the height of one of these letter's I am typing)
I've been having a similar problem (though there was also a blank page in the exported .pdf for me), which I eventually solved by doing the following:
Opened up the .rdl file in my text editor of choice
Searched for <Width> / <xxxWidth> tags, and reduced all the values contained between these tags to be less than the value minus the width of the margins on each side.
For me, the problem width belonged to the top level <Report> element, and changing it didn't affect the appearance of the report.
Of course, the next thing to try would be doing the same with <Height> tags.
There is a confusion there on the page design. Developers would think the report being designed is WYSIWYG, but actually it's NOT!! Microsoft reportviewer will take your designed page as the content!! and append the margins defined on the outside of your page, and turn out that your page can never fit in to one page!!
So, when you design a new report, focus on the content area, the client area, including your headers and footers, and allow margins to be appended on your outer border.
I had the same problem with a very simple report. My solution was in the Report Properties\Margins, set all the margins (left, top, right, bottom) to zero. That shrinks the report width and height. Apparently the margins are outside of the page size, usually (8.5 x 11 in).
I hope this solve the problem.
I also got the blank page at the end of report, but it disappeared in PDF. And I found that, if we uncheck the option "Add page break after", the blank page will not appear in SSRS. But When we export to PDF, there are no page break in PDF.
I've found that removing the Column Group for a detail report solved the problem. Nothing else worked. I made sure the Body fit within the Page size, made sure there was nothing extending into a margin in the Header or Footer. I didn't need column grouping and the output was the same without it. It seems to be necessary when using the Report Designer but isn't necessarily needed for the resulting report.
You have to check that the width of the bofy in the "Body properties" tab is not higher that the width of the page in the "Report properties" tab, otherwise the last part of the body renders in another page. A4 size is 21cm x 29,7cm and make sure to consider the margins to calculate the max body size.
I have an SSRS 2005 report, the report has two groups and one nested table inside of a group, the report is displayed correctly in VS as two pages, but when trying to export it to PDF I get 17 pages and the only correct pages I get are at the end of the PDF file.
Check the grid vs the Page Size.
If you Page Size is set to 8.5" x 11 and you have 1" margins and your Grid (The "white" part of the report) goes beyond the margins, you will get overflow on to other pages.
If you look at the picture below, you can see the grid goes just beyond the 7" mark. My interactive snf Page Sizes are set to 8.5 x 11. This exports fine. A good way to check is to switch to "Print Layout" mode. You can do this by clicking on the little icon that looks like a white piece of paper on a green background just to the right of the Printer Icon. When you view it this way, you get a pretty good idea of how it will be exported.
I have run into this problem before, generally a Table or Rectangle control will inadvertently push to the edge of the Grid and in turn increase the size of the Grid beyond your paper size and margins.
Yes, but it's been a (long) while since I worked with SSRS. I remember having adjusted rsreportserver.config
This link should help:
Customizing rendering extensions
The link is just the result of quick googling. Didn't read it through.
I had to adjust values for i.e. border width and so on, which are by default somehow a mess. And if that doesn't help, you have to adjust your report.