Subquery Filters

From LongJump Support Wiki
Revision as of 19:59, 22 February 2013 by imported>Aeric (→‎Adding a Subquery Filter)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warn.png

Important: While some problems can only be solved using Subquery Filters, Database Views (which are simple joins) are much more efficient. In addition, it is possible for a user to write an extremely costly subquery that impacts other users when executed. As a result, Subquery Filters should be used with great care.

About Subquery Filters

Use SubQuery Filters to restrict the data that is visible in a View or Report based on data that exists in another view or report.

Adding a Subquery Filter

You can add subquery filters when creating or editing a view or report.

Choose values from the dropdown fields:

Field
The field that you want to use to restrict data based on another view or report. This field must be a Lookup or Related Object.
Operator
The condition you want to apply to the field as to whether or not it appears in the selected view or report. You can select In or Not In
View/Report
The view or report which contains the data you want to act as the subquery for the specified field.
Apply Operator on Field
The field on which you want to apply the operator. This field must also be a Lookup or Related Object.

Optionally, add additional subquery filter rows with logical operators:

In
Use the In operator to display records in this report that match the selected field in the selected View or Report.
Not In
Use the Not In operator to display records in this report that do not match the selected field in the selected View or Report.
Filterbysubquery.gif