Skip to main content

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:

 AUTOTEXTDESCRIPTION 
 {&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} Display the execution time.
 {&SERVERNAME} Display the Intelligence Server name
 {&REPORT:FILTERDETAILS} Display the filter details of that report.
 {&REPORT:PROMPTDETAILS} Display the prompt details of that report.
 {&REPORT:REPORTDETAILS} Display the report details.
 {&NOTES} Display the Report Services Document notes.
 {&Prompt1&} Display the answer of the first prompt.
 {&WEBSERVER} Display the Web server URL.
 {&TITLE} Display the Report Services Document inbox title.
 {&PROMPTXML} Display the prompt answers XML.
 {&DOCUMENTMESSAGEID} Display the message ID of the Report Services Document.
 {&REPORT:GUID} Display the GUID of that particular report.
 {&ATTRIBUTE@ELEMENTID} Display the Element ID of that attribute.
 {&ATTRIBUTE@GUID} Display the GUID of that particular attribute.

Description
Code
Sample Output
Comments
Page number
{&PAGE}
1
The current page number
Total number of pages
{&NPAGES}
12
The total number of pages in the document or in the group’s section before page numbering restarts
Date & Time
{&DATETIME}
11/15/2003 7:10:55 PM
Current date and time, of the client computer. For PDFs, this is the date and time when the PDF was generated
You can display only the date without the time, or the month name rather than the number, and so on. 
Current user
{&USER}
Jane User
The full name, not login, of the user who generates the PDF or views the document
Document name
{&DOCUMENT}
Regional Sales Summary
The name of the document as stored in the project
Document description
{&DESCRIPTION}
Revenue and profit by region
Short description of the document
Document inbox title
{&TITLE}
Regional Sales Summary for Tuesday
The name of the document instance
If you send a document to your History List, you can rename that instance of the document. This auto text code displays that name, rather than the document name stored in the project.
Document notes
{&NOTES}
User1: 8/15/2010 10:10:10 AM: Reviewed and approved
Notes (annotations) added to the document.
For background information on notes, see .
Project name
{&PROJECT}
MicroStrategy Tutorial
The name of the project in which the document is stored
Prompts
{&PROMPT1&}
{&PROMPT2&}
:
{&PROMPTn&}
South (for example, if prompt1 is for the attribute Region)
The user's answers to each prompt in the document, identified by number
If n is greater than the number of prompts in the document, the code cannot be replaced with pertinent information. Therefore the code itself is displayed in the PDF.
Prompt details
{&PROMPTDETAILS}
Prompt 1: Region prompt
Northwest, Southwest
Prompt 2: Year
Year (ID)= 2007
Details for all the prompts in the document
You can define how this auto text code is displayed 
MicroStrategy Web Server
{&WEBSERVER}
http://localhost:8080
/MicroStrategy/servlet/mstrWeb
Path to the web server being used, if the document is executed in MicroStrategy Web; otherwise, the value in project configuration
Document execution time
{&EXECUTIONTIME}
The date and time the document was executed
You can display only the date without the time, or the month name rather than the number, and so on. 
To differentiate between Date and Time and Document execution time, do the following:
1Run a document and send it to the History List.
2Each time you retrieve the document from the History List, the PDF is regenerated. The Date and Time change each time, but the Document execution time does not change.

Labels:

Comments

Post a Comment

Popular posts from this blog

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A  cache is a result set that is stored on a system to improve response time in future requests.  With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the  Administration  menu, point to  Projects , and then select  Project Configuration . The Project Configuration Editor opens. 3 Expand  Caching , expand  Auxiliary Caches , then select  Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the  Administration  menu in Developer, point to  Server , and then select  Purge Server Object Caches . 4 Click  Purge Now . To purge web cache follow the steps in the link ...
3 comments
Read more

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 . ...
3 comments
Read more

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...
3 comments
Read more

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 ...
7 comments
Read more

MicroStrategy Connection File

Creating a Connection File in Microstrategy Workstation A MicroStrategy connection file (also know as the .mstrc) is a text file that contains all of the information needed to connect Workstation to a MicroStrategy environment.  With a .mstrc file, users can simply import the file and enter their credentials, and then they will be connected to a MicroStrategy On-Premises Environment. Requisites   MicroStrategy Workstation URL for your Environment MicroStrategy Login credentials How to create the connection file With the integrated option  Connect to New Environment: Open Workstation window. Go to  Environments  located under  Manage  on the left side.   Click on the plus symbol with the label of  Connect to a New Environment .   Assign a friendly environment name. Provide the Environment URL and click  Continue . Note: If it is a default MicroStrategy installation of MicroStrategy Library, the Environment U...
2 comments
Read more

Apply or Pass-through functions in Microstrategy

Ap ply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various RDBMS systems.. Syntax common to Apply functions Apply Function Name   ("expression with placeholders", Arg1, Arg2, Arg3, …ArgN) where: Apply Function Name  – is a generic name used for the predefined pass-through functions described above expression with placeholders  – is the string describing the actual expression or syntax that the engine uses while generating the SQL and which is sent to the RDBMS. The placeholders are represented by #0, #1, and so on. "#" is a reserved character for MicroStrategy. Arg  – is an argument that replaces the parameter markers in the pattern. Arg1 replaces #0, Arg2 replaces #1, and so on. There are   five  pre-defined Apply functions to replace regular, predefined functions of the same type. For more details, cli...
6 comments
Read more

Sort by metric subtotals and attribute elements together in Microstrategy

Sort by metric subtotals and attribute elements together in Microstrategy Users may observer that when creating a report that contains advance sorting with a metric that contains subtotals the report results appear to be only sorted by the metric values specified. Even if a sort is specified for the attribute elements on the report, the results in the report appear as if the attribute sort was not defined. In the screenshot below, the results for a report are shown where the Advance Sorting option 'Sort metrics hierarchically using: Total' is selected. For this report, a second sort is defined on the Customer Gender - 'DESC' form, users would notice that the ordering of the this attribute is not consistent: The sort definition for the report is shown below: CAUSE: When the option to 'Sort metrics hierarchically using: Total' option is selected, the MicroStrategy Engine first sorts the results based on the Total values, and then sorts th...
1 comment
Read more

Custom Tooltips in Microstrategy developer and Web

Custom Tooltips in Microstrategy developer and Web The following table describes the macros you can use to customize graph tooltips in both MicroStrategy Developer and MicroStrategy Web: Macro Information Displayed {&TOOLTIP} All relevant labels and values associated with a graph item. {&GROUPLABEL} Name of the graph item's category. This value is often the graph item's attribute element information, as attributes are commonly used as the categories of graph reports. {&SERIESLABEL} Name of the graph item’s series. This value is often the graph item's metric name information, as metrics are commonly used as the series of graph reports. {&VALUE} The value of a given data point. {&XVALUE} The X-value of a data point. Only applicable to Bubble charts and Scatter plots. {&YVALUE} The Y-value of a data point. Only applicable to Bubble charts and Scatter plots. {&ZVALUE} The Z-value of a data point. Only applicable to Bubble charts and Scatter plots. {...
2 comments
Read more

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...
3 comments
Read more

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...
2 comments
Read more