Im using RDLC for VS 2010 and exporting the graph to a word document gives one extra blank page (its not showing in PDF though). All of the dimensions in Report, Chart and Body are set 11x8.5 with no margins. I just wonder what could be causing the blank page in Word.
I was having the exact same problem and managed to solve it by adjusting the layout of my report.
Basically I moved all of my rectangles/tables etc to sit tightly next to each other, eliminating any white space where possible and also resized the report to be as small as possible, i.e. sit tightly against its contents.
It might also be worth enabling the report option to 'ConsumeContainerWhitespace'.
I suspect Word uses its own pagination logic, which is why you see a difference between pdf and doc. So it may just be the case that your report is over-running very slightly into the next page and saving a little space on the report may prevent this.
I realise this is not a precise answer, but I hope it helps nonetheless.
Related
I have designed a report in SSRS 2008 with three tablix that display data from different SP. When I designed the report and then previewed it, the report looked perfect. I deployed the report to our report server and viewed it. The report displays the last table with several columns that are either too large or too small. When I then export the report to PDF after I run it on the report server then the report appears the way that I designed it.
Does anyone have an idea what could cause the report to display wrong when it is run but correctly when it is exported to a PDF?
This is pretty common. I struggle with this same issue.
Edit: double check CanGrow and CanShrink on both the cells and tablix. Maybe your is interpreted differently and therefore is larger in web view?
Firstly, you're just going to have to play with your settings until it looks like in all output formats. However, here are a few tips to help:
Don't use rectangles, ever. Everything should be in a tablix cell. You have much finer control and it is less likely to blow up in PDF and web viewer.
Stay away from your margins. I try to keep at least .25"
Watch your padding. If you have top and bottom padding of 4, and your text is 10, but your cell only allows 16, then you're going to have a bad time
Use Ctrl + Mouse Scroll to zoom in and check formatting. This won't show a lot of errors, but it's something to check.
Even though your top cell and top line of the tablix should be identical, they aren't always. I can't tell you why. However, don't put a BorderStyle on both. Sometimes the border doubles up and looks wider in some of the output formats.
Always check all output formats prior to handing your project to QA. If is very common for report formatting to blow up once deployed. I have to double check Portrait vs. Landscape formatting and my borders. I miss that sometimes.
Sometimes font sizes can be interpreted differently. There can be very slight differences that can change the sizes of your cells.
I hope this helps.
I have a bar chart with horizontal bars. I used this article to setup the dynamic height property:
http://blogs.msdn.com/b/robertbruckner/archive/2008/10/27/charts-with-dynamic-size-based-on-categories-or-data.aspx
Everything looks fine in the viewer, but as soon as you go to print layout, pdf, et.al there is about 50% more blank space below the chart.
I've created a sample report (using AdventureWorks DB) to show what is happening. I placed 3 charts with blue backgrounds, each inside its own rectangle with gray backgrounds. The first chart has an expression in the DynamicHeight property, the second chart has a hard coded value in the DynamicHeight property of 8.5in, and the third chart has a blank DynamicHeight and a 8.5in in the normal Height property. I have it return 15 items to place in the chart.
They all look fine in the viewer like I said before, but go to Print Layout and the first and second charts take up twice the space with half of it being blank below the report.
I tried to post the .rdl code, but its too much for the size limit.
I have an open ticket to Microsoft that has been escalated.
We've filed the necessary request to get collaboration from our development team so we should be getting a response regarding this functionality sometime in the next couple days. I'll let you know what they say.
Development has later confirmed it was definitely a bug, now are trying to decide if it is worth it to add to the next cumulative update or wait until SSRS 2010.
The work around until this is fixed, is to place the chart control into a table/tablix.
I added an empty table, deleted the details row and the two extra columns, and added my chart that was giving me problems. Everything appears to re-size correctly now.
try setting up the interactive size, margin and page size. im not sure if it will work but you can try. page size - margin = interactive size. do not exceed from your page size when giving value to your interactive size and margin, this also can cause white spaces in print layout.
hope it helps.
best regards,
cathy
I would like to build a report that starts at the bottom of a page and grows upwards instead of a report that starts at the top of the page and grows downwards. How could I do this?
--Edit--
For clarification, below is an image depicting the way I need to construct the report.
Basically, I'm looking for a way to have the whitespace at the top of the page and the data at the bottom of the page, instead of the more traditional look of data at the top of the page and whitespace at the bottom of the page.
Without knowing much about what the request is, I don't believe there is a way for the report to run from the bottom up, but you could possibly do a couple things to fake the system out.
For example you can do something like in the following link to put your summaries in the header:
Crystal Reports: global variable running total not displaying in header
Then you can play with the sorting of the details if you need the rows to go in decending order.
Hope this helps.
[EDIT] I see you updated your question so I'll add an update to my answer.
One more thing you can try out is to play around with the Print at the Bottom of the Page and Keep Together properties of the sections. I haven't tried this, but one thing you may be able to do is put the section at the bottom of the page and perhaps find a way to have the section grow from there. You will have an issue if the page goes to another page and though it seems possible in my head that the section could grow while being placed at the bottom of the page I haven't tried it so it might not work. I am just throwing it out there for one more thing you can try. Hope this helps.
You could try:
Create an empty report with your headers and related text
Put a subreport displaying your data in the report footer and set the sort order for the subreport query to descending.
In the report footer properties, select Print at bottom of page
I tried it with some sample data and it works, but I'm not sure what will happen if your data goes to two pages.
I'm using JasperReports to generate a word (docx) document but I have a problem when I want to try to print the doc. The exporter messes up the margins of the page. Does anyone know how to prevent that from happening.
I know how to set the margin in iReport, but it just makes the data generate further from the page borders, but the margins in word which can be adjusted at the top of the page is laying right at the edge.
Has anyone had this problem?
Are you able to specify the page size? Its possible that using this in combination with the margin settings will help the export problem.
If you are not too heavily invested in your Jasper solution, Docmosis and JODReports let you layout the document visually using Word or Writer then render the report in various formats. This may save you time in the long run, but all reporting systems have quirks. Hope you find a solution, especially when your output is not PDF.
I'm seeing basically the same issue described here
I have a table that starts in the middle of the first page, and, depending on the size of the table, it should wrap onto the next page. This behaves fine when using the viewer, but when exporting to a pdf or tif image, things are displayed differently. Instead of starting on the first page and wrapping onto the second, it moves the entire table to start on the second page, leaving lots of ugly white-space on the first page. I've made sure that KeepTogether is false on the table, and there is no header/footer on the page (so it can't extend beyond the page's width).
Has anyone seen this problem, or know of a solution/troubleshooting steps?
Thanks!
The problem was fixed by re-creating the report(s) in question using the Business Intelligence Development Studio 2008 (instead of 2005). Don't know what was different in the re-created report, but it works properly now.