Skip to main content

Hierarchy Reporting with Ragged Hierarchies

KB300417: New feature in MicroStrategy 10.4 Secure Enterprise Platform: Hierarchy Reporting



Hierarchy Reporting is a new feature introduced in MicroStrategy 10.4 Secure Enterprise Platform. This technical note explains the supported configurations, required changes in MicroStrategy Web preferences, a Hierarchical Attribute and its creation steps, and general features of Hierarchy Reporting.
Mar 30, 2017•KB Article
Content
SUMMARY:
Hierarchy Reporting is a new feature introduced in MicroStrategy 10.4 Secure Enterprise Platform. This technical note explains the supported configurations, required changes in MicroStrategy Web preferences, a Hierarchical Attribute and its creation steps, and general features of Hierarchy Reporting.

WHAT IS HIERARCHY REPORTING?
Unbalanced hierarchies(also known as ragged hierarchies) are hierarchies with branches that descend to inconsistent levels. For example, in an Employee hierarchy, different parts of the organizational structure will have more management levels than others. 
Many organizations have aspects of their business that are organized in unbalanced hierarchies. Besides the Employee hierarchy, other typical examples include a chart of accounts, complex product portfolios, and multinational geographic groupings. 
Hierarchy Reports are a class of reports in which the data is naturally organized and presented in a hierarchical structure. Hierarchy Reporting features treat hierarchies as a first-class citizen, and make interacting with entire hierarchies intuitive and efficient. Both balanced and unbalanced hierarchies may be represented in a hierarchy report, although unbalanced hierarchies benefit the most from Hierarchy Reporting features.

SUPPORTED DATA SOURCE AND INTERFACES
In MicroStrategy 10.4 Secure Enterprise Platform, the following data sources are supported for Hierarchy Reporting. See the Readme for the exact database versions supported.
  • Microsoft Analysis Services
  • Oracle Essbase
Hierarchy Reporting features are currently supported only in Dashboard (Visual Insight). Normal reports, Report Services documents, and Mobile are not supported in version 10.4.

WEB PREFERENCE
Hierarchy Reporting is released as a Preview feature in MicroStrategy 10.4 Secure Enterprise Platform. When MicroStrategy is installed, Hierarchy Reporting will be disabled by default. To enable Hierarchy Reporting, implement the following steps:
  1. Log into MicroStrategy Web as an administrator.
  2. On the upper right of any page, click on the user name, and then select Preferences from the drop-down list.
  3. By default, the General preferences at the User Preferences level page is displayed. On this page, go to the Features for Customer Feedbacksection. For the Financial Reporting feature, change the feature status to “On” as shown below.
    1.jpg
    1.jpg
  4. At the bottom of the page, click on Apply

HIERARCHICAL ATTRIBUTE
In order to facilitate the building of hierarchy reports, 1MicroStrategy Secure Enterprise Platform 10.4 introduces a new type of attribute: the hierarchical attribute. The hierarchical attribute represents an entire hierarchy and all its levels. For example, you may have a Time hierarchical attribute that represents the Time hierarchy, including its levels Year, Quarter, Month, and Day. In contrast, a normal attribute usually represents a single level of a hierarchy (e.g., Year). The hierarchical attribute can be placed on a grid, filtered, and sorted, much like a normal attribute.

CREATING HIERARCHICAL ATTRIBUTES WITH DATA IMPORT
To create a hierarchy report, the first step is to perform a Data Import and connect to an OLAP data source. There are two ways to initiate the Data Import:
1) Create a standalone Intelligent Cube
The Intelligent Cube can be used to create dashboards at a later time. To import data into an Intelligent Cube, click on the Create button in the upper left of any page, and select Add External Data.
2) In Visual Insight Dashboard, import data
Data can be imported from within a dashboard. Create a new dashboard by clicking on the Create button in the upper left of any page, and select New Dashboard. In the dashboard toolbar, click the arrow next to the Add Dataset icon
2.jpg
2.jpg
, then select External Data. 

Once Data Import is initiated, take the following steps to create hierarchical attributes:
  1. In the 'Connect to Your Data' page, click OLAP. The 'Import From Cubes' page opens.
  2. From the MDX Connections panel on the left, select the name of the data source connection that contains the data to import. The cube catalog is displayed in the Browse Catalog panel.
  3. Click on the arrow to the left of the cube catalog to see a list of the cubes in the selected data source.
  4. To add a cube to import, click and drag the name of the cube from the Browse Catalog panel to the Editor panel on the right of the page. The cube name is displayed in the Editor panel.
  5. Below the Editor panel, select the option to Import hierarchy as hierarchical attribute.
  6. Click Finish.

