ssrs - [rsReportItemOutsideContainer] extends beyond the bottom edge of its container - reporting-services

When I am building my SSRS report it is throwing below warning.
[rsReportItemOutsideContainer] extends beyond the bottom edge of its container.
Is there a way I can suppress this warning or get rid of this by other way around ?

Related

MS Access Reports - How to avoid last row of details being stretched vertically at bottom of page?

I am creating an access report with sub-reports with data in the details section. There are too many rows of data to fit on the page when printing the report, so a page break happens automatically. (I want the page break to happen, that's not the problem.)
My problem is that the last row on the page is being stretched to fill the page vertically. I would like it to be the same height as the other rows.
Is there a property that controls weather or not the last line of detail will stretch to the bottom of the page or not? Or is this intended (to show the reader that the data continues on the next page)?
I have tried setting the following properties of the Detail Section in my sub report: Can Grow, Can Shrink and Auto Height. I have also tried the Fit To Page property of the sub report itself within the report. But I still get a slightly taller last line at the bottom of the page.
Maybe I'm not googling the right words, I'm new to MS Access and access reports. I use Microsoft® Access® for Microsoft 365.

SSRS Report not correctly suppressing white space

I have seen some mind-binding situations with SSRS reports in my few years of using it, and I've been able to design around most issues and get it to do everything I've been asked to do.
But apparently, not something extremely simple!
I'm using Visual Studio 2019 version 16.7.2 with the Microsoft SQL Server Reporting Services Designers
version 15.0.19124.0 installed. There's no data bound to the report, this is just a simple design concept.
I have a report that has a static custom page size (in centimetres), interactive size and no margins (12.8 x 17.8cm).
The body size is deliberately set to make it a two page report (2 x the page height).
'ConsumeContainerWhiteSpace' on the report properties is set to true.
Page 1 has an image, consuming the entire space of Page 1 (size of 12.8 x 17.8), with a Text box placed near the bottom right of the image (overlaying it, but not exceeding the width or height of the page, and is set to not grow).
Page 2 is exactly the same, with the content starting where Page 2 would and should start (0, 17.8). However, the Page 2 content is set to hidden (hidden = true, on both the image and the textbox).
When previewed, the report renders two pages, one of which is blank.
If I take the Page 2 content textbox off, and preview it, the report renders as one page (as I need it to).
The same issue occurs if I replace the textbox with a Rectangle or Tablix (the two objects I really need to use in this report as well as the textbox located where it is) and set them to hidden.
Moving any of these objects to the top of Page 2, still results in the same behaviour.
It seems that certain objects, despite being hidden, have space allocated that can't be 'rolled up / truncated / shrunk'. Is this 'by design behaviour'?
Is there some form of magic-witch-craftery I'm missing here to get this to work, or simply something I'm not understanding... ?
Thanks for reading!
Note: So far I have tried the 'Switch to inches, then back to centimeters' solution mentioned in other posts along these lines, have varied 'Keep together' properties, checked 'CanGrow' and 'CanShrink' property changes - all of which have not helped find a solution.
The report body should be set at most wide enough to fit on your output page and long enough to hold all your report items. When you want different items to appear on a new page, put them in a container with a page break set either before or after (whichever is most appropriate). This can also be handled in a data driven manner using page breaks on table groups.
There is no requirement to have white space within your report design to 'fill up' the rest of the page on the rendered report.
If you want anything to appear at the bottom of the report, simply put it in the footer section. If you want specific things to appear at the bottom of the page of different heights on different pages, that is more of a challenge and will usually require some clever data driven spacers within the report body.

SSRS report shows me a Lot of empty space to the right hand side. (when you move the scroll bar to the right)

I have created a report using the Report Builder tool.
But, when I exported with the MHTML option it shows me Lot of empty space to the right hand side. (when you move the scroll bar to the right)
Any ideas please, can you help? I really appreciate your help.
If it is a matrix report, you may also try setting the ConsumeContainerWhiteSpace to true. It is Report level property that you can find under "Other".
or else if it is a tabular report then adjust the margin and width accordingly.
Here the solution link:
https://social.msdn.microsoft.com/Forums/Lync/en-US/4a965d5c-0906-4690-a995-35aae594018c/how-to-avoid-empty-space-in-right-side-of-the-ssrs-report?forum=sqlreportingservices&prof=required

SSRS Report Rendering Error: number of children on page and saved number of children for the page

I came across this weird issue recently while creating a report. The report would generate fine at first then as I clicked through the pages in the non-print layout the report would fail seemingly randomly around the 5th or 6th page. The error generated was, reportrendering:mismatch between the number of children on page and the saved number of children for the page. The report would not fail while clicking through the print layout but I could see the data not being included in the report past the point the report would fail in the other layout. Is this a common error in SSRS? I could not find any references to it while I was searching for a solution.
The problem with my report was in the tablix properties. I was using rectangles to group my tablix's into sections. It seems that since I had set page breaks after some of my tablix's that were contained within the rectangles it was causing this error. Once I fixed the tablix properties to not have page breaks and only applied page breaks after the rectangles the problem was gone. Just posting this in case anyone else encounters that error message as well. I did not see any other help listed for it.

SSRS 2016 - multiple tablix on one report causes overlap when rendering

I have inherited an SSRS report which had an existing tablix on it - I want to add a further tablix below to display data from another data set as the format is very slightly different - each tablix displays a different kind of sales for a certain customer.
I have added the second tablix and the report seems fine within the report designer renderer, but when I access it via MS Edge directly from the URL the first tablix overlaps the second and obscures it from view.
I have set a page break at the end of the first tablix, and at the start of the second, and again in the designer renderer it works fine and pages, but in MS Edge it overlaps across the page break. In Chrome it renders OK.
The issue I have is I am displaying this SSRS report in a Web Browser Control on an access for an it renders just like it does in MS Edge so it looks screwed up.
It is like the first tablix just runs over into page 2 rather than making the extra content of itself page 2, and the second tablix then on page 3. I don't even really need the pages as ideally it would all be one long report with a vertical scroll, but this overlap issue means I have been trying to force it to split.
Any other way I can stop the first tablix obliterating the second one?
I had a similar problem recently (I found your question while searching for an answer). I didn't want to go to all the trouble of creating a sub report and eventually tracked down the cause of the issue for my case which may be the same as what you were experiencing.
The issue was that my first Tablix was setup with a height of 2.7cm. My second one's top was 2.66781cm. That caused both of them to overlap with each other when the report was rendered. When I changed the top of the second Tablix to 2.7cm the issue was resolved.