Strategy ONE
Modifying Third-Party Cube Sources in MicroStrategy: MDX
The table below summarizes the MultiDimensional Expression (MDX) related VLDB properties. These properties apply only to MDX cube reports using data from an MDX cube. MDX cubes are also referred to as MDX cube sources. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase, and IBM Cognos TM1. Additional details about each property, including examples where necessary, are provided in the sections following the table.
In the table below, the default values for each VLDB property are the general defaults that can be applied most broadly for the set of certified MDX cube sources. Certain VLDB properties use different default settings depending on which MDX cube source you are using. To determine all default VLDB property settings for the MDX cube source you are reporting on, follow the steps provided in Default VLDB Settings for Specific Data Sources.
| Property | Description | Possible Values | Default Value |
|
Defines the date format used in your MDX cube source. This ensures the date data is integrated into MicroStrategy correctly. |
User-defined |
DD.MM.YYYY |
|
|
Determines how MDX cube reports that only include attributes are processed in order to improve performance in certain scenarios. |
Do not add a fake measure to an attribute-only MDX report Add a fake measure to an attribute-only MDX report |
Add a fake measure to an attribute-only MDX report |
|
|
Determines whether or not data is returned from rows that have null values. |
Do not add the non-empty keyword in the MDX select clause Add the non-empty keyword in the MDX select clause only if there are metrics on the report Always add the non-empty keyword in the MDX select clause |
Add the non-empty keyword in the MDX select clause only if there are metrics on the report |
|
|
Defines whether the metric values in MicroStrategy MDX cube reports inherit their value formatting from an MDX cube source. |
MDX metric values are formatted per column MDX metric values are formatted per cell |
MDX metric values are formatted per column |
|
|
Determines how null values are identified if you use the Modifying Third-Party Cube Sources in MicroStrategy: MDX VLDB property to ignore null values coming from MDX cube sources. |
Only include the affected hierarchy in the "has measure values" set definition Include all template hierarchies in the "has measure values" set definition |
Only include the affected hierarchy in the "has measure values" set definition |
|
|
Determines whether level (from the bottom of the hierarchy up) or generation (from the top of the hierarchy down) should be used to populate the report results. |
Use actual level number Use generation number to calculate level number |
Use actual level number |
|
|
Allows you to specify what measure values are defined as NULL values, which can help to support how your SAP environment handles non-calculated measures. |
User-defined |
X |
|
|
Determines how null values from an MDX cube source are ignored using the non-empty keyword when attributes from different hierarchies (dimensions) are included on the same MDX cube report. |
No non-empty optimization Non-empty optimization, use default measure Non-empty optimization, use first measure on template Non-empty optimization, use all measures on template |
No non-empty optimization |
|
|
Defines how the name of the measure dimension is determined for an MDX cube source. |
Do not remember the name of the measure dimension Remember the name of the measure dimension Read the name of the measure dimension from the "Name of Measure Dimension" VLDB setting |
Do not remember the name of the measure dimension |
|
|
Determines whether TopCount is used in place of Rank and Order to support certain MicroStrategy features such as metric filter qualifications. |
Do not use TopCount in the place of Rank and Order Use TopCount instead of Rank and Order |
Use TopCount instead of Rank and Order |
|
|
Determines how date qualifications are processed for MDX cube sources. |
Do not treat a date qualification on a key form as a date qualification on an ID form: Treat a date qualification on a key form as a date qualification on an ID form |
Treat a date qualification on a key form as a date qualification on an ID form |
|
|
Supports an MDX cube reporting scenario in which filters are created on attribute ID forms and metrics. |
Do not verify the level of literals in limit or filter expressions Verify the level of literals in limit or filter expressions |
Do not verify the level of literals in limit or filter expressions |
|
|
Defines the name of the measures dimension in an MDX cube source. |
User-defined |
[Measures] |
|
| MDX Query Result Rows | Determines the maximum number of rows that each MDX query can return against MSAS and Essbase for a hierarchical attribute. | User-defined | -1 |
