NextReports - Image support
Designer v2.5 will add support to image rendering in HTML, EXCEL, PDF, RTF. A new Insert Image action will be available in layout. Image will not be scaled.
Designer v2.5 will add support to image rendering in HTML, EXCEL, PDF, RTF. A new Insert Image action will be available in layout. Image will not be scaled.
NextReports application allows for report publishing on a NextReports server. A NextReports server is a web application which manages data sources and reports and schedules reports to run at specific moments in time.
To publish a report , the user must know a NextReports server (ip and port) and must have a valid account on that server (user and password).
After the login the user is allowed to upload a report to server to a specific path.
Version 2.4 of NextReports will bring new features for resizing columns.
It is possible to select more columns headers and set the size for all of them with the mouse right click. The headers selection is done in the same way the cell selection is done :
From version 2.4 NextReports will have support for default values in parameters definition.
The ‘Default‘ tab contains the default values the parameter can take. Those values can be added by hand to a list (as in previous image) or can be taken from an sql source . If the parameter has default values, those values will be selected at runtime. If parameter is checked as hidden the parameter will not be seen at runtime, and it’s values will be computed and set at the moment the query is executed.
For example if you need a hidden parameter that is substituted at every run with the current date, you can edit the source with “select sysdate from dual” for Oracle datasource. For Derby database used as demo you may use "select current_date from sysibm.sysdummy1". The user does not have to know the format of the select for the connected data source. A template button in the dialog source does it automatically.
From the new upcoming 2.3 version, it will be possible to set the size of the columns in the report layout.
After clicking the first button in the report layout toolbar, which means that the auto-size will be change to manual column size, the user will be able to right-click with the mouse on any column header and set a size in pixels for it. If the mouse is on the column line separator, it will change in a "resize" type and user will be able to drag it to the desired width (no less than 10 pixels and no more than 1500 pixels).
If the total column sizes is bigger than an A4 (portrait or landscape) the user will be notified by a message. The export for pdf and rtf will be in A4 format and it is done so that the report do not surpass that dimension.
By default the user is notified after every column resizing if the total width is bigger than A4 dimension. To disable this notification, in the settings configuration you will have to put the A4.warning property to false.
From version 2.2 of NextReports, there is the possibility to create a report from a stored procedure. To accomplish this, there is a syntax which must be used inside the query editor :
call
where ${P1}, … , ${Pn} are procedure IN parameters. These can also be parameters defined for the query and will appear at runtime. The ‘?’ parameter is the cursor output parameter. For Oracle databases this is used. For other databases like MySql and MSSQL , the call must not contain ‘?’ parameter.
Inside this syntax , also the package (for Oracle) or catalog for other databases must be specified (if there are more procedures with the same name in different packages).
call
call <catalog_name>.
Not every stored procedure is a candidate for reporting. It can have any number of IN parameters. It must have an OUT parameter of type REF CURSOR (and only one) for Oracle. Must not have any other OUT parameters.
If some procedure parameters are also query parameters, they must be checked as ‘stored procedure parameters’ and a preview value must be set for them. This preview value must be used inside the procedure business to exit as fast as possible, making the column finding process as fast as possible.
The user can drag and drop a procedure from the explorer panel to the query editor panel. If the procedure is not a candidate for reporting a message will notify the user. If it is a candidate, the general syntax shown previously will be automatically written to the editor. The user will have to define the parameters if any.
The user can see in the explorer tree all the stored procedures. There is an action on Procedures node which will validate which procedures are candidates for reporting. This process will mark the candidates with another icon.