MicroStrategy ONE
Filters on MDX Cube Reports
In MicroStrategy you can use a filter to specify the conditions that report data must meet to be included in report results. For MDX Cube reports, most of the filtering features remain the same as those for standard MicroStrategy reports. For more general information about filtering, refer to the Filters section in Advanced Reporting Help.
In a standard report, the filter is evaluated independently of the report template in most cases. However, in an MDX cube report, due to the nature of MDX, a close relationship exists between the objects in the filter and the objects in the report template. Because of this relationship, qualifications on MDX cube reports are performed at different points during report execution:
- Qualifications on dimensions that are not included in the template are evaluated as a filter before metric aggregation. For example, the Year attribute is qualified on in the report filter and an attribute in a different dimension such as Store is on the template. In this scenario, each metric value is restricted to consider only those years determined by the filter before aggregation.
- Qualifications on dimensions that are included in the template are applied as a limit after metric aggregation. For example, the Year attribute is on the template and Year is qualified on in the report filter. In this scenario, the report results are restricted as a limit after metric aggregation.
Metric qualifications that have a specific output level are evaluated along with the output level attribute, either before or after aggregation.
The logical relationships between qualifications are set automatically depending on the dimension or dimensions to which the filtered objects belong. The following rules govern the logical operators between qualifications:
- Qualifications that define attributes in the same dimension are joined by the OR operator. For example, Customer and Customer Region both belong to the Customer dimension and would be joined with the OR operator.
- Qualifications that define attributes in different dimensions are joined by the AND operator. For example, Category belongs to the Product dimension, and Year belongs to the Time dimension and would be joined with the AND operator.
- Metric limits are always joined by the AND operator with all the other qualifications.
If you plan to perform data qualifications on MDX property data, you can support mapping MicroStrategy date forms to MDX property data of the date data type. For information on how to support these date forms and qualifications, see Supporting MDX Cube Source Date Data in MicroStrategy.
See the following to learn more about filtering options for MDX cubes: