Skip to main content

Types of prompts in Microstrategy

Types of prompts in Microstrategy

The different types of prompts allow you to create a prompt for nearly every part of a report. Prompts can be used in many objects including reports, filters, metrics, and custom groups, but all prompts require user interaction when the report is executed.

The correct prompt type to create depends on what report objects you want users to be able to base a filter on to filter data, as described in the list below.

  • Filter definition prompts allow users to determine how the report's data is filtered, based on one of the following objects:
  • Attributes in a hierarchy: Users can select prompt answers from one or more attribute elements from one or more attributes. The attribute elements that they select are used to filter data displayed on the report. This prompt lets you give users the largest number of attribute elements to choose from when they answer the prompt to define their filtering criteria.
    For example, on a report displaying profit forecasts, if the prompt lets users select from the Product hierarchy, one user might choose to see forecasts for certain electronic products, while another user might select different electronics products, or all media products.
  • Attribute forms: Users can select prompt answers from a list of attribute elements from a single attribute. This prompt is more restrictive than the hierarchy prompt, because the user has fewer attribute elements to select answers from.
  • Attribute element lists: Users can select prompt answers from a limited list of specific attribute elements. This prompt is the most restrictive of the filter definition prompts, because the user has the fewest number of attribute elements to select answers from.
  • Metrics: Users can define a metric qualification, which determines what data should be displayed for one or more specific metrics on the report.
  • Object prompts allow users to select which objects, such as attributes, metrics, custom groups, and so on, to include in a report. Object prompts can determine the definition of either the report template or the report filter. Users can use this prompt to add more data to a report. Users can also choose from among a selection of filters, to apply a filter that is most useful for their analysis purposes.
  • Value prompts allow users to select a single value such as a date, a specific number, or a specific text string. The value chosen by the user is compared to metric or attribute element values, and thus determines the data viewed by the user. Value prompts are used in metric qualifications. 
         The different kinds of value prompts are:
  1. Date prompt: Users enter a specific date for which to see data. This prompt is used in a filter.
  2. Numeric prompt: Users enter a specific number, up to 15 digits, which is then used as part of a filter, or within a metric, to look for specific numeric data.
  3. Note: If a user enters more than 15 digits for a numeric prompt, the data is converted to scientific notation. If precision is needed beyond 15 digits, you should use a Big Decimal value prompt instead.
  4. Text prompt: Users enter a word or phrase, which is then used as part of a filter to look for specific data with that text.
  5. Big Decimal prompt: Users can enter up to 38 digits, to search for numeric data with the Big Decimal data type assigned to it.
  6. Long prompt: Users enter up to 10 digits, to search for numeric data.
  7. Prompts can also be used as part of a function expression, and value prompts are particularly suited to provide values for function arguments. 
  • Level prompts allow the user to specify the level of calculation for a metric.
  • System prompts are a special type of prompt that does not require an answer from the user. Instead, it is answered automatically by Intelligence Server. System prompts are located in the Public Objects/Prompts/System Prompts folder in MicroStrategy Developer

Comments

Post a Comment

Popular posts from this blog

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

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

Microstrategy Report Execution Process

The Report Execution Process  Report execution process at a high level: The report execution process is a three-step process:  1. Query Stage : Retrieve data from the warehouse  2. Populate and Evaluate : Fill report data required for display  3. Cross-tab : Pivot and display sorting and page-by Each of the engines plays an important part in the report execution process.  As you can imagine, the SQL Engine performs its role during the Query stage while the Query Engine and Analytical Engine can be involved in all three stages.

Types of filters in Microstrategy

Types of filters in Microstrategy Below are the types of filters: 1. Attribute qualification filter These types of qualifications restrict data related to attributes on the report. a) Attribute form qualification Filters data related to a business attribute’s form(s), such as ID or description. •  For example, the attribute Customer has the forms ID, First Name, Last Name, Address, and Birth Date. An attribute form qualification might filter on the form Last Name, the operator Begins With, and the letter H. The results show a list of customers whose last names start with the letter H. b) Attribute element list qualification Filters data related to a business attribute’s elements, such as New York, Washington, and San Francisco, which are elements of the attribute City. • For example, the attribute Customer has the elements John Smith, Jane Doe, William Hill, and so on. An attribute element list qualification can filter data to display only those customer...

Tableau Dataset Connector to Microstrategy REST API URL

Tableau Dataset Connector to Microstrategy REST API URL The MicroStrategy Dataset Connector is an out‑of‑the box feature that allows you to fetch data from reports or cubes that reside in MicroStrategy projects into Tableau Public (also known as Tableau Desktop). You can import datasets with up to four million rows and 30+ columns. Tableau Public 10.4 or later is needed. Open Tableau Desktop Public Edition. Under Connect, click  Web Data Connector . If it is not there, click  More > Web Data Connector . Enter the following URL: https:// <MSTR Domain> /CommunityConnectors/mstr/ If the connector does not automatically detect Tableau, add the query  ?mode=tableau  to the end of the URL and refresh your browser. Enter your API Server URL and environment credentials. Your REST API URL is your environment URL with  /MicroStrategyLibrary/  added at the end. Click  Connect Select the dataset you want to import. Select the...

Microstrategy Release Types and Scheduling

Microstrategy Release Types and Scheduling Organizations that use MicroStrategy have asked for a more frequent and predictable platform release schedule—and we listened! We want you to be able to adopt the latest innovations more regularly while having the ability to budget for your long-term upgrade roadmap. Recently announced by CTO Tim Lang in his newsletter, that’s why we’re adopting an annual cadence for future platform releases. This means that our upcoming platform release (v11.1) hits the streets in Q4 2018, followed by another platform release in Q4 2019. PLATFORM RELEASE Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, an...

Transaction Services - Configure Transactions

Configure Transactions in MSTR Web Transaction Services-enabled document displayed on an iPhone, iPad, or Android device can allow users to insert/update/delete data in to the database, using the options in the Configure Transactions Editor. To do so, you must link a Transaction Services report to a grid or to text fields in a panel stack. If the document is being displayed on an iOS device, you can link the report to the cells of a transaction table. Data from the input objects defined in the Transaction Services report is displayed in the grid, text fields, or cells for users to edit. Prerequisites:        Ø   You must have the Web Configure Transaction privilege assigned by MSTR user admin. Ø   Create the Transaction Services report (usually a grid report) you want to link to the grid, text fields, or transaction table cells. Make sure that the Transaction Services report must contain the input object for each value you w...

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

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...