BackPrevious Topic Next TopicNext

Filtering Reports

To filter the data shown in a report, you can make use of the following filters:

  • Query filter (including filter on SQL and filter on APE), which applies to all data components that use the query.
  • Dataset filter, which applies to the data components that use the dataset in the current report.
  • Local filter on individual data component (Chart, Table, Crosstab, Banded Object, Geographic Map and KPI) defined via the report wizard or using the Edit Filter dialog. It applies to this individual data component and does not affect other components that use the same dataset.
  • On-screen filter, that is the filter created via a filter control. It applies to the data components that use the same data source as the filter control in the current report.

Dataset filters are passed along to the Query Engine the same as query filters. The two levels of filters are much more efficient since only the filtered data is returned to Logi Report. Local filters on individual components are not passed to the Query Engine so all data is returned to Logi Report and the component filters out the unnecessary data. This may be very inefficient so always use dataset filters or query filters whenever possible. However if you are using stored procedures, web services and other data sources, Logi Report may not be able to pass the filter to the Query Engine.

The advantage of using a dataset filter instead of a query filter is that it only affects data components that use the dataset in the current report. It still passes the filter to the database but does not change the catalog thus does not affect any other reports.

For data share concern, local filters most often cannot be pushed down to the database even though the Push Down Group Query feature is enabled, thus all data is returned and Logi Report filters the data locally which will use a lot more computer resources. To get better performance, it is better to define the filter at the other two levels.

To apply a local filter in a report using the Edit Filter dialog:

  1. Right-click a data component in the report to which the filter will be applied and select Format Filter to display the Edit Filter dialog.

    Edit Filer

  2. If the data component is created using a business view, the Filter drop-down list is available, listing all the predefined filters of the business view. You can select one from the drop-down list to apply, or select User Defined in the list to define a new filter as required.

    If you have applied a filter to the data component when creating it via the Filter screen of the report wizard, the filter conditions are automatically displayed. You can remove or edit the conditions according to your requirements.

  3. Add the filter conditions as required. Based on the data resource type from which the data component is created, a business view or a query resource, the way to format a filter for the data component differs.

    If the data component is created using a business view, you can add filter condition for it in the same way as you add conditions for a predefined filter in the business view. Besides, you can use a local parameter as the value of a filter condition.

    To add filter conditions for a data component created using a query resource:

    1. Select the Add Condition button to add a condition line.

      Filter Condition Line

    2. From the field drop-down list, select the field to be filtered. All the DBFields in the query resource the data component uses, as well as the parameters and valid formulas of these DBFields in the same catalog data source as the query resource are listed in the drop-down list. You can select any field to filter.
    3. From the operator drop-down list, set the operator with which to compose the filter expression.
    4. From the value drop-down list, select the value or values of how to filter the field depending on the selected operator.

      You can also type the values manually in the text box if you are familiar with the values. If multiple values are required, you should separate them with ",", and if "," or "\" is contained in the values, write it as "\," or "\\".

      (missing or bad snippet)
    5. Select Add Condition to add more condition lines and define the logic (And or Or) between the condition lines.

      To make some condition lines grouped, select them and select the Group button, then the selected condition lines will be added in one group and work as one line of filter expression. Conditions and groups together can be further grouped. To take any condition or group in a group out, select it and select Ungroup.

      To adjust the priority of the condition lines, select it and select the Up or Down button.

      To delete a condition line, select it and select the Delete button.

  4. Select OK to create the filter.

    Then when you preview the report, only data satisfying the specified filter conditions are shown in the data component.


  • The following SQL type of data cannot be filtered: Db.SQL_BINARY, Db.SQL_BLOB, Db.SQL_CLOB, Db.SQL_LONGVARCHAR, Db.SQL_LONGVARBINARY, Db.SQL_VARBINARY and Db.SQL_OTHER.
  • If a data component in a page report is created on an HDS, the filter conditions you define in the Edit Filter dialog for the data component will not be applied when the report runs due to the specialty of HDS. Therefore if you want to apply local filters in such type of data components, you need to make use of the dataset filter.

Back to top

BackPrevious Topic Next TopicNext