Jump to content

Friendly User

Members
  • Posts

    435
  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Forum

Downloads

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Security Advisories

Events

Profiles

Everything posted by Friendly User

  1. The description of the input control repository item might be obtained through the /rest_v2/resources service. It will return the generic information about the element. The /inputControls/values request returns all the values that input control allows to have and information about which values are selected. It is an expected result for /values request.
  2. This question is a bit confusing, You don't really name objects in iReport / report, when you use expressions you also don't create objects that persist and have to be named. You can give keys to the report elements but that's quite different.
  3. If you remove FALSE() from the report design, does it work properly? If yes, you might want to get a false value in a different way instead like java.lang.Boolean.FALSE or just false.
  4. 1. Make sure in your data adapter you have a proper mask for the date/time fields. 2. Make sure the Java type of the field is appropriate as well, something like java.util.Date.
  5. There are no custom validators for the input control elements themselves. You'll probably need to customize the input control JSP or do validation on a report level and run some different version of a report it if the input is not what you expect.
  6. Subreports inherit the properties from the main report. You will need to define the properties on the main report level.
  7. Remove the extra bands from your report design like ColumnFooter, PageFooter, Summary, etc. Also make sure your detail band does not contain any empty space itself.
  8. For the location of the file the JasperServer plugin is looking at the following properties: <property name="ireport.jasperserver.url" value="http://somewhere:8080/jasperserver-pro/"/> <property name="ireport.jasperserver.user" value="superuser"/> <property name="ireport.jasperserver.report.resource" value="/public/report1_files/main_jrxml"/> <property name="ireport.jasperserver.reportUnit" value="/public/report1"/> Do you have them set in your JRXML? If not, you may want to specify them manually. If yes, are they set correctly? As for problem #2 try to either re-create the connection to the JasperServer or take a look at existing connection -> advanced settings. There is a property named "workspace folder". It may point to a folder that doesn't exist in your current workspace. Might be worth specifying a concrete folder if none is specified. Another thing is to try to run JasperSoft Studio with -clean flag to clear your workspace (add the -clean to the .ini file or shortcut target)
  9. You can try to add it to JVM options. Depending on what application server you use, there is different way of specifying it. For example for tomcat it usually is set in setenv.sh/bat file or in service properties if you run tomcat as a service.
  10. Report will automatically paginate if your detail band + other bands go beyond the page size and your Ignore Pagination parameter is set to False. Some formats like HTML do not have pagination by default.
  11. I guess you're using JasperServer to export reports. To change this behavior go to your WAR file location, for example for tomcat: /tomcat/webapps/WEB-INF/classes and edit the jasperreports.properties file. Find and switch this to false: com.jaspersoft.jrs.export.xls.paginated=true Save and restart the server.
  12. You can try downloading the existing domain XML schema and the creating a new domain from that schema. To download the schema edit the domain in the domain designer and press Export Design button. Save the schema.xml. Then create a new domain and instead of creating a new domain using the domain designer select the Upload option and point it to your schema.xml file.
  13. The input control and the report can have different data sources. If your input controls are internally defined you'll need to go through all the reports and change them manually. To avoid that in future it's a good practice to use external input controls and use profile attributes in the data source values so you can have exactly the same structure in the repository but have an option to define the data source connection details through the server or organizational or user level profile attributes. You can read more about that in JRS Admin Guide.
  14. If the images are part of the report itself (report content resources) you can just reference them by ID in your image expression like "test.jpg". If the image is a repository resource you can use "repo:/path/to/image" syntax to reference the image. For REST v2 there is a parameter called attachmentsPrefix that you can try using. I am not sure it's present in 5.6. For HTML output, this property specifies the URL path to use for downloading the attachment files (JavaScript and images). The full path of the default value is: {contextPath}/rest_v2/reportExecutions/{reportExecutionId}/exports/{exportExecutionId}/attachments/ You can specify a different URL path using the placeholders {contextPath}, {reportExecutionId}, and {exportExecutionId}. The {contextPath} can be also manipulated through deploy.base.url property in js.config.properties file. If you are to use REST v2 it's generally recommended to use 6.3/6.4 version as it has more ironed out and more feature complete REST web service.
  15. Maybe your text field is evaluated earlier than the variable is calculated. Try to change evaluation time from Now to Report for example and see what result that yields.
  16. If you want to display both percentages and sum values then you'll need to create 2 measures. One will display the sum without percentage, the other will display sum value as percentage of grand total.
  17. It's an either/or scenario. The way I do it so that I can see image in both server and JSS is that when I add image I select the "Workspace item", pick an image from workspace and work from there. Then when I publish the report the publish option will ask me if I want to publish the images too and I can pick that. These images will be publish as report resources and they will be referenced by the server too.
  18. The Gantt chart in Jaspersoft Studio is under Components Pro -> Widgets Pro -> drag it to the pane -> select Gantt Chart. It is a fairly complex chart with a lot of datasets that can be used. I don't have any documentation at hand for it unfortunately. I'll see if I can find something.
  19. There is no functionality like this out of the box. You will have to create a custom input control JSP to introduce a feature like that. See JasperReports Ultimate Guide for more information on custom input control JSP's.
  20. Create a variable with No Calculation Function and expression $F{myField}. The variable will always have last value of the field.
  21. Responsive as in resizable so they can be properly viewed on any device? Yes, visualize.js can help you with that but bear in mind that visualize.js is a library/framework which provides you JavaScript wrappers for REST v2 calls. You can call reports on demand using visualize.js and embed reports into a web page like that.
  22. So you want something like pass a JSON data source for the report and that JSON data source will need to run SQL queries to obtain data for those values? That won't work unfortunately. You can either have an SQL query to a data source or have a JSON file as a data source. You can try to write a program that would execute these queries and form you a JSON file as a result which you can then feed to a JasperReport for data. Or create a custom data source object but that would also require additional coding.
  23. Possible the equation 30* 24 * 60 * 60 * 1000 overflows because that value is way to big for an integer to store. Might want to try something like 30L * 24 * 60 * 60 * 1000 so it forces to a Long.
  24. Hello, i don't think you can use the SQL functions in the $X{} clause. It's $X{Function; Field_name; Parameter_name}. Field_name needs to be something identifyable for the compiler, it can't identify the functions. The $X{} clause is made to avoid the specifics of certain database engines about how they require different operations to be coded. Adding extra functions there removes the whole purpose of this.
  25. When you export the report, the data source gets exported with it. You can edit the datasource related to exported reports and change the connection details there.
×
×
  • Create New...