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

mstrio – Python and R wrappers for the MicroStrategy

mstrio – Python and R wrappers for the MicroStrategy REST APIs Connecting to MicroStrategy Create a connection to the Intelligence Server using Connection() and  connect() in Python and R, respectively. Required arguments for the   Connection()  function are the URL for the MicroStrategy REST API server, MicroStrategy Intelligence Server username and password, as well as the MicroStrategy project name. By default, the  connect()  function anticipates your MicroStrategy Intelligence Server username and password. LDAP authentication is also supported. Use the optional argument  login_mode=16  in the  connect()  function for LDAP authentication. Extract data from cubes and reports To extract data from MicroStrategy cubes and reports, use the get_cube()  and  get_report() functions. Use...

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

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

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

HyperIntelligence and its Architecture

HyperIntelligence and its Architecture When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. This feature is similar to what we see in web pages particularly stock related web sites. MicroStrategy introduced HyperCards, a new object that is built, managed, and deployed using MicroStrategy Workstation(Not by using Developer or Desktop as far as I know). Cards can be consumed in a web browser via the MicroStrategy HyperIntelligence Chrome extension and on iOS devices via the MicroStrategy HyperMobile app. This feature can help the users to inject Zero-Click Intelligence (as it requires the users to hover only and no need to click!) about customers, products, people, and more directly onto words within websites or web application or emails. This feature can display the conte...

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

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

Create a Visualization Filter in a Dossier

Create a Visualization Filter You can select attribute values to filter data that appears in a visualization by creating an attribute filter. Create a visualization filter by dragging attributes and metrics from the Datasets panel. To create an attribute filter Open the dossier you want to modify. Select the chapter that contains the visualization to filter. Click Filter . An empty filter appears in the dossier. Drag the attributes and metrics for filtering from the Datasets panel to the empty filter. Use the Ctrl key to select multiple attributes and metrics. In the filter, click Select Target . Click on target visualizations or visualization filters to select them. You can select targets across chapters and pages, as long as they are all on the same page. Click Apply . Click More in the filter and select options for modifying the filter. The available options are based on the objects you select.

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

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 Analytics

Search This Blog