Problem after hiding a GRID/TABLE

I have this odd problem. I'm sure this is a "me issue" as it happens throughout all my reports.

I have a CMPM report that hides fields based on whether or not the type of Maximo Work Order is a CM or a PM. In all instances of this, I have either the GRID/TABLE/FIELD or a combination of 2-3 of those hidden with the following code:

Visibility (hide for all outputs if) - row["pmnum"] != null

The gap noted in the attachment is causing quite the issue with extra pages, large blank spaces, etc. Any help you have would be greatly appreciated.

Thanks, Shadraq

Find more posts tagged with

Comments

mwilliams

What is your BIRT version? You don't know if you hide a grid/table until you have the data? If it were by a parameter, you could drop the table from the design. Any way you can reproduce the error with the sample database? Worst case, can you attach your report design?

TheShadraq

Mike, Thanks for the quick reply.

I am running:

Version: 3.4.2
Build id: M20090211-1700

Being a relative newbie to BIRT & this site I'm not sure I fully understand your questions, but I'll take a crack at them:

1. I assume that because I have parameters attached to this TABLE that the query runs prior to populating

2. How would I do this?

3. Are you inferring there is a sample database on this website or are you asking if I have sample data that I can run this against, apart from my production database?

File is a .rptdesign. I zipped it. Let me know if you prefer a differing format. The section I referred to in this and the original post is at the very top under "Problem Description" and its corresponding parameter [longdesc]

Thanks,
Shadraq

mwilliams

If you go into BIRT and make a new dataSource, there is a ClassicModels Sample Database option for a source. From there, you create a SQL dataSet based on the sample database tables. For the parameter, I meant, if you are choosing to run a CM or a PM by a parameter, you could drop the unneeded table/grid in your beforeFactory. If you don't know which table you'll hide til you get your data, you'll have to stick to hiding or making the display property equal to "none". This may just have been a bug in your version, but if you could reproduce what you're doing to hide the table and cause this space with the sample database, I'll take a look at it.

TheShadraq

Thanks for the info. I'll give both those a shot and let you know what happened.

When you say change the display property to "none" are you referring to (click grid/table) --> Properties --> Section --> Display --> "No Display" ... or something else?

TheShadraq

Thanks for the info and the help. I'm posting what I did to fix this in case anyone else stumbles through looking for this answer:

I realized that in using VISIBILITY option, The section I was hiding had still been "built" by the report. Just because I was hiding a field/grid/table didn't mean it the white space was going to disappear. The white space was already built after the query ran.

So:

1. Create a new Table - Detail Report Section and move grid/table you wish to fully hide into it (see blue section in attachment)
2. Keeping new Table - Detail Report Section highlighted, click Visibility --> Hide Element --> (fill in your options)

By doing the "hide" here rather than at field/grid/table level, this section is fully hidden and white space removed.

Hope that helps!

mwilliams

Thanks for the update!