Hide Group Headers depending on detail

Hi,
I have a report that contains several groups. The lowest/last group is "category". In this group, I have 3 categories - labor, material, external. Depending on the category, I display different columns from one table in a row. For example, labor displays employee, hours, amount. Material displays part #, description, cost. All the data is contained in one table.

Depending on which group is currently printing, I need to display different group headings. In BIRT 2.1.3 I was able to use the visibility property to hide the heading and the detail depending on the category (ie. I used the expression row["CATEGORY"] != "LABOR" , etc.). This worked fine in BIRT 2.1.3.

I am now using BIRT 2.3.0 and the detail lines still work - they are suppressed when they should be. However, I can't suppress the headings when a category goes over one page. If a category goes over one page, then all the headings are printing for each category.

I can make it work if I don't repeat the group headers, but I need to print the headings on each page. I also do not want a page break when a group changes.

Is there a way to do this?

Thanks for any help you have.

Nancy

Find more posts tagged with

Comments

mwilliams

Hi Nancy,

Do you think you can recreate this issue with the sample database or with a flat file of your own data? Thanks.

nancyw

Hi Michael,
I'm attaching a report using the Classic Models database. I'm grouping by productline, using the Products table as my dataset and including the Classic Cars, Motorcycles and Vintage Cars product lines. Page 1 starts fine, but the top of page 2 is where the problem is.

I forgot to say that I need to print the report as a .pdf.

Thanks for your help!
Nancy

nancyw

Hi,
I sent in a sample report about a month ago to show my issue with the headers. Has anyone come up with a solution yet?

mwilliams

Nancy,

Sorry for the delay. I don't have a copy of 2.3.0 on my computer to try this report in, so I tried it in BIRT 2.3.1. It seems to work as expected. It must've been an issue in BIRT 2.3.0 that you're seeing. Is there any way you can jump to 2.3.1 instead of 2.3.0?