Dimension Extract

A dimension can be extracted from a Jedox In-Memory DB (OLAP) database using the dimension extract. The extract creates a tree.

Dimensions can be filtered for the following items:

  • Elements
  • Consolidations (i.e., hierarchical relations between elements)
  • Consolidation factors
  • Element types (numeric / string)
  • Attributes
  • Formats and styles for dimension elements

Settings

Connection Connection to Jedox In-Memory DB
Dimension A dimension from the selected database
Read attributes
none No attributes are extracted.
standardAttributes Attributes are extracted. If several languages are defined in the database, only values of the default language are extracted.
includeLanguages Attributes are extracted for all languages of the database. The attribute names in the dimension extract are in the form "<attributeName>@<languageName>" (e.g. "Description@de_DE")
includeStyles Same as standardAttributes, but including formats and styles of dimension elements
includeLanguageStyles Same as includeLanguages, but including formats and styles of dimension

Query Filter on Dimensions

A query filter on the dimension allows filtering according to the name of elements and the hierarchy. The values are filled dynamically, depending on the selected filter type, operator, and mode. These filtering options are described below.

Filter type

Filter type: various filter lines to the same input column are evaluated like a rule chain with the filter types "accept" and "deny". If only accept-filters are used, this behaves like a logical OR.

Operator

Here you can define the logical operator between the filtering lines. This is only relevant if there are several filter lines with different input columns. Any column can be filtered with the following operators. The values for each expression depend on the operator used; specific values are noted when necessary in the descriptions below.


equal Only the specified elements are filtered. Filter behavior depends on the type of data:
  • String: the filter must be exactly equal to the source value.
  • Decimal number (floating or double): the filter value must be the most minimal representation of the value. For example, if the source value is 1.0, the filter value must be 1. If the source value is 1.5000, then the filter value must be 1.5.
  • Non-decimal number (int or long): the filter value must be exactly the same as the number.
  • Boolean (true/false): the filter must be "true" or "false" as appropriate.
inAlpharange Alphanumerical values in a particular range are filtered. Example: [A100,D200]. The short GIF below shows how this functionality works with dates.

inRange Numerical values in a particular range are filtered. Example: [1000,2000]

Other examples:
  • “[100,200]” - inclusive range: 100, 101.....199, 200
  • “(100,200)” - exclusive range: 101, 102, ... 198, 199
  • “[100,]” - inclusive half-open interval: numbers greater or equal to 100
  • “[,100)” - exclusive half-open interval: numbers lower than 100
isEmpty Empty values (blank, space, or multiple space values). For this operator, the Value field should be left blank.
like Filters the dimension elements according to regular expressions. This operator is case-sensitive. You can change that by using the (?i) modifier at the start of a regular expression.

After using the regular expression, the data preview must look like in the example below:
subset Filters the dimension elements based on any stored global Subsets for the dimension. The extract can filter from Subsets with one or more defined filter criteria or variables:

Filtering from a stored Subset

Select the stored Subset from the "Edit Subset" dialog:

If the Subset uses variables, you must select them manually by adding as many rows as there are defined variables within the "Edit Subset" dialog.

Filtering with an Integrator variable

For more dynamic design, you can replace the value of the Subset variable with an Integrator variable, as shown in the screenshot below:

Note: the value " has to be escaped as \"

Value

The element you want to filter for in the source data (optional).

Mode

Defines a hierarchical filter for the dimension. If not set, the default mode "onlyNodes" is applied, returning only the filtered elements independently of the hierarchy. In case of a global Subset filter, a mode is in general not reasonable.

Mode Example Tree view
rootToBases Selected value: Austria

Based on the selected element, this element and the elements above and below are filtered.
rootToNodes (to top element and the nodes above) Selected value: Basic Sports Equipment

All parents and their respective parents are filtered, including the selected elements.
rootToConsolidates Selected value: Basic Sports Equipment

Only consolidated elements above the selected element are filtered.
nodesToBases Selected value: Austria

All bases under this value are filtered, including the parent element.
onlyChildren Selected value: East

Only the children are filtered based on the element selected.
onlyBases Selected value: East

After filtering the elements according to any of the operators, takes all base elements underneath them. Consolidated elements are not included.

From the cube, only cells where ALL elements are base elements are returned. If you would filter all dimensions with mode "onlyBases" setting, "Base elements only" has no longer an effect. But here it removes cells from the result that are on consolidated elements for other dimensions.

In the example on the right, the filter value "East" passes the operator, and the returned elements are the base elements.
onlyNodes Only the selected element is filtered (nodal point).
onlyRoots Selected value: Austria

Only the element from the highest level of the hierarchy is filtered based on the selected element.

Updated April 23, 2025