Model a dynamic cube
- A measure dimension that contains at least one measure
- At least one dimension
- At least one hierarchy and associated levels defined for each dimension
- Mappings between the measure and the dimensions
- Attributes that reference table columns either directly, by expressions, or by an expression that is a constant value
When modeling a dynamic cube, the relationship between a measure and a dimension must be defined for each dimension in the cube. This relationship is defined by a measure-to-dimension join. For more information, see Defining a measure-to-dimension join.
| Property | Description |
|---|---|
| Name | The name of the dynamic cube. This is also used as the name of the data source that represents the cube. If the project supports multiple locales, there can be versions of the name in all supported languages. Tip: When creating a Framework
Manager package for the dynamic cube, select this name from the list
of data sources.
|
| Comment | A comment or description of the dynamic cube. Comments are not visible in the IBM Cognos studios. |
| Remove non-existent tuples | True (default) - remove tuples from the cross join set that cannot contain any data. False - do not remove tuples from the cross join set. Applies when a dimension has multiple hierarchies and a report contains the cross join of two or more of those hierarchies. With this feature enabled, only those tuples for which data may exist are retained from the cross join, improving report efficiency. A cross join of hierarchies from the same dimension may contain tuples for which no data can possibly exist. For example, in a Time dimension with two hierarchies, the cross join of [2011 Q1] and [2011 Aug] would be removed since [2011 Q1] and [2011 Aug] do not share a common month. |