Using Hierarchical Attributes in a Visual Insight Dashboard
When a Visual Insight dashboard is linked to a dataset, the hierarchical attributes are listed in the Datasets Panel. Hierarchical attributes will be denoted with the
3.jpg
3.jpg
icon. To use a hierarchical attribute in a visualization, simply drag-and-drop the desired hierarchical attribute into the main panel.
To search for the desired hierarchical attribute, use the Search box at the top of the Datasets Panel.
When the hierarchical attribute is first placed on a grid, the hierarchy will be displayed with its element tree collapsed. Elements can be expanded and collapsed by clicking on the + (expand) or – (collapse) button next to the element.
4.jpg
4.jpg



NAVIGATION SHORTCUTS
Every level of the entire hierarchy can be expanded or collapsed by using the Expand/Collapse All Levels shortcut.
  1. Hover over the row or column header to reveal an arrow on the right side of the header. Click on the arrow.
  2. Select Expand All Levels or Collapse All Levels.

A similar shortcut is available for each element as well, in order to expand every level of a branch.
  1. Right click on an element of a hierarchy.
  2. Select Expand All Lower Levels.

SORTING
When a report with a hierarchical attribute is sorted, the structure of the hierarchy will remain intact, so every element will retain its parent in the hierarchy tree. Each level of the hierarchy will be sorted separately from the other levels.
To sort on a hierarchy or a metric, hover over the row or column header to reveal an arrow on the right side of the header. Click on the arrow. The sorting options available are:
  • Sort Ascending
  • Sort Descending
  • Advanced Sort

The Advanced Sort dialog will allow users to:
  • sort on multiple hierarchical attributes or metrics
  • sort on alternative attribute forms, such as ID or Description

FILTERING
To filter the data in a dashboard sheet, drag a hierarchical attribute into the Filter Panel. The Filter Panel will display the elements of the hierarchy in a tree. Select or deselect elements to filter the data.

FILTER SELECTION SHORTCUTS
Groups of elements can be selected or deselected with the use of shortcut buttons. There are two types of shortcuts: branch selection, and level selection.
Users may want to see all elements of a hierarchy branch. For example, if users want to see the Year 2015 along with all Quarters and Months of 2015. To select or deselect all elements of a branch in the Filter Panel, hover over an element to reveal the branch selection shortcut
6.jpg
6.jpg
to the right of the element. Click on the branch selection shortcut.
Users may also want to see only the elements of a particular level of the hierarchy. For example, a user may want to see data at the Year level for every Year, but not data at the Quarter or Month levels. The level selection shortcut is a row of buttons above the hierarchy. 
5.jpg
5.jpg

To select or deselect all elements of a level, click on the button corresponding to the hierarchy level. Clicking on the All button will select or deselect all elements.

APPLYING MULTIPLE FILTER CHANGES ALL AT ONCE
By default, each time a change to the filter is made, the data in the sheet will be immediately refreshed. If the sheet contains large amounts of data, it may be helpful to apply a number of filter changes all at once. In order to be able to make a number of changes to the filter before applying it, click on the arrow at the top right of the Filter Panel, and de-select the Auto-apply Filters option. An Apply button will appear at the top of the Filter Panel.
For more information on the Visual Insight Dashboard Filter Panel, see Creating filters for a sheet of data.

VISUAL INSIGHT DASHBOARD FEATURES NOT SUPPORTED BY HIERARCHY REPORTING IN MicroStrategy Secure Enterprise Platform 10.4
The hierarchical attribute is not supported by some features in Visual Insight Dashboard. When a hierarchical attribute is in the dashboard’s dataset, the unsupported features will be disabled in the interface.
The following features are not supported by the hierarchical attribute. (For each feature, the location of the feature in the interface is listed. When there are multiple ways to perform the action, only one of the ways is documented below.)
  • Convert to Document (File > Convert to Document)
  • Download dashboard (File > Download Dashboard)
  • Adding multiple datasets (File > Add Data)
  • Replace dataset (Dataset menu > Replace Dataset With)
  • Create Group (Right click on grid element > Group)
  • Create Calculation (Right click on grid element > Calculation)
  • Alternative display styles for the Filter Panel (Filter menu > Display Style)
  • Exclude option for filtering (Filter menu > Exclude)

Comments

Popular posts from this blog

Level metrics in Microstartegy/MSTR

Level Metrics Level metrics allows the users to choose the right combination of level target, filtering, and grouping (referred to as elements) to achieve your desired results.  The elements of a metric level are described below: • Target : The target is the attribute level at which the metric calculation groups. For a more detailed description, see  Target: The context of a calculation . • Grouping : Grouping determines how the metric aggregates. For a more detailed description, see  Grouping: How aggregation is performed . • Filtering : Filtering governs how the report filter interacts with the metric calculation. For a more detailed description, see  Filtering: Interaction with report filters . The level is indicated between the curly braces ({ }) in the metric definition shown below: Sum(Revenue) {~, Product} The tilde (~) represents the report level with standard filtering, denoted by the plus sign (+). If you add item as a level, th...

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...

Apply or Pass-through functions in Microstrategy

