Configuring dimensions

For each available dimension, you can configure whether to allow refinement by the dimension values, and whether to allow cascading of the dimension.

If a dimension is hierarchical, then when the dimension value is used for refinement, the Chart component is displayed using the values from the next level in the hierarchy. For example, for the Wine Type dimension, if a user clicks the Red dimension value on the chart, the next level of values under Red - Bordeaux, Merlot, Pinot Noir, etc. - are displayed.

If the dimension allows cascading, then when the data is refined so that only one dimension value is displayed, the chart can be updated to use a different dimension.

When there are no more dimensions to cascade to, the chart remains on the last dimension in the cascade.

For example, a chart by default displays sales totals grouped by country. The Country group dimension is configured to cascade to State and then to Supplier. With this configuration:
  1. When users refine the data to only show records for the United States, the chart displays sales totals grouped by state (within the United States).
  2. If users then refine the data to only show records for California, the chart displays sales totals grouped by supplier (within California).
  3. If users then refine the data by a specific supplier, the chart displays a single value for the selected supplier, and the cascade stops.
Important:
Some behaviors to be aware of when dealing with refinement and cascades:
  • As a general rule, if the dimension is not available in the Guided Navigation component, then in the Chart component, the dimension cannot be used for hierarchical refinement, and is skipped in a cascade.
  • For multi-or or multi-and dimensions, where users can refine by more than one value, then if the data is refined by any one of the dimension values, then the cascade continues to the next dimension, even if there are still available values to refine by.
  • For dimensions based on managed attributes, whether the dimension can be used in a cascade is based on precedence rules and other settings in the Oracle Endeca Server. See the Oracle Endeca Server Developer's Guide for more information. These rules may cause a managed attribute in a cascade to be skipped unexpectedly, even if it is at the top of the cascade.

To configure a dimension:

  1. On the Chart Configuration tab, click the edit icon for the selected dimension.
  2. To allow users to refine the data using the dimension values, check the Enable drilldown refinement on this value checkbox.

    If the checkbox is checked, then when end users click a data point (such as a bar or pie wedge), a category axis label, or a legend entry on the chart, the selected data source is refined to only include records with that dimension value.

    Note that end users can only use the dimension for refinement if it corresponds to a field in the physical data. If the dimension is derived from or aliased from a physical field, then end users cannot use it for refinement.

  3. To allow the dimension to cascade, check the Enable dimension cascade for drill hierarchies checkbox.

    The cascade configuration is displayed. The dimension is automatically at the top of the cascade. A drop-down list is displayed for you to select the next dimension in the cascade.


    Group dimension configuration dialog with cascade enabled
  4. If you are allowing the dimension to cascade:
    1. To add a new layer to the cascade, select the dimension for that layer from the drop-down list, then click Add Layer.

      The new layer is added to the end of the cascade.


      Group dimension dialog showing a layer added to the cascade
    2. To remove a layer from the cascade, click the delete icon next to that layer.
    3. To clear the entire cascade, click Clear Cascade.
  5. To save the dimension configuration, click Apply.