Cube Extract

• excludeEmpty: empty cube cells are not returned from the extract. This corresponds to behavior in 6.0 when when option "ignore empty cells" was turned off.
• excludeEmptyAndZero: if the option "store zero values" is set for the cube, no "0" (for numerical cells) and "" (for string cells) values are returned. Otherwise the option is identical to "excludeEmpty".
• includeEmpty: the extract returns a NULL in the value column for empty cube cells.
• includeEmptyDefaultMapping: the extract returns "0" (for numerical cells) and "" (for string cells) for empty cube cells. This corresponds to behavior in Jedox 6.0 when option "ignore empty cells" was turned off.

From the cube, only cells are returned where ALL elements are base elements. 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.

If set, rule-based cell values are extracted. If the rule value has the result 0, it is extracted if "empty cells" is set to "excludeEmpty" but not if it's set to "excludeEmptyAndZero".

Rule-based cell values of numeric type are extracted, even if the Cell Types setting is set to “only_string”. Rule-based cell values of string type are extracted, even if the Cell Types setting is set to “only_numeric”.

Tip: if your data requires both numeric and string cell types, you may see improved performance by creating separate extracts for the numeric and string types, rather than one extract with both.

Note: "Equals" is case-insensitive. "Like" (see Query filter for dimensions) is case-sensitive. You can change the case-sensitivity by using a (?) modifier: https://www.regular-expressions.info/modifiers.html

After using the regular expression, the data preview must look like in the example below:

possible values:
<enumeration value="Equals" />
<enumeration value="Not equals" />
<enumeration value="Less than" />
<enumeration value="Less or equal" />
<enumeration value="Greater than" />
<enumeration value="Greater or equal" />

- Value (must be numeric value)

Example:
- Operator: "Greater than", Value: 1000
Returns all paths with cube cell values > 1000.

• The name of the column (default: Name of the dimension)
• The cube dimension

In most cases this manual definition is not necessary: by default, all cube dimensions are output columns of the Cube extract with the dimension name as column name and with the order as defined in the cube.

The manual definition offers the options of
- reordering columns
- renaming columns
- omitting some of the cube dimensions.

When a cube dimension is omitted from the output columns, the cube values are extracted on the default read element of this dimension. This default read element has to be specified for the dimension in the Modeler. Additionally, no filter condition can be applied on this dimension.

For Lucanet connections:
The blocks can be defined by so-called slicer dimensions which split the XMLA request to a series of block requests. For each element of each slicer dimension a separate XMLA request is sent.
Format: #<Dimension>,[<Dimension>,....]
As alternative, the block size can be defined by a numerical value which leads to an automated determination of suitable slicer dimensions.
Example: #Year,Company
For each year and each company, a separate XMLA request is sent.