Jump to content
We've recently updated our Privacy Statement, available here ×

C-Box

Members
  • Posts

    910
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Everything posted by C-Box

  1. Without a table you could use the default columnfooter band for that purpose, where you just evaluate if the current record count < the total record count. This is what I did in former times for some customers, that also wanted a "hint" on the current page, that some content is wrapped to next page(s). This was working fine... but I never used the table-component for represent the records. Within a table component it's probably (not tried) impossible (without the - sorry, but "quite senseless" - comment by hozawa to modifiy the (open) source-code of JasperReports library! ) Perhaps there is also a way to incrememt a variable that is evaluated for each table-row and you could use it "outside" the table for the default column-footer band and "redesign" a "fake table row" (some borders etc around a textfield) with your static text "to be continued" !??! Just give it a try! hth + regards C-Box
  2. There are NO PROBLEMS with TextAlignment in JR 5.5.1 !!! So no really need to update in this case. Please post your jrxml and a screenShot of the preview/result with the problems marked, so that we could throw an eye on it. regards C-Box
  3. It should be just an flag within the PrintRequestAttributeSet when I remember right. So you needn't to change the Printer settings in generall. So this is always the decission of the user how a JasperPrint will be sent to the printer and not defined in the design mode. (also like in MS Word... you PRINT it duplex and don't set an option to the word doc itself!) Something like. attr.add(Sides.TWO_SIDED_LONG_EDGE); hth + regards C-Box
  4. If you don't like (as me) to use the incredible slow JasperSoftStudio and also don't need any new features of JasperReports > 6.x, you could of course run iReport also in Windows10. The only thing you should be aware: iReport was designed in NetBeans and is NOT compatible with any Java Version > 1.7 So you will have to install/copy a JRE7 to your local machine and edit the iReport.conf (located in your iReport install directory unter etc ... eg "C:Program Files (x86)JaspersoftiReport-5.6.0etcireport.conf") and point to the JRE7 directory: eg: # default location of JDK/JRE, can be overridden by using --jdkhome <dir> switch jdkhome="C:\Program Files (x86)\Java\jre7" keep in mind, that any (newer) Java Setup could tell you, that an installed Java 1.7 is unsecure and should be deinstalled - you must ignore this warning (or your JRE7 will be uninstalled automatically) hth + regards C-Box
  5. When I understood right, the only problem is, that the SubReports present no data, but the defined space isn't removed, correct? So try to set the flag "RemoveLineWhenBlank" at the SubReport(s) element(s) to let them dissappear, if they don't render any data. hth + regards C-Box
  6. So just googled it for you and as for API docs from JasperReports it's still supported in 6.8.0: http://jasperreports.sourceforge.net/api/net/sf/jasperreports/engine/JasperRunManager.html So perhaps you should better describe, what you want to achieve?!? hth + regards C-Box
  7. Why so "complicated" ??? There is also an option "StartOnNewPage" at group-level. So if you create a group for your "sales rep name" and sort it already in your query, each sales-rep-name should invoke a page break and start on a new page... so you don't need to place any Break-Element in your group-Footer band, as this would cause an empty page at the end of the report when last group-footer is rendered. This isn't wanted... I'm sure! hth + regards C-Box
  8. Just add your own Hyperlink Listener to your own preview window in your appplication that shows the filled JasperPrint-Object and listen to the click events. Then you could interprete the hyperlink parameters and could just start a new report call to show the detailed data of your stacked bar either in same window or in a new frame. This is, what we've done, to enable "DrillDownFeatures" also without JaspersoftServer just with pure JasperReports Library Community Edition hth + regards C-Box
  9. have you already tried to set the "Reprint header" flag at your "dummy group" ? When I remember right, we used it to reprint "column titles" where the "normal" column header could not be used. But I'm not sure, whether the crosstab between will know the outside group header band when it breaks - so just give it a try hth + regards C-Box
  10. What about the spitting behaviour on detail-band level? I'd just set the "splitting type" to "prevent" at your detail band... that means, that the whole detailband is moved to next page, when one of it's element is stretching to the next page. Of course if your textfield will stretch over 2 pages at all, it won't work (as then the selected "prevent" type would actually cause an infinity loop, that is catched of course)... but in most cases we've used it successfully to prevent breaking content that should keep together. hth + regards C-Box
  11. I'd avoid switching to JasperSoftStudio if you don't need any new features of JR > 6.x --> it's a PAIN working with it, as it's terrible slow even on a Core7 with SSD and 16GB RAM.... (tested on serveral machines here at work and also at home) so if you are used in RAPID designing your JRXMLs the Netbeans based iReport is still the best choice -> of course not with the latest version of JasperReports. I don't know why the new Eclipse based Studio isn't optimized and don't understand where the performance is lost. I guess it's kind of bug whith rendering the jr-design object model. So as we intensively used the html formatting text features I can confirm, that there is NO problem within JR 5.5.1 with inline bold segments in a textfield... even when exporting to PDF! Many customers of us use this feature in there outgoing pdfs. Of course we use another Font (Arial) and we created a FontExtension for that. Also the sample report (see other post) is running fine in iReport 5.5.1 -> in preview and also in pdf-export. So the JR5.5.1-engine works well! @stenio that's why: track down the FontExtension problem in your application. For testing you could also change the font to the built-in DeJavu fonts. When I remember right, these are included in the default JasperReportsFontExtensions (that sould be as welll in your classpath of course!) hth + regards C-Box
  12. So if it's okay in iReport and not in your java-app.... then you should check the involved fonts. Check if all used fonts are available to the JVM and use a FontExtension for custom font's . Jasper itself has also a built-in font-extendsion when I remember right. (jasperreports-fonts-5.5.1.jar that should be within the classpath of your app) Probably your app don't know how to render the bold part of your textelement because of a missing bold-font??! regards C-Box
  13. ... and also just copied your full JRXML into my iReport and run it against EMPTY DATASOURCE: works... so I just can imagine, that the field content of your Field "dsUsuarioDeferimento" contains some illegal characters, that escapes the html-syntax!?!??! Could you post the field content also? regards from Dresden/Germany C-Box
  14. ... works like a charm (just putted your textfield snipped into an empty design): <?xml version="1.0" encoding="UTF-8"?><jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="report12" language="groovy" pageWidth="595" pageHeight="842" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="09565e94-7305-4c20-bd80-8383c088a43a"> <property name="ireport.zoom" value="1.0"/> <property name="ireport.x" value="0"/> <property name="ireport.y" value="0"/> <field name="dtDeferimento" class="java.lang.String"/> <field name="dsUsuarioDeferimento" class="java.lang.String"/> <background> <band splitType="Stretch"/> </background> <title> <band height="79" splitType="Stretch"/> </title> <pageHeader> <band height="35" splitType="Stretch"/> </pageHeader> <columnHeader> <band height="61" splitType="Stretch"/> </columnHeader> <detail> <band height="125" splitType="Stretch"> <textField isBlankWhenNull="true"> <reportElement isPrintRepeatedValues="false" x="0" y="70" width="535" height="50" isRemoveLineWhenBlank="true" isPrintWhenDetailOverflows="true" uuid="40729a1f-839b-40ca-8fe4-d053cfcbca5b"/> <textElement textAlignment="Justified" verticalAlignment="Middle" markup="html"> <font size="10"/> </textElement> <textFieldExpression><![CDATA["Documento assinado eletronicamente por <b>" + $F{dsUsuarioDeferimento} + "</b> , em " + $F{dtDeferimento} + " , com fundamento no art. 6º, § , 1º, do <a href=http://www.planalto.gov.br/ccivil_03/_Ato2015-2018/2015/Decreto/D8539.htm'><u><span style='color:#0000EE'>Decreto nº 8.539, de 8 de outubro de 2015.</span></u></a&gt]]></textFieldExpression> </textField> </band> </detail> <columnFooter> <band height="45" splitType="Stretch"/> </columnFooter> <pageFooter> <band height="54" splitType="Stretch"/> </pageFooter> <summary> <band height="42" splitType="Stretch"/> </summary></jasperReport>[/code]see preview: so no glue what's going wrong?!?! C-Box
  15. The NO-DATA-SECTION wouldn't help, as the GROUP-HEADER should contain the text "no data for this element" just for the grouped part of data... so the NO-DATA-SECTION would just appear, if the whole main query returns no data.... that's why - in my humble opinion - refactoring the design and queries into one grouped main and detailed subreport would make the life much easier in this case. C-Box
  16. Have you really switched the MARKUP attribute to HTML? Do you use the built-in Preview or the PDF-Export? Just post your whole jrxml otherwise. regards C-Box
  17. I've just putted your design into my good old iReport 5.5.1 (removed uuid's of course ) and run it against the EmptyDataSource with 10 empty records.. so no problem so far: I just placed the red colored REPORT_COUNT variable to show where the records appear. seems to be a problem with JasperStudio 6.6 and/or your data!??!?! Are you sure that all wanted records are really fetched from the query?? regards C-Box
  18. Why do you mix up Styled markup language with Html syntax? With pure html tags <b> and markup = html it's working fine so far: "Documento assinado eletronicamente por <b>" + $F{dsUsuarioDeferimento} + "</b> , em " + $F{dtDeferimento} + " , com fundamento no art. 6º, § , 1º, do <a href='http://www.planalto.gov.br/ccivil_03/_Ato2015-2018/2015/Decreto/D8539.htm'><u><span style='color:#0000EE'>Decreto nº 8.539, de 8 de outubro de 2015.</span></u></a>"[/code] hth + regards C-Box
  19. Of course you could count also at column level.... just take a look at the reset-time COLUMN, so the value will be resetted at each column break. But I still don't understand what you want to achieve. You said "suppress condition in crystal reports" ?!?! As in your initial post you want to "suppress" the whole group-header band if the actual group count is 0, right? So in this case, the report engine should know in advance not to print the whole groupheader-band if there are no records found in the group at the end..... so as the variable is incremented at each detail record how should the engine do that? So I would try to use a SubSelect within the main query and ask for your group-count something like "SELECT COUNT(FieldName) FROM TABLEX WHERE ConditionField = X ..." Or perhaps you could use a grouped query for the main report and use a SubReport with an own sub query for represent the detail-records for each group? So this would fullfill your needs much easier as you already know at group-header level if there are some records or not!??! hth + regards C-Box
  20. The PrintWhenExpression is normally evaluated at current runtime... so in a group-Footer it could work... but if you place your TextElement in GroupHeader, you can set the evaluation-Time to group.... but the PrintWhenExpression is evaluated BEFORE ... so at runtime... when the header is printed. Removing Elements AFTERWARDS should not be possible, as this could cause reallocate other (following) elements... so a NO GO... What I've done in former times.... not to use a PrintWhenExpression but use an IfThenElse - TEXTEXPRESSION with EvaluationTime set to Group: $V{Count_Field} == null || $V{Count_Field} == 0 ? "No records found" : $V{Count_Field} + "records found" hth + regards C-Box
  21. You could try to place your tables in group bands and set the group-flag "StartOnANewPage"... but if one table doesn't fit at one page in total and even just one row is placed on next page. you will earn a let's call 99% emtpy page (just with one row at the top) and the next table is starting at next page (e.g. 3)... so perhaps not a "nice solution" Otherwise you could also play around with some page_break_elements hth + regards C-Box
  22. btw... of course you could also load your images OUTSIDE before calling the FillManager and pass this as e.g. via HashMap where the key is for examle your MonthID and the value your preloaded java.awt.Image (or whatever else). ,> In groupfooter you could use the following expression as ImageExpression: ,> $P{MyCachedImageMap}.get($F{MonthID}) hth + regards again ,> C-Box,>
  23. Why you don't use a SubDataSource with a ListElement or even an own SubReport with a own query for your signature ? I'd place it in groupfooter so it load's your image for the current group. So each image is just loaded once per group and not per (detail) record. hth + regards from Dresden/Germany C-Box
  24. @Andrew... is the "Hiding Columns" Feature of the table component available in community edition? When I remember right, this was a ProFeature in former JR-Editions???? regards C-Box
  25. What's about the FULL STACKTRACE here and not just a snippet from the error itself to trace down the error!?! regards C-Box
×
×
  • Create New...