Creating a Microcharts widget in Microstrategy

Creating a Microcharts widget in MSTR

The Microcharts widget consists of one or more microcharts, which are compact representations of data that allow analysts to quickly visualize trends in data.

Microcharts convey information in such a way that the user can, at a glance, determine the trend of a metric over time or how a metric is performing compared to forecasted figures. The Microcharts widget is useful for this purpose because individual microcharts can display attribute and metric data in a small graph that would otherwise be displayed as a single value in a grid report cell.

The Microcharts widget can be used when an analyst needs to quickly visualize the trend of a metric at a glance without having to know many additional details. The bar, sparkline, and bullet microcharts used in the Microcharts widget convey information that an analyst can understand just by looking at the graph once.

You can view these rows of microcharts in several ways:

As a scrolling ticker that moves horizontally
As scrolling rows that move vertically

The number of rows in the widget represents the number of elements from the first attribute on the rows of the Grid/Graph that contains the widget. For example, the widget above has seven rows of regional data because the Region attribute on the Grid/Graph's rows has seven different elements, or regions.

To create and add a Microcharts widget to a document

Open the document in Design or Editable Mode.
From the Insert menu, point to Widgets, and then select Microcharts.

Click the location on your document in which to place the widget. You cannot place the widget in the Detail section of a document.
The Grid/Graph, which looks like a standard grid container, is displayed. A small icon is displayed at the bottom right of the Grid/Graph, identifying the type of widget you added to the document.
If required, resize the widget by clicking and dragging its handles.

Add objects to the Grid/Graph that contains the widget

From the Dataset Objects panel on the left, select attributes, and drag them on top of the widget. The steps below ensure that the widget is prepared to display all three microcharts (bar, sparkline, and bullet); however, this procedure also contains information to display or hide any of the microcharts.

If KPI List mode will not be used, place at least two attributes on the Grid/Graph’s rows.

The last (right-most) attribute on the rows determines the X-axis values in the bar microcharts and in the sparkline microcharts in the widget.
The remainder of the attributes on the rows (the first, second, third, fourth, and so on), determine the total number of rows displayed in the widget. The elements from those attributes become individual rows in the widget.

If KPI List mode will be used:

Only one attribute can be included on the rows if the widget will be used with KPI List mode enabled in Grid mode or Vertical Scroll mode.
Use a time-based attribute such as Month since the attribute controls the time series of the bar charts and of the sparklines in the widget. If only one attribute is included on the rows, KPI List mode is enabled automatically and the widget cannot be used except in KPI List mode.

Place at least seven metrics on the Grid/Graph’s columns.

The first (left-most) metric on the columns determines the height of the bars in the bar microcharts and the peak points in the sparkline microcharts.
The second metric creates the horizontal reference lines that are displayed in the sparkline microcharts.
The third metric determines the length of the performance measure bar in the bullet microcharts. The bar represents the actual metric value.
The fourth metric determines the maximum possible values in the bullet microcharts.
The fifth metric determines the right-most boundary of the first color band, Band 1, in the bullet microcharts.
The sixth metric determines the right-most boundary of the second color band, Band 2, in the bullet microcharts.
The seventh metric determines the value of the vertical reference line in the bullet microcharts, which is typically the target value for the metric.
Any additional metrics are displayed in the columns of the widget, after the microcharts and their associated metrics.

Enable the widget to be displayed in Flash Mode

From the Tools menu, select Document Properties. The Properties dialog box opens. Select the Flash check box under Run Modes. For more information about Flash mode, see Viewing documents in Flash Mode.
Click OK to apply the changes and return to the document.

Comments

Order of tables appear in the SQL generated by the MicroStrategy SQL Generation Engine

Order of tables appear in the SQL generated by the MicroStrategy SQL Generation Engine By default, the MicroStrategy SQL Generation Engine orders the tables in the following way( FMRL ): Fact Tables Metric Qualification (MQ) Tables Relationship Tables Lookup Tables

HyperIntelligence Training Videos

HyperIntelligence Training Videos Design and build hyper cards Optimizing Datasets for HyperIntelligence Using the HyperIntelligence for Office Outlook Add-In Building HyperIntelligence Cards Using HyperIntelligence for Mobile on Android Deploying HyperIntelligence for Outlook Insights On-The-Go: HyperIntelligence for Mobile Building HyperIntelligence Profile Cards Designing Custom HyperIntelligence Cards Using the Calendar with HyperIntelligence for Mobile

Customers Who Live in the Same City as Call Centers

Customers Who Live in the Same City as Call Centers Your new utility company has call centers located throughout the country, and your recent surveys indicate that customers who live in the same city as a call center are particularly satisfied with service due to extremely rapid repairs during power outages. To begin your new advertising campaign, you want to generate a list of Call Centers that coincide with Customer Cities. The following steps create an attribute-to-attribute qualification filter that generates the list of desired cities. To Create an Attribute-To-Attribute Qualification that Compares the Call Center and Customer City Attributes In MicroStrategy Web, log in to a project. Open any folder page (for example, click Shared Folders on the home page). Click the Create Filter icon . From the Object browser on the left, select the Customer City attribute from the Customers hierarchy and drag it to the filter pane on the right. Change Qualify...

Administration standards to optimize network data transfer speeds

Optimization standards to help developers work with the System Administrator to optimize network data transfer speeds: Place all server components in the same segment to minimize latency between the Intelligence Server, Web server, data warehouse server, and metadata server Expand bandwidth and minimize latency between servers and clients to ensure that bottlenecks do not occur when data is requested over your network Use HTTP compression between the Web servers and Web clients to achieve maximum throughput between these components Configure a Web proxy server to handle caching and reduce the load on the Web server

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

Derived metric based on attribute values

Derived metric based on attribute values Here is how could create and display data correctly on using below simple steps. Create a report with Category, Subcategory and Revenue. Create New Metric in a report or VI. Case((Category@ID = 1), Revenue, 0) Booksand Name it as Revenue for where 2 is Category ID for "Books" Report will display result as below. Result for new metric is blank. Now to fix this create a new Derived metric on Category attribute first with formula as Max(Category) {~ } and calling Books Now Edit the "Revenue for Books metric and Replace Category@ID with this new Books metric formula would looks like this Case((Books = 1), Revenue, 0). Report result would now display as expected as 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 . ...

Create an alert-based subscription in MicroStrategy Distribution Services

Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief steps bel...

Bursting file subscriptions Microstartegy

Bursting file subscriptions: Delivering parts of reports across multiple files: Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis). Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region. As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Ele...

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

Microstrategy Analytics

Search This Blog