Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338781

Summary:	Crosstab - Dynamic columns width autofit issues
Product:	z_Archived	Reporter:	Abhishek Kumar <g.abhishek.kr>
Component:	BIRT	Assignee:	Birt-ReportEngine-inbox <Birt-ReportEngine-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3	CC:	bluesoldier, g.abhishek.kr, jouyang
Version:	2.6.2
Target Milestone:	3.7.0
Hardware:	All
OS:	All
Whiteboard:

Description Abhishek Kumar

2011-03-03 04:29:23 EST

Build Identifier: BIRT 2.5.2.v20100210-0630

[BIRT 2.5.2] - While building the cross tab element (Tried with Excel Report fromat), What ever width I am assigninng to the dynamic column ..it always fits to the width of the Page (Master Page width). As a result of which if page width is defined lesser than the actual required ..individual column width gets shrinked & if moe then it expands. How can we contol the width as per the choice.

How ever I have noticed that this issue was more or less in the earlier version 2.2.2 too... But I had a work around of using grids with 2 columns & putting the cross tab in the first column.



Reproducible: Always

Steps to Reproduce:
1.Create a simple cross tab.
2.Set the columns width individually.
3.Case 1 : Set the page width higher than actually occuied (column width*no of columns) - result : Column width will be expanded than actual given
4.Case 2 :  Set the page width higher than actually occupied (column width*no of columns) - result : Column width will be compressed than actual given (#### can be seen)

Remarks : When the cross tab is meant for data based dynamic number of columns , why is this dependednt on page width ?? This restricts the cross tab purpose.

Comment 1 Jun Ouyang

2011-03-03 04:47:23 EST

In 2.6.2, for auto-layout report, top level items will be extended even if it exceeds the width of page.

Comment 2 Abhishek Kumar

2011-03-03 05:54:46 EST

(In reply to comment #1)
> In 2.6.2, for auto-layout report, top level items will be extended even if it
> exceeds the width of page.

Is there any thing that can be done with 2.5.2 ? (In reply to comment #1)
> In 2.6.2, for auto-layout report, top level items will be extended even if it
> exceeds the width of page.

Thanks for your input .. Is there any work around that can be used in BIRT 2.5.2 ? I doubt I shall be able to use BIRT 2.6.2 immediately.

Comment 3 Jun Ouyang

2011-03-03 20:49:48 EST

No, there is no workaround for 2.5.2. Please try to upgrade to 2.6.2.

Comment 4 Abhishek Kumar

2011-03-04 08:44:07 EST

Crosstab Format testing 

Case 1 - Layout 	:	Auto Layout
1.1 : When Individual column width not set - 
Result : If the page width is not sufficient then the data gettign wrapped & not getting auto extended as mentioned by you earlier.
1.2 : When Individual column width has been set
Result : 
a.) if page width is too less then table & workbook error come while opening the file.
b.) If page width is normal but less than actual required then its cutting the extra data & same is not shown at all--> this is critical as we have loss of data.

Case 2 - Layout 	:	Fixed Layout
2.1 : When Individual column width not set - 
Result : If the page width is not sufficient then the data gettign wrapped & not getting auto extended as mentioned by you earlier.
2.2 : When Individual column width has been set
Result : 
a.) if page width is too less then table & workbook error come while opening the file.
b.) If page width is normal but less than actual required then its cutting the extra data & same is not shown at all--> this is critical as we have loss of data.

Comment 5 Abhishek Kumar

2011-03-04 08:54:34 EST

Adding the build for your reference : 2.6.2.v20110219-1842

Comment 6 Xiaoying Gu

2011-03-11 05:28:14 EST

(In reply to comment #5)
> Adding the build for your reference : 2.6.2.v20110219-1842

Would you please attach a sample report for Case1(autolayout), senario 1.2 (b):
b.) If page width is normal but less than actual required then its cutting the
extra data & same is not shown at all--> this is critical as we have loss of
data.

I can not reproduce this issue in 2.6.2.

Comment 7 Xiaoying Gu

2011-03-15 03:42:28 EDT

Set as worksforme as I can not reproduce any of the case listed in comment 4.

Please feel free to reopen if sample reports can be attached.