Skip to main content

<property>

Defines optional properties for a level in a Business Intelligence cube.

Details

A level may contain zero or more custom level properties. These are properties whose value is derived from the source data and is associated with a specific member of a level. For example, the city level could include properties such as population or ZIP code. For each city, there would be one value of each of these properties.

The <property> element has the following contents:

Attribute Purpose
name, displayName, description, disabled See Common Attributes in a Cube.
sourceProperty, sourceExpression Specify one of these attributes in almost the same way that you would specify Property or Expression in the Architect; see Specifying the Source Values for a Dimension or Level and Details for Source Expressions. Notes:
  • For sourceProperty, use the same value you would enter for Property, enclosed within single quotes.

    For example: sourceProperty='MyProp'

  • For sourceExpression, use the same value you would enter for Expression, enclosed within single quotes.

    For example: sourceExpression='%source.MyProp_"ABC"'

You can enclose the value in double quotes instead if the value itself does not contain any double quotes. For example: sourceExpression="%source.MyProp"
sort (Optional) Specifies how to use this property to sort members of the level that contains this property. You can sort a level by multiple properties; if you do, the sorting is applied in the order in which you define the <property> elements; the first property controls the primary sort, the second property controls the secondary sort, and so on.

Specify "asc", "asc numeric", "desc", or "desc numeric"

By default, the property does not affect the sort order of the members.

isName (Optional) If "true", this attribute specifies that, for a given level member, the system should use the value of this property to specify the names of that member.

Specify either "true" or "false" (the default).

isDescription (Optional) If "true", this attribute specifies that, for a given member, the system should use the value of this property as the tooltip for the member. Specify either "true" or "false" (the default).
isReference (Optional) If "true", this attribute specifies that the system should not store the property value, but should instead define the property as an SQL computed field that refers to the original source tables. If you specify isReference="true", the level must be defined so that the member keys are the IDs of the records on which the level (and its properties) are based.
useDisplayValue (Optional) For class properties that have values for the DISPLAYLIST and VALUELIST parameters, this attribute specifies which value to use for the property. If this attribute is "true" (the default), the system uses the value given by DISPLAYLIST; if this attribute is "false", the system uses the value given by VALUELIST.
linkClass, linkProperty (Optional) See Linking to Another Table.
factName (Optional) Name used (in the generated dimension table) for the column that corresponds to this property. If this attribute is null, the system generates a name. You do not need to worry about this unless you plan to issue SQL queries directly against the generated dimension table.

Despite the name of this attribute, properties are not contained in the fact table. They are contained in the table that corresponds to the level to which the property belongs.

See the comments for factName for <measure>.

formatString (Optional) Controls how the values are displayed. See formatString Details. In the format string, you can also use the special character 0, which serves as a placeholder for leading zeros. For example, 00000 would show a five-digit number padded with leading zeros.
hidden (Optional) If hidden="true" then the property is defined and can be used in queries, but is not listed as an available property in the Analyzer.

Example

For example:

<property name="Population" sourceProperty="City.Population"/>

Intrinsic Properties

For each level, the system also automatically defines a set of intrinsic properties. These are listed in the InterSystems MDX Reference.

FeedbackOpens in a new tab