I am trying to freeze rownum column of grid. Because I have replaced text of rownum with meaningful row description.
I took help from jqgrid freezing columns demo. But it is not working out for rownum column.
My grid loads local array data and using version jQgrid 4.3.2
Aftert his I tried another approach to freeze first column with property
'frozen: true' and then I call function $(grid_selector).jqGrid('setFrozenColumns');
and I get below issues:
The grid loads becomes exceptionally slow (tested in IE, Firefox)
After much wait when page loads, the row header alignment is distorted. All rowheaders get shifted one step up and overlaps Caption div.
Row1Header goes into Caption place - Row2Header goes into Row1 and so on..
My ultimate requirement is to freeze rowheaders. Any help is much appreciated.
Thanks
Related
I'm having an issue with a my current dgrid. I have a column which is dijit/Form/FilteringSelect with a Ajax-based store. The store works fine for searching and populating, but, when I open a page with the dgrid store having a couple of rows already I face a problem. Only the last FilteringSelect triggers the edit event and fires the XHR request.
For example, if the Grid store has 4 items, so it will have 4 rows, only the FilteringSelect of the last row will go to the server to get the display value.
I'm a bit lost, any help?
when I login for the first time on my page I view the information in staggered rows in the table (rich:dataTable). As soon as I step just with the mouse pointer on these areas, the text in the cells goes to occupy its correct position.
I see the text in the header of the columns hidden by filters that are below (the correct position is on top of the filters) and a few rows back off the table but on mouse hover are shown automatically in the correct position of the row in the table.
Can you help me to solve this problem? I use RichFaces 4.3.7 and IE8.
Thanks
I have a scenario where i need to use scrolled paging on my jqgrid, and it works perfectly. But now i need to add dynamic grouping capabilities to the grid as well. The problem I face, is that when I group the grid, only records in teh currently loaded page get grouped, and not the whole underlying dataset. Is there a way to acheive this using jqgrid.
a. Grouping groups all rows in a dataset, not just the ones loaded in a scrolled page in the grid.
b. When expanding such a group and scrolling, the grouped rows now follow scrolled paging
Any help here would be appreciated as I have been trying to figure this out for a while now with no luck :-(
Thanks
Lokesh
I need to change the orientation of a table in a BIRT report so that the table header is vertical instead of horizontal.
Is this possible? I don't want to use a Crosstab.
It seems this thread is still being pointed at so I posted an example of a horizontal table layout using a crosstab. I know it won't help the original author but others following this thread now may find this helpful.
To create the horizontal grouping, first create your query like normal, then create a Data Cube. In this data cube, drag each field that you want into a group. Then drag a new crosstab on the report and drag each field into the top right column group area. It will create a new header row for each field. Don't put anything in the left side (Rows) and don't put anything in the measure field (bottom-right). This will create labels on the left... and the data will extend out to the right.
The report design example can be downloaded from: http://developer.actuate.com/community/forum/index.php?/files/file/1079-horizontal-table-using-crosstab/
Virgil
If you want dataset records to be reported across the page, this would have to be done via a crosstab.
If you want dataset records to be reported down the page, this can't be done automatically as far as I know. However, it can be done by inserting a new detail line in your report table object for each database field to be reported, then moving column headings from the heading row into the first column's detail rows and moving record values into the second column's detail rows.
So, for example, a report with 6 columns in it would become a two column report with six detail rows.
Not in box (up to 3.7). You have to use 3'd party libs like that one.
After upgrading BIRT from version 2.3.2 to 2.6.1, some reports have started producing empty first pages. I've checked the source XML of the rptdesign and the referenced rptlibrary and verified that ALL settings of page break properties are set to "auto". I.e. there are no forced page breaks anywhere in the report definition. The first page contains the master page header/footer items but no data.
Being a relative newbie to BIRT I'm not sure where to go next to solve (or even debug) this problem. My Google-fu turns up some old BIRT bugs (2.1 timeframe) relating to empty first pages but they were resolved long ago.
Can someone suggest how debug this?
First Page
Second Page
I have identified the source of the problem. When this report was
originally designed (long before my time) a grid was used to effect some
padding around the outside of the content. At the top level of the
design (in the body) is a 3x3 grid with skinny top and bottom rows and
left and right columns, with all content going in the center cell.
body
grid
column1 width=2%
column2 width=96%
column3 width=2%
row1 (empty)
row2
table with all report content
row3 (empty)
All the border cells are empty, and if I completely remove the grid and
place the content table in the body directly, there is no initial page
break.
body
table with all report content
So the bug appears to occur if the content, which is larger than a
single output page, is inside a grid. In this case, the normal
suppression of the page break before the first page does not seem to
function.
It's not clear if this is a bug or a design decision, so I have asked
on the Eclipse community forums if this behavior is expected. I will
update this answer when I get a definitive reply.
EDIT: Looks like a BIRT Bug
EDIT: For us, an acceptable workaround is to simply delete the first row in the grid, which consisted of only empty cells anyway. If the too-large section occurs in the (now) first row, the spurious page-break disappears.
This happened for us when we were including svg - images in Birt. Removing them in the XML - document fixed the Problem. Interestingly this only happens with specific svg - images and not with all of them...