Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Is it possible to hide a column in a straight table when I print a report?
I have a dimension called PageBreak which I use for Forced Page breaks. When I hide column PageBreak then report doesn't force page breaks anymore. One thought is to hide PageBreak column after report is generated but I'm not sure if thats possible.
Unless there is other way to handle this situation?
Well, the simplest solution (at least that occurs to me) is to create 3 objects, 1 each for Revenue, Expenses and Overhead. Then put one of these objects per one page of the report. So page 1 would contain the first (Revenue) object, etc.
Would that work?
Well, you would typically create a second chart that is used just for exporting and keep this export object hidden.
Regards,
Hello, I'm not sure if you read second part of my post, because that's where my problem is. If I hide my dimension column then my page breaks disappear too,
Thank you
I'm not sure I understand...why do you want to hide the column if you need the page break? Or do you mean you want to hide the column so users don't see it in the front end? Because that would be fixed by having the second object
Sorry for the confusion, I will try to explain myself better.
My straight table looks like this:
[PageBreak] [AccountName] [Amount]
Revenue Sales Frozen 8999.00
Revenue Sales Grocery 8999.00
Expenses Payroll Frozen 8999.00
Expenses Payroll Grocery 8999.00
Overhead Insurance 8999.00
Overhead Security 8999.99
I want Revenue, Expenses and Overhead to be printed out each on a different page, but I DONT want to print out column [PageBreak]. If I simply hide the [PageBreak] column then page breaks will gone and everything will be printed out on one page.
Thanks
Well, the simplest solution (at least that occurs to me) is to create 3 objects, 1 each for Revenue, Expenses and Overhead. Then put one of these objects per one page of the report. So page 1 would contain the first (Revenue) object, etc.
Would that work?
I ended partialy with this solution.
Main reason is that my table was getting very long with a lot of rows and it was hard to read and navigate around it. I ended up dividing 1 table into 3 tables (revenues, expenses, overhead) and using container to combine them. This way is much more practical and printing is done easily.
Thanks