I've added a sortable spry table on my website. It works great everywhere except Internet Explorer. And I'm really struggling because no one can't tell me how to resolve the issue.
In the page, you can see the table right at the bottom.
You're first defining the CSS width like this, and then dynamically replacing it with the real values. However, this is invalid CSS which, apparently, IE not only ignores but discards altogether - the entire style attribute is removed from the DOM.
Related
I am on Msoft SQL Server Report Builder, v15.0
I have a multi page report that no matter that forces a blank page every 2nd page.
I have searched through the tablix properties, report properties, header & footer properties and have not found a culprit yet.
I fear that there are somehow some hidden pieces that are causing this issue, but I do not know how to be able to see the hidden pieces.
I have opened the .rdl file up in notepad++ and started walking through the code, but I am not certain where I should look at in there that would cause my problem.
It is a 10 column report that is generated from a dataset culled down, but the report has 3 calculated fields in it, including a column which generates a ranking number.
If you know of a explicit piece of code I should search for that would be awesome, but I know that is a needle in a snowpile.....
Found finally what I had done...
my durn body was the same width as the page sheet so it was pushing the margins off and creating a new page.
Here is a good walk through of what I found.....
http://www.keepitsimpleandfast.com/2009/12/export-of-reporting-server-reports-to.html
I have a KendoUI Grid that holds records. One of the values in a record is a boolean that I am using to show/hide a command (delete). I was trying to follow the instructions here:
http://docs.telerik.com/kendo-ui/api/javascript/ui/grid#configuration-columns.command.visible
I then realized, if you click on the "Preview" it doesn't even work for them. I know I can use a template to set the class of the div tag and then hide it with some jQuery, but would rather do it with their built in feature...if it even work. Has anyone had any luck with the command visible command?
The link is working as expected now. I am also pasting a Dojo just in case:
Example
BIRT 3.71v20110905
One of my data fields is a CLOB with html tags. I'm using the Dynamic Text Control in my report. This specifically happens when:
The Dynamic Text Control content type is to HTML or Automatic
in my case since I have html tags in the data. (Problem does not occur if I set the content type to Plain, but then the HTML tags show up in the report output as text.)
and
The total amount of data to be displayed by the control is more than one full page on its own
(without taking into account spacing used by other controls). If the
total amount of data to be displayed by the control is less than one
full page but can't all fit on the current page, it works as expected (meaning it displays what it
can on the current page and wraps the rest correctly onto the next
page.)
Is this a bug in the calculation for the DTC pagination?
Additional notes - I encountered this while trying to use a sample report that inserts a page break as needed between groups for duplex printing. It works great under most circumstances, but not when this DTC pagination issue rears up. ( GroupAlwaysStartsOnOddPage.rptdesign )
Sorry to disappoint, but this is a known issue and has not yet been resolved. At least not in the version of BIRT that Maximo is using.
What I tend to do is break the dynamic text where possible, experiment until I get the largest possible part on one page and put the rest into another dynamic text field.
This is obviously only a work around, but as far as I know there is not much else that you can do.
We ran into this problem with a dynamic text field containing HTML content coming from IBM Maximo long description fields. The report was designed in BIRT 3.7.1 Designer.
We were able to work around the duplication bug by changing the layout from Fixed to Auto. With Auto layout, it is also not necessary to change the Display setting of the field to "inline" (which we previously had to do to allow it to flow between pages without creating an initial page break).
In our case, changing the layout to Auto did not have negative effects on the appearance or geometry of our report.
I'm having a bit of problems creating a DataGrid with a header label AND a text box (at this point I'm not even entirely sure this is possible).
Here's what I want to do:
I need to dynamically create a table (the number of columns can and will change, so the grid needs to be created dynamically and cannot use bindings specified in the XAML code or similar). All the columns however will always be text columns.
Because those will be text columns, I'd like to add a text box to each header to enable simple filtering of the data in the DataGrid. I don't want to add extra text fields to OTHER parts of the Silverlight page, as I want to keep things as compact as possible. Also, since the number of columns is dynamic, adding a large number of text boxes above the DataGrid wouldn't look too good either. ;)
Also, if possible, I'd like to keep a label in each header to display the names of the columns as well.
So far I've tried adding the a TextBox as the Header of a DataGridTextBoxColumn but when I do that in a very simple Silverlight project, the whole DataGrid won't show up.
Please help.
EDIT:
I saw the answer to this question: placing a text box inside the silverlight data grid column header
However, the answer itself didn't give me much to go on (the example is too short, and I'm not too good with XAML yet), and the code on CodePlex just adds extra fields to the Silverlight page. None of it tackles the problem of dynamically creating the DataGrid.
OK, here's what I did that solved my issue...
I had to use a Style to achieve the functionality of having an extra text box inside each column header and filling out the Tag property of each thus created TextBox to later find out which column has been changed.
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...