beekerc69

I understand the $X syntax, but what if the parameter is not a required parameter (one that you can leave blank to mean "include everything"? for a single entry parameter $P you would use something like. select <field_list> from <table> where $P{<parm_name>} is NULL or $P{<parm_name>} = ID lf the parameter input is blank, then all records are returned, if a parameter input is speciried, then only the one matching reccrod is returned. how would the NULL condition be handled for $X select <field_list> from <table> where $X{IN, ID, <parm_name>} if the parameter(s) are specified then every record with that ID will be returned. how should the clause be coded to handle the condition if the input parameter is empty, implying "return all rows"? would this work or is it something else? select <field_list> from <table> where $X is NULL or $X{IN, ID, <parm_name>}

sorry, posted in the wrong place, meant this to be in the answers section to continue the thread

I'm converting reports from Crystal to Jaspersoft. The parameter nomenclature is similar but different "$P{<parm_mame>}" vs "{$<parm_name>}". but for the purposes of initial report creation, i comment out (using oracle double dash "--") any line that refernces a parameter so when i test it grabs all available records. however, when i compile the code, i get errors saying that "Query Parameter not found: <parm_name>". when i look at the code both in the Source tab and the DataSet and Query Editor dialog, every line referencing a parameter is commented out. why is this happening? do i still need to define parameters in the report if they're note being executed in the code? Then another odd thing happened, i removed the affected lines (so now there is no trace of parameter reference in the SQL code) and tried to compile and/or preview the report, and i still get errors to "Query Parameter not found" to parameter references that don't even exist in the report at all? is this normal behavior for Jaspersoft Studio or is this a bug?

two pie charts that i'm inserting into a report as two sub-reports because their data query is completely different from the main query in the report. the thing is between the two pie charts, they're very similar. one shows a count of projects by operational phase, one shows a count of projects by a health status indicator. the queries render 3 columns the first has phase (start, in progress, finished), then a count (number of projects in that phase category), and a numeric sorting key the second has health (red, yellow, green), then a count (number of projects in that health category), and a numeric sorting key. because they're two independent data sets i have two suberports. my question is, could i build a query that returns all this data in one dataaset, adding a column indicating "chart type" (1 for phase, 2 for health) then when i build the chart, let jaspersoft filter out which group of data i want to display in the chart. so for phase chart, can i indicate in addition to the fields i want displayed, to filter by $F{chart_type} == 1, and similarly , in the health chart, filter by $F{chart_type} == 2, but do this in the chart properties? or am i stuck with havnig to do two subreports? by extension, can i embed a data query into a chart so that i can include a chart in a report that has it's own embedded query and use those fields and not the fieds in the main report query? Thanks

i have a query parameter but need to tie it to a lookup query from the database as i want to control what can be picked. is this only available from the server side? or can one be created and attached to the paramter in Studio?