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

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

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

Differences between OLAP cubes and Super cubes

Differences between OLAP cubes and Super cubes OLAP Super Version Existed before MicroStrategy 10.0 New in MicroStrategy 10.0 Data Volume In 9.x, limited to 2 billion rows Each partition can have up to 2 billion rows ...

Retrieve a list of user groups and the associated users in MicroStrategy Developer 9.x / 10.x

Retrieve a list of user groups and the associated users in MicroStrategy Developer Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9.x, select 'Project Documentation' from the Tools menu to start the wizard. Select any project that is in the project source that contains the users and groups and click Next. Select only Configuration Objects for documentation. Uncheck the 'Basic Properties' object category from the next screen, as shown below: Then select only 'User Group' under the Configuration Objects section and only 'Groups' and 'Members' under the Definition section, as shown below: Go through the rest of the wizard, and open the resulting documentation. After navigating down to the User Groups, the documentation should look similar to the following image: This page shows every group, any child groups, and all members of each group.

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

Non Aggregate metrics Beginning lookup, Ending lookup, Beginning fact., Ending fact

Non Aggregate metrics Beginning lookup, Ending lookup, Beginning fact ., Ending fact A nonaggregatable metric, such as an inventory metric, is one that should not be aggregated across an attribute. For example, if you have monthly inventory numbers in your data warehouse and want to calculate the yearly inventory, adding the monthly numbers together does not provide a useful business measure. Instead, you may want to use the end-on-hand and beginning-on-hand inventory numbers to see how the total inventory changed during the year. The following options are available: • To use the first value in the lookup table, select Beginning lookup . • To use the last value in the lookup table, select Ending lookup . • To use the first value in the fact table, select Beginning fact . • To use the last value in the fact table, select Ending fact .

Microstrategy Document Autotext macros:

Autotext code/macros in Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard: AUTOTEXT DESCRIPTION {&PAGE} Display the current page. {&NPAGES} Display the total number of pages. {&DATETIME} Display the current date and time. {&USER} Display the user name that is executing the Report Services Document. {&DOCUMENT} Display the document name. {&DOCUMENTID} Display the document ID. {&DESCRIPTION} Display the document description. {&PROJECT} Display the project name. {&EXECUTIONTIME} Dis...

Metric values are repeated across rows when a report is executed in MicroStrategy

Metric values are repeated across rows when a report is executed in MicroStrategy When comparing report results between DB Query Tool and MicroStrategy, some reports show repeated metric values in MicroStrategy where there were none in DB Query Tool. To illustrate the issue, a fact table CAT_ITEM_SLS has been added into the MicroStrategy Tutorial project and populated with a small set of three rows. CAT_ID ITEM_ID REVENUE 1 1 10 1 2 20 2 2 30 Report results in DB Query Tool: Report results in MicroStrategy: In MicroStrategy, the row for "Art As Experience" in the Spring 2007 catalog repeats the $20 value from the Winter 2007 catalog, where DB Query Tool shows the $30 value from the fact table. CAUSE The discrepancy occurs because the attribute elements for Catalog and Item are in a many-to-many relationship, but the attribute relationship in the MicroStrategy schema is defined incorrectly w...

Microstrategy Analytics

Search This Blog