Microstrategy Document Editor Sections Important Notes:

The Layout area is in the center of the Document Editor interface and provides the framework for precisely controlling where controls (such as text fields, grid and graph reports, images, and widgets) are displayed when the document is viewed in different display modes, printed, exported, emailed, and so on.

To add data to the document, drag objects from the Dataset Objects panel and drop them into the Layout area. Controls are rendered differently depending on what section they are placed in, as described below:

Page Header: The control is displayed at the top of each page in the document. By default, if a document contains multiple layouts, the same Page Header is displayed for all layouts in the document. You can change this setting so that each layout has a separate Page Header.
Document Header: The control is displayed once at the beginning of the document, immediately below the Page Header section. Any data fields placed in the Document Header are calculated using all of the data in the document. The Document Header can be used for grand totals and document information, such as the name and execution time. If a document contains multiple layouts, the Document Header is replaced by the Layout Header, described below.
Layout Header: The control is displayed once at the beginning of the layout, immediately below the Page Header section. Any data fields placed in the Layout Header are calculated using all of the data in the layout. For example, a metric in the Layout Header displays as a grand total. If a document contains only a single layout, the Layout Header is replaced by the Document Header, described above.
Group Header: In Design Mode, this type of section is displayed as Group Header, where Group is replaced by the name of the report object used to group data in the document (for example, Region). There is a corresponding Header and Footer for each group in the Grouping Panel . You can place controls in the Grouping Headers to display information about groups in the document, such as the name of the group element (such as Northeast or Southwest) or group totals. The order of the Group Header sections corresponds to the order of the items in the Grouping panel.
Detail Header: The control is displayed immediately before the Detail section and after the Document, Layout, and Header sections (if applicable). The Detail Header is commonly used to display column headings above their corresponding data fields in the Detail section.
Detail: One row containing the control is displayed for each row of data in the document's dataset. The Detail section typically provides the most detailed or granular information in the document; the Detail section is also where most of the attributes, metrics, and main content are placed. You can place a Grid/Graph anywhere in a document except in the Detail section.
Detail Footer: The control is displayed immediately following the Detail section. The Detail Footer section is often used to display totals.
Group Footer: In Design Mode, this type of section is displayed as Group Footer, where Group is replaced by the name of the report object used to group data in the document (for example, Region). There is a corresponding Header and Footer for each group in the Grouping Panel. Group Footers are often used to display totals at the group level. The order of the Group Footer sections corresponds to the order of the items in the Grouping panel.
Layout Footer: The control is displayed once at the end of the layout, immediately above the Page Footer section. Any data fields placed in the Layout Footer are calculated using all of the data in the layout. It can be used to display closing notes, a conclusion, or a summary. If a document contains only a single layout, the Layout Footer is replaced by the Document Footer, described below.
Document Footer: The control is displayed once at the end of the document, immediately above the Page Footer section. This section is often used to display information such as closing notes, a conclusion, or a summary. Any data fields placed in the Document Footer are calculated using all of the data in the document. If a document contains multiple layouts, the Document Footer is replaced by the Layout Footer, described above.
Page Footer: The control is displayed at the bottom of each page in the document. This section is often used to display the page number, or the date and time. By default, if a document contains multiple layouts, the Page Footers are shared for all layouts in the document. You can change this setting so that each layout has a separate Page Footer.

You can display the Group Header, Detail Header, Detail, Detail Footer, and Group Footer sections horizontally across the page, instead of vertically.

The Layout area provides an alignment grid to help you control the placement and alignment of controls. You can change the density of the grid by defining the Alignment grid density in the Report Services preferences in the User Preferences.

Note: If your layout expands past the width of a single page, a dotted line is displayed to show the page break.

Example of a grid report displayed in the Layout area

More details from MSTR: https://doc-archives.microstrategy.com/producthelp/10.6/DocCreationGuide/WebHelp/Lang_1033/Content/DocumentCreationGuide/Understanding_and_working_with_document_sections.htm

Comments

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

URL API connection mode parameters

URL API connection mode parameters When using the URL API, to denote which type of Authentication to use, developers can use the connMode parameter. The following values are used for this parameter: Standard = 1 LDAP Authentication = 16 Database Authentication = 32 Guest = 8 Windows Authentication = 2 Trusted Authentication = 64 Integrated Authentication = 128

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

HTML image as a button that exports a grid on a document to Excel in MicroStrategy

HTML Image as a Button That Exports a Grid on a Document to Excel in MicroStrategy In MicroStrategy Web, it is possible to use an image as a button to export a grid on a document to Excel in MicroStrategy version 10.4 and later. This document provides the steps to accomplish the same. The goal is to create an image link that is used to export the grid, like shown below: Document in Edit Mode Follow the steps below: 1. Create a Report Services Document 2. Make two grids with different attributes and metrics in each 3. Insert an HTML container (and not an image) and insert the script below. Make sure the Project name matches the given project and gridKey matches ( highlighted in bold in the script below). The code below is used for the first grid and button. Main things to watch are the gridKey values and the name of the element id which in the below code is exportLink . <a target="_blank" id="exportLink" href=""...

Level metrics in Microstartegy/MSTR

Level Metrics Level metrics allows the users to choose the right combination of level target, filtering, and grouping (referred to as elements) to achieve your desired results. The elements of a metric level are described below: • Target : The target is the attribute level at which the metric calculation groups. For a more detailed description, see Target: The context of a calculation . • Grouping : Grouping determines how the metric aggregates. For a more detailed description, see Grouping: How aggregation is performed . • Filtering : Filtering governs how the report filter interacts with the metric calculation. For a more detailed description, see Filtering: Interaction with report filters . The level is indicated between the curly braces ({ }) in the metric definition shown below: Sum(Revenue) {~, Product} The tilde (~) represents the report level with standard filtering, denoted by the plus sign (+). If you add item as a level, th...

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

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

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

MicroStrategy Hadoop Gateway operation modes

MicroStrategy Hadoop Gateway operation modes MicroStrategy Hadoop Gateway is a native connector which was built based on Spark 1.6.x. You can choose one or more data files from Hadoop HDFS and load them into MicroStrategy Intelligence Server. Data files can be published as either an In-Memory Cube or a Live Connect Cube. MicroStrategy Hadoop Gateway supports three operation modes : YARN client Standalone (HDP cluster does not support Standalone) Local YARN client mode: The driver runs in the client process, and the application master is only used for requesting resources from YARN. Running in this mode requires YARN service to be enabled on your Hadoop cluster. Standalone mode: MicroStrategy Hadoop Gateway uses Spark Master to coordinate data processing. Local mode: no application is deployed in the Spark nodes. All data processing is executed in the MicroStrategy Hadoop Gateway host. This modality is intended for testing and troubleshooting.

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

Microstrategy Analytics

Search This Blog