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 perform transf
Microstrategy Release Types Platform release Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, and regular hotfix cadence addresses critical defects. Feature Release Interval:  Quarterly every three (3) months Who:  Customers with specific feature requirements. What:  New functionality developed in close collaboration with customers and customer council. Expectation:  Customer has chosen feature path, will consume further feature releases. Support:  Six (6) months patch support for approved P1 defects and (eighteen) 18 months troubleshooting. Customers upgrade to next feature release for roll-up fixes. Why has MicroStrategy introduced “Platform” and “Feature

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 two types of objects for the incremental fetch: a report or

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 want to allow users to change.  Ø   Ma

Sending an email in MSTR where the results of a report are in the email body as HTML content and a different report/document is an attachment to the same email in MicroStrategy

Is it possible to send an email using Distribution Services where the results of a report are in the email body as HTML content and a different report/document in MSTR? ANSWER: It is currently not possible to send an email using Distribution Services where the results of a report are in the email body as HTML content and a different report/document is an attachment to the same email in MicroStrategy 9.x. An enhancement request has been logged for this feature. ACTION: Contact Microstrategy Technical Support for an update on the enhancement, I have contacted but nobody knows where the request is  

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 dialog box opens. To determine how

Multi-Table Data Import(MTDI) from one or more supported data sources

Multi-Table Data Import(MTDI) from one or more supported data sources In MicroStrategy Analytics Enterprise Web 10 onewards, users can now simultaneously import two or more tables from one or more supported data sources, this feature is called Multi-Table Data Import (MTDI) which has been renamed as Super Cubes in MSTR 2019 (Does it sound like multisourcing for all the users without admin help?) Currently, all connectors in MicroStrategy Web 10 except " OLAP " and " Search Engine Indices " support Multi-Table Data Import. Users are able to add multiple tables/files when doing data import from single connector, as shown below: Users are also able to combine multiple tables/files from different sources and store them into one single Intelligent Cube, as shown below:

Stop a Report Services Document subscription from sending if no data is returned in MicroStrategy Web

Trick to Stop a Report Services Document subscription from sending if no data is returned in MicroStrategy Web The following steps are for stopping a Report Services Document subscription from sending if no data is returned: In MicroStrategy Web, edit or execute a report. Right-click on the metric header to apply the condition or threshold and select " Alerts ". Specify the condition " Is Not Null " to the metric for the delivery to be triggered in the filter editor as shown below. Expand the "Delivery Settings" section. Specify the desired delivery options including recipient address, subscription name, delivery format, compression options and the schedule to run the report and check the condition.  The subscription will be sent on the defined schedule only when data is returned in the Report Services Document.

Personalizing file locations, email and file subscriptions using macros in Microstrategy

Personalizing file locations MSTr allows to dynamically specify the  File Location  and  Backup File Location  in a file device using macros.  For example, if you specify the  File Location  as  C:\Reports\{&RecipientName}\ ,  all subscriptions using that file device are delivered to subfolders of  C:\Reports\ . Subscribed reports or documents for each recipient are delivered to a subfolder with that recipient’s name, such as  C:\Reports\Jane Smith\  or  C:\Reports\Hiro Protagonist\ . The table below lists the macros that can be used in the  File Location  and  Backup File Location  fields in a file device: Description Macro Date on which the subscription is sent {&Date} Time at which the subscription is sent {&Time} Name of the recipient {&RecipientName} User ID (32-character GUID) of the recipient {&RecipientID} Distribution Services address that the subscription is delivered to {&AddressName} File path that a

MicroStrategy default sort order for an attribute elements browsing

MicroStrategy default sort order for an attribute elements browsing and display How does MicroStrategy 9.x resolve the default sort order for an attribute when different sort orders are defined for different forms? Consider the following cases: CASE 1 A new attribute is created with three forms, all with sort order set to none. Form Name Form Type Default Sort Order ID ID None DESC DESC None LongDesc None None The overall sort order is evaluated and stored in the attribute definition when the attribute is saved. With all form sort orders set to none there is no saved sort order, MicroStrategy defaults to sort ascending by ID. CASE 2 The same attribute is modified so the forms are now: Form Name Form Type Default Sort Order ID ID None DESC DESC Descending LongDesc None Ascending Now when the attribute is saved, MicroStrategy goes through each form in the order they appear in the main 'Forms' window of the attribute editor. The first