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

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

Create a transaction services photo uploader

Create a transaction services photo uploader 1. Create a new table "photo_upload" in Tutorial warehouse database (the default location: C:\Program Files\MicroStrategy\Tutorial Reporting\TUTORIAL_DATA_7200.mdb), as shown below: 2. The 'photo_upload' table has to be pre-populated with *exactly* 10 rows of data, the values for the 'ID' column should be 1-10 and the values for the 'uploaded' column should all be 0 3. In MicroStrategy Desktop, create a freeform report "R1" based on the new table "photo_upload" in Tutorial data created at step 1, as shown below: SELECT Location, Description, ID, uploaded, numbers FROM PHOTO_UPLOAD 4. Create another table for transaction insert SQL. Make sure to create an 'autonumber' type ID as primary key for this table, or auto_increment ID for different DBs. 5. Create...

Microstrategy "Error type: Odbc error. Odbc operation attempted

"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

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

Scheduling a report or document to be sent to an FTP in MSTR

Scheduling a report or document to be sent to an FTP server You can have a report or document automatically delivered to a location on your FTP server on a specific schedule. To do so, you must subscribe to the report or document, as described in the steps below. You can customize your subscription by typing macros in the File Name , Sub-folder , or Zip File Name fields. These macros are automatically replaced with the appropriate text when the report or document is delivered. For example, you create a subscription to a document. If you type {&Project} in the File Name field, the name of the project in which the document is saved is displayed in the name of the document when it is delivered. • This procedure assumes that an administrator has already added your FTP server as a new device in Developer. Steps to do so are included in the System Administrator Help . To send a report or document to an FTP server on a schedule ...

exact string when searching for elements in an element prompt in MicroStrategy

When a user types in keywords to tries to find element names in an element prompt, the search returns all objects containing the keywords in MicroStrategy Developer 9.4.x-10.x. However, the user would like to search for the exact phrase. It is suggested to use quotes to get exact phrase when there is a space between. Like "Black Panther" Using the MicroStrategy Tutorial Project as an example, a user wishes to search for an item named Minolta Maxxum Camera. The search results for Minolta Maxxum Camera return all items containing any or all of those words, as shown below: CAUSE: This occurs due to the search defaulting to 'ORing' the search terms. This means that any or all keywords that match the strings will be returned. The SQL for this search is shown below: SELECT ITEM_NAME FROM LU_ITEM WHERE (ITEM_NAME LIKE '%Minolta%' OR ITEM_NAME LIKE '%Maxxum%' OR ITEM_NAME LIKE '%Camera%') ACTION: To match an exact string, use...

Super Cubes in MicroStrategy 2019

Super Cubes in MicroStrategy 2019 Beginning in MicroStrategy 11.0 and 2019, users will notice objects referred to as " Super Cubes ". Super Cubes are simply a renaming of what was previously referred to as MTDI (Multi Table Data Import) Cubes. Note that only the naming convention has changed, as the functionality remains the same . This name change is visible in MicroStrategy Workstation and MicroStrategy Web. In MicroStrategy Workstation, right click on any cube created via Data Import and select Properties . The object Type is listed as Super Cube: This can also be seen when editing or authoring a dossier. In your Datasets panel, hover over the name of your dataset. The tooltip will show the dataset type listed as a Super Cube.

Microstrategy Custom group and consolidation comparison

Custom group and consolidation comparison Both consolidations and custom groups provide flexibility in reports, but the objects differ in their structure and use. The essential distinction is that consolidations work with attributes and custom groups use filters. Consolidations are groupings of attribute elements while custom groups are based on filter criteria. Custom groups are used to apply different filters to different rows of a report. Consolidations are used to create virtual attributes to allow reporting on attributes that do not exist in the data model. Finally, row level math can be performed with consolidations but not with custom groups. Custom groups are more flexible than consolidations because you do not have to know much about your data to create filters for a custom group. In contrast, consolidations require that you know exactly which attribute elements to select when creating the consolidation. To continue with the examples from the previous sect...

Execute Integrity manager test from Command line

Execute Integrity manager test from Command line MSTR Integrity Manager allows the user to execute a test without having to load the GUI, or to schedule a test to run later at specific times or dates. Go over using Windows AT command at: https://support.microsoft.com/en-us/help/313565/how-to-use-the-at-command-to-schedule-tasks https://www.lifewire.com/at-command-2618090 Here are the prerequisites to execute a test from the command line: Create a test and saved using the Integrity Manager graphical interface. Make sure that the users has the ' Use Integrity Manager ' privilege for that project(provided by the administrator) and the ' Execute ' permission for the reports to be tested. Keep in mind that MicroStrategy Integrity Manager can only test three-tier projects, i.e., projects which are connected to a MicroStrategy i- Server. Projects in Direct Connection (two-tier) mode cannot be tested with this tool...

Multi-Select Drop Down Selector with Apply Button

Multi-Select Drop Down Selector with OK Button When creating a Report Services Document, you may want to create a drop down selector to save space, but also would like the drop down to be a multi-selector with OK/Apply button. Below are instructions to achieve this in a Report Services Document. Steps to Create: 1. Right click on your drop down selector and choose Properties and Formatting 2. Navigate to the Layout Tab 3. In the layout tab, click "Allow multiple selections". It will not indicate that the check box is enabled, but this step is mandatory. 3. Next, navigate to the Theme tab. Choose the L ight Theme from the drop down menu and click the Apply button. 4) Next, change the Theme back to None and click Apply. 4. When you return to the Layout tab, you will see the checkbox for Allow multiple selections is now checked.

Microstrategy Analytics

Search This Blog