The decorations editor is used to add information to the metadata coming from the underlying back-end databases. Decorations are added before metadata is further processed. The benefits of using decorations include improved performance, easier and better data overview and additional information not available in the database.

When clicking Manage decorations a dialog box will open to display a list of all database connections on the left and a list of properties on the right.


Each database connection in the left panel may be expanded to display available cubes and each cube may be expanded to display its dimensions and measures.

The available properties will vary according to which level of the hierarchy you have selected. You can work on any of these levels: Database connections, cubes and dimensions/measures.

Changes to the properties of an element overrides any values of the property specified elsewhere in TARGIT Management client (e.g. on the database connection definition itself) and any values specified on higher levels in the hierarchy.

The screenshot below displays the properties for the connection string created for one of the Demo Data cubes.


In this table, you can read about each property setting:



Criteria request: Include calculated members

This property makes it possible to specify if calculated members should be included in a request for possible criteria values. Any changes overrides the default specified in the option in Setup | Back-end.

Criteria request: Selected measures

By default all measures in a cube are included in the criteria requests made from dimensions on the criteria bar. Sometimes it may be convenient to select specifically which measures should be included to reduce the number of members shown in the criteria bar. With this property the measures to include in criteria requests may be selected specifically. Note that selecting measures specifically overrides any values set for the property 'Criteria request: Include calculated members'.

Dynamic dates definition

This property makes it possible to define dynamic dates dimension level names in a way that is usable for the database backend. E.g. in a tabular model, a hierarchical time dimension may be defined in a way that requires redefinition here. It is necessary to know what the unique names for each dimension level in the dimension are (e.g. in SSAS) to make the definitions. When selecting an appropriate hierarchy and clicking this field, a dialog with three tabs opens: Dynamic time definition, Offset and table lookup and Level type overrides. For further documentation on dynamic dates, see the appropriate chapter in this manual.

Include in Sentinel search

When searching for Sentinels all cubes and measures are included in the search by default. This property makes it possible to specify for each database, cube and measure whether it should be included in the search.

Non empty criteria

This property ensures that dimensions on the criteria bar are filtered to only display members where data exist for one or more measures in the measure groups the dimension is associated with.

Non empty queries

This property filters dimension members with empty results from the data set.

Use subcubes

A subcube is a subset of a cube based on the criteria applied to the data set. The use of subcubes will in most cases result in a performance increase. Disabling subcubes may have an impact on totals and subtotals no longer adding up correctly. 

Use DrillDownMember...

Setting this property to 'Yes' may have a positive impact on query response times in objects with many dimension members - but it should be used with care. Enabling this  property will result in a number of limitations. For each dimension, on any axis, all of these requirements must be met:

  • Dimensions must be single attribute hierarchies
  • All members must be present in dimension
  • Drilldown will not work
  • Cannot be a User Dimension
  • Criteria on hierarchy is only permitted if subcubes are enabled as well
  • Multidimensional subtotals must be disabled

DrillDownMember optimization is just another way of querying the Analysis Server for data when you have a crosstab with several hierarchies per axis. The requirements listed are only used by the server when determining to actually use DrillDownMember(). If these requirements are not met, it will fall back to querying "the old way".

Prevent criteria Auto-filter

This property makes it possible to prevent a dimension to be included in an auto-filter request in the criteria bar. This is convenient for some calculated dimensions that causes auto-filter requests to take long time.

Search-only in criteria bar

Prevents fetching members automatically when opening a dimension field in the criteria bar.

Visual totals

This property makes it possible to enable (default) or disable measure totals when criteria are applied.

Note: This setting will only have an effect if Subcubes (connection property) is disabled.

Oracle Warehouse Builder caption column

By default the dimension captions presented in TARGIT are based on the key values in the Oracle Warehouse Builder. To change this to another value (e.g. Name value) write the name of the value in this field. After any change the cubes must be processed by right-clicking the connection and select 'Process Cubes'.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.