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

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

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

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

Display a report in different view modes through URL API in MicroStrategy Web

The URL parameter report view mode in Microstartegy visMode - the mode in which the document is displayed, e.g. 2 for Interactive reportviewmode  determines how reports are displayed in the view mode, e. g. 1 for grid mode. &reportViewMode=1 (grid) &reportViewMode=2 (graph) & reportViewMode=3 (grid/graph)  &visMode=0 (no visualization) &visMode=51 (AJAX visualization)  <--- this and Flash (50) require that you setup a Custom Visualization in the report definition.&visMode=50 (Flash visualization). M ake sure those modes are enabled in Document Properties. Other parameters in the URL API Webserver - name or IP address of the webserver  Evt - event/action to be performed, e.g. 2048001 for running a document  Src - web page component to perform the event  documentID - document object ID to be executed  The parameter to pass an answer to an element list prompt:  elementsPromptAnswers=AttrID;AttrID:E...

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A  cache is a result set that is stored on a system to improve response time in future requests.  With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the  Administration  menu, point to  Projects , and then select  Project Configuration . The Project Configuration Editor opens. 3 Expand  Caching , expand  Auxiliary Caches , then select  Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the  Administration  menu in Developer, point to  Server , and then select  Purge Server Object Caches . 4 Click  Purge Now . To purge web cache follow the steps in the link ...

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

Transaction Services - Configure Transactions

Configure Transactions in MSTR Web Transaction Services-enabled document displayed on an iPhone, iPad, or Android device can allow users to insert/update/delete data in to the database, using the options in the Configure Transactions Editor. To do so, you must link a Transaction Services report to a grid or to text fields in a panel stack. If the document is being displayed on an iOS device, you can link the report to the cells of a transaction table. Data from the input objects defined in the Transaction Services report is displayed in the grid, text fields, or cells for users to edit. Prerequisites:        Ø   You must have the Web Configure Transaction privilege assigned by MSTR user admin. Ø   Create the Transaction Services report (usually a grid report) you want to link to the grid, text fields, or transaction table cells. Make sure that the Transaction Services report must contain the input object for each value you w...

Types of filters in Microstrategy

Types of filters in Microstrategy Below are the types of filters: 1. Attribute qualification filter These types of qualifications restrict data related to attributes on the report. a) Attribute form qualification Filters data related to a business attribute’s form(s), such as ID or description. •  For example, the attribute Customer has the forms ID, First Name, Last Name, Address, and Birth Date. An attribute form qualification might filter on the form Last Name, the operator Begins With, and the letter H. The results show a list of customers whose last names start with the letter H. b) Attribute element list qualification Filters data related to a business attribute’s elements, such as New York, Washington, and San Francisco, which are elements of the attribute City. • For example, the attribute Customer has the elements John Smith, Jane Doe, William Hill, and so on. An attribute element list qualification can filter data to display only those customer...

Time-based and event-based schedules

Time-based and event-based schedules executed in a clustered MicroStrategy A  schedule  is a MicroStrategy object that contains information specifying when a task is to be executed. Schedules are stored at the project source level, and are available to all projects within the project source. MicroStrategy Intelligence Server supports two kinds of schedules: Time-triggered schedules execute at a specific date and time, or at a specific recurring date and time. These schedules execute based on the time on the machine where they were created. Event-triggered schedules execute when the event associated with them is triggered. Both types of schedules can be used to schedule reports and documents, called subscriptions, or to schedule administrative tasks like delete all history list, idle project, etc. Execution of Time-Based Schedules in a MicroStrategy Intelligence Server Cluster: In a 9.x MicroStrategy Intelligence Server clustered environment, subscriptions...