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 document/dashboard applying selections as filters or slices

Applying selections as filters or slices In a Microstrategy Document the selections a user makes in a selector can either filter or slice the data in the target: Filtering means that the data for the current selection is calculated only when it is requested by the user. The selections are used to filter the underlying dataset before the metric values are aggregated at the level of the Grid/Graph that is displayed in the document. If the source attribute is not included in the Grid/Graph, the metric values from all the selected elements are aggregated and shown at the level specified in the Grid/Graph. All metric condition selectors (which filter metric values or ranks) and selectors that target other selectors filter data by default. You cannot change them to slicing selectors. Slicing means that the data for each available item in the selector is calculated in advance when the document is first displayed. Selections made while ...

Command Manager Scripts in Microstrategy to create a user

Command Manager Scripts in Microstrategy to create a user and add to a group CREATE USER "LDAPID" FULLNAME "FirstName LastName" NTLINK "\DOMAIN\LDAPID" PASSWORD "123456" ALLOWCHANGEPWD TRUE ALLOWSTDAUTH TRUE CHANGEPWD FALSE PASSWORDEXP NEVER; ADD USER "LDAPID" TO GROUP "Project Name";

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...

Microstrategy Authentication Using the URL API

Microstrategy Authentication Using the URL API Users have to be authenticated before accessing functionality in MicroStrategy Web. Using the URL API, there are three ways for MicroStrategy Web to obtain the information needed to authenticate a user. Opening the login page to gather user for credentials Bypassing the login page by providing credentials in the URL Bypassing the login page by providing the session state in the URL A detailed explanation of each method for obtaining the authentication information is provided below. Opening the login page to gather user for credentials If the URL attempts to access a MicroStrategy Web page that requires login and no credentials or session state are provided in the URL, the user is redirected to the login page. If login is successful, the user is redirected to the specified page. The sample URL shown below executes a report without providing authenticating information. Since the Repo...

MicroStrategy VLDB properties with Hive

Recommended VLDB Properties for use of MicroStrategy 9 with Hive 0.7x The recommended VLDB optimizations for Hive 0.7x are listed below. These values are set by default when the "Hive 0.7x" database object is used (set at Configuration Managers > Database Instances > Database Instance > Database connection type ) Selected Default VLDB Properties for Hive 0.7x VLDB Category VLDB Property Setting Value Tables Fallback Table Type Permanent Table Tables Maximum SQL Passes Before FallBack 0 (no threshold) Tables Maximum Tables in FROM Clause Before FallBack 0 (no threshold) Tables Drop Temp Table Method Drop after final pass Tables Table Creation Type Implicit Table Query Optimizations Sub Query Type Use Temporary Table, falling back to IN (SELECT COL) for cor...

Email Subscription in Microstrategy

Create Email Subscription in Microstrategy Creates an email subscription. Do not include any leading or trailing spaces in the ANSWER parameters. This causes a SQL error and prevents the command from executing. Ex: CREATE EMAILSUBSCRIPTION "New Multi Users" FOR OWNER "administrator" SCHEDULE "Books Closed" CONTACTGROUP "TEST" CONTENT "Electronics Revenue by Region" IN FOLDER "\Public Objects\REPORTS\SUBJECT Areas\Sales and Profitability Analysis" IN PROJECT "MicroStrategy Tutorial" DELIVERYFORMAT HTML EXPIRATIONDATE NEVER EXPRIED FILENAME "file_name" SUBJECT "Test REPORT" MESSAGE "Please Test"; CREATE EMAILSUBSCRIPTION [ subscription_name ] [FOR OWNER login_name ] SCHEDULE schedule_name (ADDRESS address_name | USER user_name | CONTACT contact_name [ADDRESS contact_ address_name ] | CONTACTGROUP contact_group_name ) CONTENT ( report_or_document_name IN FOLDER loc...

Custom formatting Microstrategy metric format into 1M 2M etc

Custom formatting metric values of 1,100,000 into a 1.1 million 1.1M type format In addition to the the pre-defined options for metric formatting, MicroStrategy supports custom formatting. The MicroStrategy Tutorial project is used to explain how users can customize numbers from "1,000,000" to a "1.00" format. Consider a report containing row data values greater than a million, as illustrated below: To format these metric values to use a decimal (i.e., 1.1) instead of showing all the numerals, right-click on the metric (' Revenue ' , for this example) and select Formatting > Revenue Values , as shown below: Select " Custom " as a category in the Number tab and enter ' 0,,.## ' (without quotation marks), as shown below: Confirm that the format applied properly:

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

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy FiscalWeek Returns the numeric position of a week within a fiscal year, for a given input date. This function is useful in financial reporting when the start of the fiscal year is different than the start of the calendar year. Syntax FiscalWeek< firstWeekDay , firstMonth >( Date / Time ) Where: • Date / Time is the input date or timestamp. • firstWeekDay (default value is 1) is a parameter that determines which day of the week is considered as the first day of the week. You can type an integer value from 1 to 7, with 1 representing Sunday, 2 representing Monday, and so on until 7 representing Saturday. • firstMonth (default value is 1) is a parameter that determines which month is considered as the start of the fiscal year. You can type an integer value from 1 to 12, with 1 representing January, 2 representing February, and so on until ...

Prompt-in-prompt (nested prompt) in a FreeForm SQL Report in MicroStrategy

Prompt-in-prompt (nested prompt) feature in a FreeForm SQL Report in MicroStrategy The following procedure describes how to achieve prompt-in-prompt in a Freeform SQL report in MicroStrategy Tutorial project: Create a new filter, select Add an Attribute qualification and choose the highest level attribute Country. Make sure to Qualify On: Elements. Click Prompt as the image shown below. Accept all the default values without any changes in the popped up window after clicking on "Prompt" as shown below. Save the filter as "Country Filter". Click "Prompt", choose "Use a filter to reduce the number of elements" option and select Country Filter created in last step, as shown below. Save the filter as "Region Filter". Select Filter definition prompt -> Choose from an attribute element list as shown below. Choose attribute Call Center and use the Region Filter created in the previous st...

Microstrategy Analytics

Search This Blog