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, 2017KB 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

MicroStrategy Developer Preferences options are expanded so big that some options are being cutoff. Show the hidden objects in the  Microstrategy  developer MicroStrategy Developer Preferences options are expanded so big that some options are being cut off. The steps below given in the MSTR article may not work. This can be simple handled by using the steps below:  In the Microstrategy Developer go to Tools -> Preferences (Not my prefernces :) ) Under Developer category -> select Browsing on the browsing tab you see all the options like below: 3. Now using the mouse place the cursor on text box of 10000 which is next to 'Maximum number of monitoring objects displayed per page. 4. Then Hit Tab on Keyboard and hit another Tab on keyboard 5. Then press the space or down arrow on keyboard and click on OK or Enter. That will show the hidden objects in the Microstrategy developer   Normal Version ...

System Manager workflow to execute on a schedule

Creating a System Manager workflow to execute on a schedule System Manager workflow can execute on a schedule or after an event has been triggered. This can be accomplished by creating a simple batch file, and scheduling that batch file to execute with a third-party tool like Microsoft Task Scheduler.   Note : To avoid user permission conflicts, the following steps must be performed with highest privileges.   In the below example, the workflow makes the i-server restarts every day.   1. The user must first have a valid workflow. This particular workflow is a template that is delivered out-of-the-box with System Manager.   2. Save the workflow in  .smw  format.   3. In a text editor (such as Notepad), enter the command line statement that the task scheduler should execute.     MASysMgr.exe -w C:\filename.smw” “UserName=User1 “Password=1234”   4. Save the file in  .bat  ...

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...

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Export a Report Services document to Excel with formatting using URL API

Export a Report Services document to Excel with formatting using URL API in MSTR Web In order to export a document in excel format using the URL API, the executionMode must be set to 4.  If excutionMode is not provided in the URL, by default PDF will be used as executionMode.   Below are the list of parameters that the URL must contain in order to execute correctly.   evt= 3069 src= Main.aspx.3069 executionMode= 4 documentID= 7E1644CA424F482DA811569FCE8127FF( Replace the document Id with your document ID)   Sample URL for .NET environment: http://WebServerName/MicroStrategy/asp/Main.aspx?evt=3069&src=Main.aspx. 3069 &executionMode= 4 &documentID= 7E1644CA424F482DA811569FCE8127FF    

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. {...

Optimizing queries in Microstrategy using VLDB properties

Optimizing queries in  Microstrategy using VLDB properties #vldb #vldbproperties The table b elow summarizes the Query Optimizations VLDB properties. Additional details about each property, including examples where necessary, are provided in the sections following the table. Property Description Possible Values Default Value Additional Final Pass Option Determines whether the Engine calculates...

Control the display of null and zero metric values

Show   Control the display of null and zero metric values in a grid report You can determine how to display or hide rows and columns in a grid report that consist only of null or zero metric values. You can have MicroStrategy hide the rows and columns in the following ways: Hide rows and columns that consist only of null metric values Hide rows and columns that consist only of zero metric values Hide rows and columns that consist only of null or zero metric values (default) Once you have defined how MicroStrategy hides null and zero metric values in the grid, you can quickly show or hide the grid using the Hide Nulls/Zeros option in the Data menu, as described below, or by clicking the  Hide Nulls/Zeros  icon  in the Data toolbar. To determine how null and zero metric values are displayed or hidden in a grid report Open the report in Edit mode. From the  Tools  menu, select  Report Options . The Report Options...

Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy

Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy MicroStrategy has introduced a feature known as, Incremental Refresh Options, which allow Intelligent Cubes to be updated based on one or more attributes, by setting up incremental refresh settings to update the Intelligent Cube with only new data. This can reduce the time and system resources necessary to update the Intelligent Cube periodically versus a full republish. For example, if a user has an Intelligent Cube that contains weekly sales data, the user may want this Intelligent Cube to be updated at the end of every week with the sales data for that week. By setting up incremental refresh settings, he can make it so that only data for one week is added to the Intelligent Cube, without affecting the existing data and without having to reload all existing data. Users can select t...