Skip to main content Skip to complementary content

INxTreeDimensionDef Interface

Namespace: Qlik.Engine
Assembly: Qlik.Engine.dll

Syntax

[ValueClass]
public interface INxTreeDimensionDef : IAbstractStructure

Properties

Name Description
AttributeDimensions

List of attribute dimensions.

JSON property name: qAttributeDimensions

AttributeExpressions

List of attribute expressions.

JSON property name: qAttributeExpressions

CalcCondition

Specifies a calculation condition object.

If CalcCondition.Cond is not fulfilled, the dimension is excluded from the calculation and CalcCondition.Msg is evaluated.

By default, there is no calculation condition.

This property is optional.

JSON property name: qCalcCondition

Def

Refers to a dimension.

JSON property name: qDef

LibraryId

Refers to a dimension stored in the library.

JSON property name: qLibraryId

NullSuppression

If set to true, no null values are returned.

JSON property name: qNullSuppression

OtherLabel

This property is used when some dimension limits are set.

Label of the Others group. The default label is Others .

Example:

"qOtherLabel":"= <label>"

or

"qOtherLabel":{"qExpr":"= <label>"}

Where:

* < label > is the label of the Others group.

JSON property name: qOtherLabel

OtherTotalSpec

Sets the dimension limits. Each dimension of a hypercube is configured separately.

Defines if some values (grouped as Others ) should be grouped together in the visualization.

For example in a pie chart all values lower than 200 could be grouped together.

JSON property name: qOtherTotalSpec

ShowAll

If set to true, all dimension values are shown.

JSON property name: qShowAll

TotalLabel

If this property is set, the total of the calculated values is returned.

The default label is Total .

Example:

"qTotalLabel":"= <label>"

or

"qTotalLabel":{"qExpr":"= <label>"}

Where:

* < label > is the label of the Total group.

JSON property name: qTotalLabel

ValueExprs

List of measures.

JSON property name: qValueExprs

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!