Field

Description

Data Set

A Data Set definition can be entered here to display the information created in the data set (No query or fields are required for this).

Condition Field

A function that determines whether a record should be included or not. The function returns a logical value: yes to include the record, no to exclude it.

Maximum Rows

Allows the query to fun faster by only displaying a maximum number of rows per query. 10.23 onwards, this defaults to 10

Extra Parameters (10.23 onwards)

Where a dataset has been specified, this field allows entry of of parameters (URL) that are needed by the dataset query.

e.g.

The parameterised fields are so that you don't have to 'hard code' queries in the dataset to get it to run in the query editor – particularly if there are date replacements etc with fields like {RS_glp_fdate__2}. Or another useful reason for using these parameters is so that you can test results in a efficient way for instance: if you have a query on the dataset which reads:

FOR EACH jc_job WHERE jc_job.kco = {kco} {jobSelect}

You could call the dataset from within the query editor and in the parameters say jobSelect=and jc_job.job_num = 'XXXX' (where XXXX is a vailid contract number).

That way the dataset would run but for only contract XXXX - This is good to save time in checking the validation of fields in the dataset as you don't have to wait till the whole dataset evaluates prior to getting a response back.

If you have more than one {} replacement in your dataset then you would separate the parameters with a & symbol Eg: Dataset query might read :

FOR EACH jc_job WHERE jc_job.kco = {kco} {jobSelect},

EACH jc_costcode of jc_job WHERE TRUE {jccSelect}

You could call the dataset from within the query editor and in the parameters say jobSelect=and jc_job.job_num = 'XXXX' &jccSelect= and jc_costcode.jcc_cc = 'YYYY' (where XXXX is a vailid contract number and YYYY is a valid Costcode).