Subreport not aligning inside report upon deployment
-
I have a report showing an overview of some data and for each row I have a subreport. When I run this locally on my machine all columns line up beautifully as shown below
However when this is deployed the report now looks as follows ...
All fields are matching sizes, Grow is turned off ... any ideas what else I can try
Thanks
-
Fiona,
I'm having the same problem. Everything's lined up in preview, but not in the Report Server website. I think it's a rendering issue, but I can't figure out how to resolve the problem.
I'll let you know if I find something out (this is my project for today), but if someone else knows the answer, please add to this thread.
-
Fiona,
Make sure your font sizes are also all the same. This is another issue that can cause line up problems between subreports and main reports.
Not that it helped me any. However, I did notice when I exported my report from the HTML renderer to PDF format, everything lined up precisely. So I think it's something in the HTML renderer that's causing the issue, not the report itself.
-
That's HTML for ya:)...You could spend years formatting that and HTML will kill it in no time flat...
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again? -
Tell me about it!
At least I'm not going to waste a day's worth of "making it purty" now that I know it wasn't my fault. @=)
-
Thank you.
All fonts were already the same. I finally managed to make the problem less noticeable by making the width of the subreport boy exactly match the width where I am placing the subreport in the main report - weird.
-
I'm glad you finally got it working.
Mis-Aligned Height settings can also mess you up. So if you haven't checked that already, you should.
-
I faced a similar problem, but mine involved a matrix item. I had textboxes resized unexpectedly (both vertically and horizontally) once deployed to a server. Here are my findings:
1. Unexpected horizontal resize: server Web renderer "overrides" "CanGrow"=False property based on "Padding*" values. I had a small fake inner row group textbox that contained a (color) value to achieve green bar effect (alternating row highlighting). Instead of setting its "Hidden" property to true and create a break in the highlight, I increased a "LeftPadding" property value enough to move the text out of textbox's visible area. That, needless to say, didn't work once moved the a server. The solution was to set "LeftPadding" property back to 0pt and, in turn, set "BackgroundColor" and "Color" propery to the same value to make the text, for all practical purposes, invisible.
2. Unexpected vertical resize: server Web renderer resized row height if any of the column values in that row contained a NULL value. Strange, huh? To fix the issue you can either handle NULL values on the dataset level or use a combination of iif() and isnothing() to handle NULL values within textbox itself.
Another side lesson I've learned from my endeavor: server Web renderer doesn't understand "Transparent" as a value for "Color" property, while BIDS and even server PDF renderers do.
-
Hi, I am having a similar problem and looking for help.
I have a subreport as a row in a table. The last column of the main and subtable's visibility property is true or false based on a parameter. The problem happens when the last column is hidden. The subreport formats how I would expect (staying in it's allocated space), but the column before the hidden column of the main report gets stretched out to fill the hidden columns space. Trying to demonstrate below. Column two is the last column before the hidden and left aligned. So the
col1 c o l 2
main 1 1
main 1 1
sub 2 2
Any help would be greatly appreciated.
Thanks!
Melissa
-
Melissa,
Are all the widths the same for each column and for the subreport "form"? What about the widths of the columns within the subreport? They should be just slightly smaller than the size of the subreport form so they don't spill over the boundaries.
-
Hi Brandie,
Thanks so much for your response.
I had everything set so that the columns of main and sub were exactly the same, so I made the sub .001in smaller, that didn't work. It looks like the sub expands to fill the main though when I made it smaller, but the columns do add up to less. What confuses me is that it's the main table that is growing, not the sub. I have changed all of the 'CanGrow' properties for the column and individual cells and that didn't do anything either. Anything else you can think of to try?
Thanks again,
Melissa
-
Try also turning off "Can Shrink" and making sure all the row sizes are the same. Then, check each individual cell to make sure all your changes are propagated correctly. I've noticed that sometimes a cell doesn't get changed even though a column or row does.
-
I think what's happening is your subreport placeholder remains the same width regardless of how your subreport renders. If your place holder is 3 columns wide in the main report, it's still going to be 3 columns wide even when the 3rd column is hidden in both the main and sub reports. The last unhidden main report column is stretching to fill the gap. Playing with Can shrink, Can grow won't help because they only impact height, not width.
Unfortunately, I can't think of a proven work around for it though.
Possibly reconfigure your original tables for both reports to just include the columns that show every time. Then create additional tables in both reports for the single column that may or may not show. Set those tables to hide/show based on your param.
[font="Comic Sans MS"]toolman[/font]
[font="Arial Narrow"]Numbers 6:24-26[/font] -
Thanks to you both!
I did play around with both CanGrow and CanShrink with no luck. Toolman, you did hit the problem right on. I'm going to try your suggestion and see what happens. I'll let you know. Thanks a bunch to both of you!!
Melissa
-
Well, after I got it there and thought it could be a solution, I'm now worrying that some of the fields in the main report may wrap at some point so it's probably not the best way to go either. They may just have to live with it. I appreciate both of your help!
Viewing 15 posts - 1 through 15 (of 28 total)
You must be logged in to reply to this topic. Login to reply