-
Cube name — Logical name of the cube to use in queries.
-
Display name — Localizable name of the cube. If you do not specify this, the user interface instead displays the logical name.
-
Description — (Optional) Comments to add to the cube class definition. Each line is saved as a separate comment line at the start of the class definition.
-
Caption— (Optional) Specify the caption to display in the Analyzer and other utilities when working with this cube.
-
Domain— (Optional) Specify the name of the domain to contain the localized strings of this cube. You might find it convenient to use a single domain for all your cubes; in other cases, it might be appropriate to have a separate domain for each cube. See Performing Localization.
-
Source class — Complete package and class name of the base class for this cube.
-
Null replacement string — (Optional) Specifies the string (for example, None) to use as the member name if the source data for a level is null.
This option can overridden for levels, by a level option of the same name.
-
Default listing — (Optional) Logical name of the default listing for this cube. This listing must be defined in the cube.
-
Resource — (Optional) Specify the resource that secures the cube.
For information on how this is used, see Setting Up Security.
-
Owner — (Optional) Specify the owner of the cube. Specify an InterSystems IRIS® data platform username.
-
Count measure name — (Optional) Specify an alternative name for the Count measure. The default is %COUNT. It is useful to rename the Count measure if you create a compound cube; see Advanced Modeling for InterSystems Business Intelligence.
-
Count measure caption — (Optional) Specify an alternative caption for the Count measure. The default is COUNT.
-
Initial build order — (Optional) Specifies an optional ORDER BY clause for use when building the entire cube; does not affect cube synchronization or incremental updates. Specify a comma-separated list of fields in the source table. You can use the SQL keywords ASC and DESC. For example: Age DESC,Gender
For the implications of this option, see Controlling the Fact Order.
-
Build restriction — (Optional) Specifies an optional WHERE clause to use when building or updating the cube; this causes the cube to use a subset of the records. Specify an SQL comparison expression that uses fields in the source table. For example: Gender='F'
This option has no effect if the cube is based on a data connector.
For an alternative option, see Restricting the Records Used in the Cube.
-
Depends On — (Optional) Specifies the class or classes that must be runnable before this class can be compiled. This option controls how the Architect sets the DependsOn compiler keyword.
By default, when a cube is created, the system automatically sets the DependsOn keyword equal to the name of the source class for the cube. In some cases (for example with cube relationships), you might need to specify an additional class.
If you need to specify this option, specify a comma-separated list of classes and specify the full package and class name for each class in the list. Your list should include the source class for the cube.
For information on relationships between cubes, see Advanced Modeling for InterSystems Business Intelligence.
-
Allow SQL Restrict — (Optional) Selecting this check box enables you to use the %SQLRESTRICT dimension for a cube. This option enables you to define an SQL restriction in the slicer of an MDX query by adding a SQL SELECT statement or WHERE clause. Selecting this option also enables the SQL Restriction field in the Pivot Options menu of the Analyzer. For more information on using the %SQLRESTRICT dimension, see %FILTER Clause.
