Reports should inherit search filter from window

Description

I want to print a list of records. If I press the Report button in any adempiere window I get a standard report with only one entry - the record that is activated. I want to print the whole list of records. The best would be if one can select some records with the search button and then print a nice list of them.

This should work with the internal report generator and also JasperReports.

Environment

ADempiere 361

Activity

Show:

Thomas BayenJanuary 25, 2014 at 9:01 PM
Edited

The code integrated in trunk uses an array of record ids as a filter. In the JasperReports ReportStarter class this array is not used in a way that keeps the sorting of the records. You can even not sort them yourself by anything because an "ORDER BY" clause will probably break the query constructor. A view through the query constructor gives me the impression that there are some other issues.

Generally it seems a very bad idea to deal with an handcrafted (possibly complex) SQL Query with simple String search, replace and concatenation functions.

My proposal is to remove this thing fast in the hope that noone used it up to now and do it better.

A simple way for the future would be to let the report query writer decide where to include the IDs by using the

$P!{...}

syntax (http://community.jaspersoft.com/wiki/using-report-parameters). I expect something like this done in JasperReportsFreiBier.

Thomas BayenMay 31, 2012 at 3:56 AM
Edited

I want to add the conclusion if the idempiere weekly meeting at 2012-30-05:

<tbayen> I would like to summarize: We use one report button. In form view it prints a single record. In list view it depends on a SysConfig: Either it prints the filtered list or it opens a submenu (or doubles the entries in a already present submenu).
<CarlosRuiz> tbayen, the two buttons idea sounds clearer for user and for everybody
<CarlosRuiz> and we have now the ability to hide/show buttons per system/window/role

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

Created May 25, 2012 at 2:37 AM
Updated June 6, 2014 at 2:27 PM
Resolved April 26, 2013 at 10:01 AM