Hello All,
Can anyone let me know any work around on the Fit to a single page(Page Layout Mode) in the Web intelligence Document which has more than 60 reporting columns.
kivi (BOB member since 2007-12-26)
Hello All,
Can anyone let me know any work around on the Fit to a single page(Page Layout Mode) in the Web intelligence Document which has more than 60 reporting columns.
kivi (BOB member since 2007-12-26)
You can fit it but you canât see the content inside
Thanks,
Zaif
zaif235 (BOB member since 2010-06-15)
Hi,
Try to keep the page orientation as Landscape and keep the page size as A0.
Hope this will help you.
S_Shetty (BOB member since 2010-07-15)
Hi
click on the report body i will select the entire page and then go to properties â>pagecontentâ>change the vertical records and horizontal records per page
Hope this helps u
sunil kumar (BOB member since 2011-10-03)
How will that help? :?
Hi Mark
Actually they asked to fit 60 columns in a single page . i thought that it is in quick display mode . sorry for the post .
sunil kumar (BOB member since 2011-10-03)
Um, export to Excel?
How anyone can work with tabular data in Infoview is beyond me.
If you are trying to get a data range that large to fit to page in WEBI youâll struggle (Iâve tried myself - I gave up)
Fit To Page is the thing I miss 2nd most about v5⌠2nd only to Alt+F11⌠and only slightly above âSave as Textâ
Penfold (BOB member since 2008-05-09)
Iâve managed to fit a LOT in some of my WEBIâs by changing a few things:
However Iâve never come close to 60 columns
So I have to ask the obvious, here. jumps up on the soapbox.
Who is asking for this and WHY?
Even on a paper size of 17" wide, with no margins, you only get approx .28 inches per column (and thatâs assuming all are equal size). Thatâs about the equivalent to 3-4 characters at most.
I cannot help but think that a report with 60 columns on one page will never be legible.
Even if your users have no intention of printing but want it on one âpageâ on the screen, they will have to constantlly use scroll bars to look around such a large set of data.
When users I had asked for similar requirements, I always took a step back and asked them âWhy One page?â.
Usually the answer came down to something like âWhen itâs all one one page, I can easily scan the report and see which stores/products/whatever are out of line. Then I can run xyz report to get the detailâ.
My compromise was to find out what âout of lineâ meant, and build exception based reporting around those rules only. One such report ended up with a nice scorecard type layout that had one list of stores with under performing sales, one with overperforming, one with âsales out of trendâ etc⌠Then each of those rows linked to a detail report. Overall it was much easier to read than trying to cram every measure into one report just âso we can easily see the issuesâ.
JPetlev (BOB member since 2006-11-01)