I have a tablix(table) with column grouping making the number of columns dynamic.
Although our customers have been warned that this could lead to the columns going beyond the edge of the normal landscape 8.5x11 inch page, they have asked for alternate solutions.
Beyond rotating the column labels and reducing fontsizes, the issue is not so much that it goes off the page, but the fact that in print preview mode the data is broken up requiring that you go to the next page to get the remaining data.
What I am investigating is whether the Page Properties of the report body, either the pagesize property and/or the interactivesize property, can be manipulated at run time?
This way if a user, based on their experience with the parameters they usually select and pass into the report, knows that the results will span the length of the page onto a second page, could choose a new parameter such as pagesize/interactivesize so that
it changes from 8.5/11 to perhaps the next standard page size of 8.5/14 inches?
This does not mean the contents would change during the course of rendering the report, just a new input that could decide at run time what paper size to use in print preview mode.
View Complete Post