Ap ply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various RDBMS systems.. Syntax common to Apply functions Apply Function Name   ("expression with placeholders", Arg1, Arg2, Arg3, …ArgN) where: Apply Function Name  – is a generic name used for the predefined pass-through functions described above expression with placeholders  – is the string describing the actual expression or syntax that the engine uses while generating the SQL and which is sent to the RDBMS. The placeholders are represented by #0, #1, and so on. "#" is a reserved character for MicroStrategy. Arg  – is an argument that replaces the parameter markers in the pattern. Arg1 replaces #0, Arg2 replaces #1, and so on. There are   five  pre-defined Apply functions to replace regular, predefined functions of the same type. For more details, cli...

Tableau Dataset Connector to Microstrategy REST API URL

Tableau Dataset Connector to Microstrategy REST API URL The MicroStrategy Dataset Connector is an out‑of‑the box feature that allows you to fetch data from reports or cubes that reside in MicroStrategy projects into Tableau Public (also known as Tableau Desktop). You can import datasets with up to four million rows and 30+ columns. Tableau Public 10.4 or later is needed. Open Tableau Desktop Public Edition. Under Connect, click  Web Data Connector . If it is not there, click  More > Web Data Connector . Enter the following URL: https:// <MSTR Domain> /CommunityConnectors/mstr/ If the connector does not automatically detect Tableau, add the query  ?mode=tableau  to the end of the URL and refresh your browser. Enter your API Server URL and environment credentials. Your REST API URL is your environment URL with  /MicroStrategyLibrary/  added at the end. Click  Connect Select the dataset you want to import. Select the...

Microstrategy Report Execution Process

The Report Execution Process  Report execution process at a high level: The report execution process is a three-step process:  1. Query Stage : Retrieve data from the warehouse  2. Populate and Evaluate : Fill report data required for display  3. Cross-tab : Pivot and display sorting and page-by Each of the engines plays an important part in the report execution process.  As you can imagine, the SQL Engine performs its role during the Query stage while the Query Engine and Analytical Engine can be involved in all three stages.

Microstrategy Dossiers explained

Microstrategy  Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has  evolved dashboards to the point that they are more than dashboards - they are  interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so  the've  renamed VI dashboards to  ‘ dossiers ’.  Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers   With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...

Microstrategy Removing sections that do not have metric data

Removing sections that do not have metric data This is an interesting feature which might not be explored by many of us and it comes us handy. A  cross join between datasets can result in rows or Group Header/Footer sections that do not have metric data. For example, a document contains two datasets. Dataset 1 contains Year and Revenue, with data for three years (2007-2009). Dataset 2 contains Year and Profit, filtered to return data for only two years (2008 and 2009). If you place Year and Profit in the Details and execute the document, it displays three rows, although no profit data exists for 2007. This is a product of the cross join between the two datasets. You do not want to see the blank line for 2007 since it does not give you any data for profit. You can select the  Trim sections for which no metric value data is available  check box. This removes the row for 2007, since no metric data for Profit is available for 2007. The results are shown below: ...

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...

Custom Tooltips in Microstrategy developer and Web

Custom Tooltips in Microstrategy developer and Web The following table describes the macros you can use to customize graph tooltips in both MicroStrategy Developer and MicroStrategy Web: Macro Information Displayed {&TOOLTIP} All relevant labels and values associated with a graph item. {&GROUPLABEL} Name of the graph item's category. This value is often the graph item's attribute element information, as attributes are commonly used as the categories of graph reports. {&SERIESLABEL} Name of the graph item’s series. This value is often the graph item's metric name information, as metrics are commonly used as the series of graph reports. {&VALUE} The value of a given data point. {&XVALUE} The X-value of a data point. Only applicable to Bubble charts and Scatter plots. {&YVALUE} The Y-value of a data point. Only applicable to Bubble charts and Scatter plots. {&ZVALUE} The Z-value of a data point. Only applicable to Bubble charts and Scatter plots. {...

MicroStrategy Hadoop Gateway operation modes

MicroStrategy Hadoop Gateway operation modes MicroStrategy Hadoop Gateway is a native connector which was built based on Spark 1.6.x. You can choose one or more data files from Hadoop HDFS and load them into MicroStrategy Intelligence Server. Data files can be published as either an In-Memory Cube or a Live Connect Cube. MicroStrategy Hadoop Gateway supports three operation modes : YARN client Standalone (HDP cluster does not support Standalone) Local YARN client mode: The driver runs in the client process, and the application master is only used for requesting resources from YARN. Running in this mode requires YARN service to be enabled on your Hadoop cluster. Standalone mode:  MicroStrategy Hadoop Gateway uses Spark Master to coordinate data processing. Local mode:  no application is deployed in the Spark nodes. All data processing is executed in the MicroStrategy Hadoop Gateway host. This modality is intended for testing and troubleshooting.