View filters versus report limits

View filters and report limits are similar filtering features, as they can both be used to restrict the final result set by setting criteria on the report metrics.

You can define report limits on the value, rank, or percent of the metric value returned. For example, if you set a report limit of Employee Headcount greater than (>) 5 in the Employee Headcount by Region report in the MicroStrategy Tutorial project, the report returns the following results.

An important aspect of report limits is that they are processed by the SQL Engine after metric aggregation. In the report SQL, the report limit definition is included in the Having clause, instead of the Where clause as for the report filter. You can observe this in the report's SQL statement, shown in the image below.

In addition to this functionality, the following features supported for report limits are not supported for view filters:

• Prompts within report limit

• Break By

The table below compares the available features and feature requirements of view filters and report limits:

Features and Feature Requirements	Available in View Filters	Available in Report Filters
Attribute qualifications	Yes	No
Simple metric qualifications	Yes	Yes
Can define filtering at report run time by including a prompt in a qualification	No	Yes
Can define Break By filtering parameters	No	Yes
Evaluated without re-executing SQL and querying the data source	Yes	No
Requires OLAP Services license	Yes	No
Can quickly switch the level at which the qualification is evaluated from report level to the level of attributes displayed on the report	Yes	No

For general information on report limits, see Comparing view filters to report filters and report limits.

For design considerations on using view filters versus report filters, see the In-memory Analytics Help.