Request forms are used in connection with reports to let the end-user specify search criteria and filtering in a report.
Filtering on Request Forms
On a new report, the fields that you define as ReqFilterFields are shown, but you can determine if you want to place a filter on other fields by adding lines below those already used.
Remember that users can choose to set filters on fields which you did not specify. We recommend that you add fields that the users of the report will frequently set filters on. You should always strive for balance in your design. If the table has a lot of fields, inexperienced users may find it difficult to find the relevant fields that they want to set filters on.
To remove the tab where you set the filters, do not define any ReqFilterFields for the data item and set the DataItemTableView to define a sort order. If you create a request options form, it will still be shown.
If there is no request options form, an empty form is displayed. On this form, users can choose options such as Print and Cancel. If you set UseReqForm to No, the report will start printing as soon as it is run. In this case, users cannot cancel the report run. It will still be possible to cancel the report, but some pages may still print. If a DataItemTableView is not defined, users can select the key and sort order at runtime.
Be careful what you allow users to change. In complex report that involves data from several tables, the functionality may depend on a specific key and sort order. Letting the user choose filters freely does not interfere with the logic of the report.