Académique Documents
Professionnel Documents
Culture Documents
Course Guide
Version: RPTESS-941-Mar14-CG
U.S. Government Restricted Rights. It is acknowledged that the Course and Software were developed at private
expense, that no part is public domain, and that the Course and Software are Commercial Computer Software and/or
Commmercial Computer Software Documentation provided with RESTRICTED RIGHTS under Federal Acquisition
Regulations and agency supplements to them. Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFAR 252.227-7013 et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer SoftwareRestricted Rights
at FAR 52.227-19, as applicable. The Contractor is MicroStrategy, 1850 Towers Crescent Plaza, Tysons Corner, Virginia
22182. Rights are reserved under copyright laws of the United States with respect to unpublished portions of the
Software.
Trademark Information
Application Development, MicroStrategy Intelligent Cubes, The Foundation For Intelligent E-Business, The Integrated
Business Intelligence Platform Built For The Enterprise, The Platform For Intelligent E-Business, The Scalable
Business Intelligence Platform Built For The Internet, Office Intelligence, MicroStrategy Office, MicroStrategy Report
Services, MicroStrategy Web MMT, MicroStrategy Web Services, Pixel Perfect, Pixel-Perfect, MicroStrategy Mobile,
MicroStrategy Integrity Manager and MicroStrategy Data Mining Services are all registered trademarks or trademarks
of MicroStrategy Incorporated.
All other company and product names may be trademarks of the respective companies with which they are associated.
Specifications subject to change without notice. MicroStrategy is not responsible for errors or omissions.
MicroStrategy makes no warranties or commitments concerning the availability of future products or versions that
may be planned or under development.
Patent Information
This product is patented. One or more of the following patents may apply to the product sold herein: U.S. Patent Nos.
6,154,766, 6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033, 6,567,796, 6,587,547, 6,606,596, 6,658,093,
6,658,432, 6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,741,980, 6,765,997, 6,768,788,
6,772,137, 6,788,768, 6,798,867, 6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693,
6,885,734, 6,940,953, 6,964,012, 6,977,992, 6,996,568, 6,996,569, 7,003,512, 7,010,518, 7,016,480, 7,020,251,
7,039,165, 7,082,422, 7,113,993, 7,127,403, 7,174,349, 7,181,417, 7,194,457, 7,197,461, 7,228,303, 7,260,577, 7,266,181,
7,272,212, 7,302,639, 7,324,942, 7,330,847, 7,340,040, 7,356,758, 7,356,840, 7,415,438, 7,428,302, 7,430,562,
7,440,898, 7,486,780, 7,509,671, 7,516,181, 7,559,048, 7,574,376, 7,617,201, 7,725,811, 7,801,967, 7,836,178, 7,861,161,
7,861,253, 7,881,443, 7,925,616, 7,945,584, 7,970,782, 8,005,870, 8,051,168, 8,051,369, 8,094,788, 8,130,918,
8,296,287, 8,321,411 and 8,452,755. Other patent applications are pending.
How to Contact Us
MicroStrategy University
1850 Towers Crescent Plaza
Tysons Corner, VA 22182
Phone: 877.232.7168
Fax: 703.848.8602
E-mail: education@microstrategy.com
http://www.microstrategy.com/training-events
MicroStrategy Incorporated
1850 Towers Crescent Plaza
Tysons Corner, VA 22182
Phone: 703.848.8600
Fax: 703.848.8610
E-mail: info@microstrategy.com
http://www.microstrategy.com
TABLE OF CONTENTS
Course Description.................................................................... 13
Who Should Take This Course .............................................. 14
Follow-Up Courses ................................................................ 14
Related Certifications............................................................. 14
Course Objectives ................................................................. 15
About the Course Materials ......................................................... 16
Content Descriptions ............................................................. 16
Learning Objectives ............................................................... 16
Lessons ................................................................................. 16
Opportunities for Practice ...................................................... 17
Typographical Standards ....................................................... 17
MicroStrategy Courses .......................................................... 19
Core Courses......................................................................... 19
Advanced Courses ................................................................ 20
1. Introduction to
MicroStrategy
Business Intelligence
Table of Contents
Lesson Summary......................................................................... 35
2. Introduction to
MicroStrategy
Developer
3. Reports
4. Report Data
Manipulations
Table of Contents
5. Report Style
Manipulations
Table of Contents
6. Filters
7. Metrics
Table of Contents
8. MicroStrategy OLAP
Services
Table of Contents
9. Prompts and
Searches
10
B. MicroStrategy
Glossary
Table of Contents
11
Table of Contents
12
PREFACE
Course Description
This two-day course provides an overview of reporting, using MicroStrategy
Developer. The topics covered in this course include:
13
Preface
Project Architects
Administrators
SDK Developers
Follow-Up Courses
After taking this course, you might consider taking the following courses:
Related Certifications
To validate your proficiency in the content of this course, you might consider
taking the following certifications:
Preface
Course Objectives
After completing this course, you will be able to:
Define the components that comprise a report and create simple reports
using Developer. (Page 60)
Define the different types of style manipulations available and perform these
style manipulations using Developer. (Page 158)
Define the different types of report filters available in Developer and create
each type using the Filter Editor. (Page 210)
Define the different types of metrics, and create them using the Metric
Editor in Developer. (Page 242)
Define the different types of prompts, and explain how you can use search
objects inside prompts. Create prompts and searches in
Developer. (Page 304)
Course Objectives
15
Preface
Content Descriptions
Each major section of this course begins with a Description heading. The
Description introduces you to the content contained in that section.
Learning Objectives
Learning objectives enable you to focus on the key knowledge and skills you
should obtain by successfully completing this course. Objectives are provided
for you at the following three levels:
Lessons
Each lesson sequentially presents concepts and guides you with step-by-step
procedures. Illustrations, screen examples, bulleted text, notes, and definition
tables help you to achieve the learning objectives.
Preface
Review
Case Study
Business Scenario
Exercises
Typographical Standards
The following sections explain the font style changes, icons, and different types
of notes that you see in this course.
Actions
References to screen elements and keys that are the focus of actions are in bold
Arial font style. The following example shows this style:
Click Select Warehouse.
Code
References to code, formulas, or calculations within paragraphs are formatted
in regular Courier.New font style. The following example shows this style:
Sum(Sales)/Number of Months
17
Preface
Data Entry
References to literal data you must type in an exercise or procedure are in bold
Arial font style. References to data you type that could vary from user to user or
system to system are in bold italic Arial font style. The following example
shows this style:
Type copy c:\filename d:\foldername\filename.
Keyboard Keys
References to a keyboard key or shortcut keys are in uppercase letters in bold
Arial font style. The following example shows this style:
Press CTRL+B.
New Terms
New terms to note are in regular italic font style. These terms are defined when
they are first encountered in the course. The following example shows this
style:
The aggregation level is the level of calculation for the metric.
Precedes Exercises
Preface
MicroStrategy Courses
Core Courses
19
Preface
Advanced Courses
All courses are subject to change. Please visit the MicroStrategy website for the
latest education offerings.
1
INTRODUCTION TO
MICROSTRATEGY BUSINESS
INTELLIGENCE
Lesson Description
This lesson introduces you to the basic components of a MicroStrategy
business intelligence architecture. It also describes key MicroStrategy objects
that you will use while working with MicroStrategy Developer.
21
Lesson Objectives
After completing this lesson, you will be able to:
Describe the MicroStrategy business intelligence architecture and define basic
MicroStrategy reporting terminology.
After completing the topics in this lesson, you will be able to:
22 Lesson Objectives
23
Analysis
Metadata
Data sources
Analysis
MicroStrategy applications enable you to intuitively interact with your
business intelligence system and enable you to do everything from rapid data
discovery to predictive analytics. User-friendly and robust analysis and
analytics tools in your business intelligence system ensure your data is not lost
in the last mile.
A variety of grid and graph formats are available for superior report
presentation. You can even build documents, which enable you to combine
multiple reports with text and graphics.
In addition, you can use the MicroStrategy Software Developers Kit (SDK) to
customize the interface that users see and the functionality available to them.
In previous versions of MicroStrategy, the objects in a standard report had to
come from a single data source. MultiSource Option is an add-on component
to Intelligence Server that removes this limitation. It enables you to define a
single project schema that uses multiple data sources. As a result, you can now
create a standard report that executes SQL against multiple data sources.
more information on MultiSource Option, refer to the
For
MicroStrategy Architect: Project Design Essentials course.
MicroStrategys unified Web interface is a single code base that provides BI
functionality to all users, ranging from basic reporting functionality for novice
users, to interactive analysis functionality for analysts, to full report design
functionality for power users and IT professionals.
Because of the way it is designed, the MicroStrategy Web interface can deliver
your spur-of-the-moment visualizations or storyboarded dashboards equally
well to multiple different interfaces, including: mobile devices, Web browsers,
third-party enterprise portals, and to Microsoft Office applications like
Excel, Word, and PowerPoint using Web services.
You can host your MicroStrategy applications, along with your data sources
and metadata, on premises, or you can use MicroStrategy Cloud. Using
MicroStrategy as a platform-as-a-service reduces your infrastructure overhead,
increases scalability, and reduces costs, while continuing to provide access to
MicroStrategys range of applications.
25
Metadata
All MicroStrategy analysis, development, delivery, and administration
applications can share a common metadata in your environment. A metadata
database contains information that enables MicroStrategy applications to
retrieve and display data from data sources. The metadata stores
MicroStrategy object definitions and maps MicroStrategy objects to the data
source structures and content.
MicroStrategy applications use the metadata to translate user requests into
queries and to translate the results of those queries back into MicroStrategy
objects, like reports, documents, and dashboards.
The metadata also stores the definitions of all objects created within the
MicroStrategy Analytics Platform (such as filters, reports, metrics, facts, and so
forth). The metadata enables the sharing of objects across MicroStrategy
applications by providing a central repository for all object definitions. Since
all of the interfaces share the same metadata, users can move from one
interface to another without any re-configuration or administrator
intervention. A report created with MicroStrategy Developer or MicroStrategy
Web can be viewed in Windows, Office, on a mobile device, and in emails
without any loss of functionality, security, or object privilege settings. The
metadata is used by MicroStrategy Intelligence Server to evaluate the most
efficient data retrieval scenario to guarantee optimal query performance.
more information about Intelligence server, see Connect to a
For
Project Source starting on page 42
Data Sources
At the base of the MicroStrategy Analytics Platform architecture is your data.
MicroStrategy supports a spectrum of data sources, from unmodeled, imported
spreadsheets to petabyte-sized databases:
Relational databases
Columnar databases
MapReduce databases
27
All MicroStrategy objects are stored in your metadata database. The main role
of these objects is to enable presentation and analysis of your data. The most
important objects for reporting are:
Reports
Filters
Attributes
Facts
Metrics
Prompts
Hierarchies
addition, there are objects that are used to manage security and
Inconfigure
connections and servers. For more information, refer to the
MicroStrategy Administration: Configuration and Security course.
Reports
A report is a request for specific data that has a defined layout and format. All
of the information for a report can be predefined, or you may be able to choose
part or all of the content of a report. You can view report results either in grid
or graph format. The following image shows an example of a report in grid
view:
Report Grid
Attributes
Attributes are the descriptive data in your data warehouse that you want to be
able to display on a report or document. Whether you want to view customers,
account numbers, products, regions, or employees, attributes enable you to
map to this data in your data warehouse and then display it on reports and
documents. You can also use this descriptive data to filter reports and
documents so that they only display specific customers, regions, accounts, and
so forth.
29
In the report above, Region, Category, and Year are all attributes that have
been placed on the report so you can display the corresponding data in the data
warehouse. The individual items that display under each attribute header are
referred to as attribute elements.
The report does not display data for all of the regions, categories and years that
are represented in the data warehouse. The report creator has filtered on an
attribute to restrict the result set.
is used to show relevant information and improve
Filtering
performance. For more information about how to use attributes in
Attributes define the level at which calculations are performed. For example, in
this report, revenue and units sold are calculated for each subcategory, which is
the lowest-level attribute on the report.
is possible to calculate data at different levels in a report or document
Itusing
advanced functionality. For more information, see the
MicroStrategy Developer: Advanced Reporting course.
Facts
Facts represent numeric data in your data warehouse that can be used as the
basis for calculations. They are typically numeric and they map directly to
columns in fact tables in your data warehouse. Some examples of things facts
can represent are information about sales, inventory, profit, costs, deposits,
withdrawals, or balances. For example, a Cost fact could be defined as
corresponding to the TOT_COST column in the ITEM_MNTH_SALES fact
table:
ITEM_MNTH_SALES Fact Table
Facts cannot be placed directly onto reports. Instead, you must use metrics,
which can be based on facts.
31
Metrics
Metrics are calculations that you place directly in reports. For example,
suppose you have a Cost fact, which represents the cost per item. Consider a
case in which you need to calculate the cost for Books, which is a category of
items. How should cost be calculated?
Sample Report with Two Metrics
Two ways of aggregating the cost data at the Category level are used in the
above report. One metric aggregates using the sum function and another uses
the average function.
You can use the Metric Editor to display or edit the formulas used in defining
metrics:
Sum of Cost
Average Cost
33
{~} indicates that the metric is to be aggregated at the report level, which is the
level of the lowest attribute on the report grid. For more information, see the
MicroStrategy Developer: Advanced Reporting course.
Metrics can be built using facts, attributes, or other metrics. In the following
report, the Employee Headcount metric uses the formula Count(Employee)
to apply the Count function to the Employee attribute
Report with Employee Headcount Metric
Lesson Summary
In this lesson, you learned:
Data warehouses are designed and optimized for analytical processing. This
type of system involves manipulating transaction records to calculate sales
trends, growth patterns, percent to total contributions, trend reporting,
profit analysis, and so forth.
The extract, transform, and load (ETL) process contains information that
facilitates the transfer of the data from the source systems to the data
warehouse.
Lesson Summary
35
36 Lesson Summary
2
INTRODUCTION TO
MICROSTRATEGY DEVELOPER
Lesson Description
This lesson introduces you to the MicroStrategy Developer application. It gives
you an opportunity to familiarize yourself with the interface and learn some of
the basic functionality.
In addition to navigating the interface, this lesson introduces you to project
sources and projects, two of the highest-level objects in the MicroStrategy
environment.
37
Lesson Objectives
After completing this lesson, you will be able to:
Describe the components of MicroStrategy Developer, navigate the main
interface, and access project sources and projects.
After completing the topics in this lesson, you will be able to:
Connect to a project source and access the projects within it. List and define
the components of a project. (Page 42)
Navigate and use the MicroStrategy Developer menus and toolbars. (Page
51)
List the different ways to create and save new objects. (Page 54)
38 Lesson Objectives
MicroStrategy Developer
MicroStrategy Architect
This course teaches you the fundamental skills required to use MicroStrategy
Developer. Each of the components of MicroStrategy Developer is briefly
described in this lesson.
more information about MicroStrategy Architect, refer to the
For
MicroStrategy Architect: Project Design Essentials course. For more
39
MicroStrategy Developer
MicroStrategy Developer is a next-generation business intelligence
environment designed to meet todays sophisticated business intelligence
requirements. It brings integrated querying and reporting, powerful
collaborative analytics, and investigative workflow to every Developer.
MicroStrategy Architect
MicroStrategy Architect is the innovative development environment designed
to meet todays sophisticated business intelligence requirements. Unique
techniques of mapping the business model to the underlying data structures
make MicroStrategy Architect the most flexible tool in the industry. It creates
business intelligence applications against terabyte-sized data warehouses
based on any industry business model, such as finance, banking, retail, or
pharmaceuticals. Through a user-friendly interface, you can create a rich
abstraction layer for a relational database. MicroStrategy Architect also
enables you to update the metadata, so changes are immediately and
transparently implemented for all users.
MicroStrategy Architects convenient database reference utility lets you view
column names and data types for any table in the data warehouse and speeds
application development by evaluating definitions in the logical model.
Advanced data models are simplified using the flexible schema definitions of
MicroStrategy Architect. You can use single columns, compound keys, or
user-defined expressions to define your schema objects.
Administrative Functions
Most of the administrative functionality for the business intelligence system is
found in the MicroStrategy Developer interface. The list below represents
important administrative functions that are offered by MicroStrategy
Developer:
User ManagementMicroStrategy Developer enables easy maintenance of
users and user groups. A host of powerful user and object management
features enables you to update access for current users, remove old users from
the system, and copy existing user profiles to new user accounts.
41
The following illustration shows the relationship between a project source, the
metadata database, and MicroStrategy projects:
Relationship Between Project Source and Projects
43
The icon above represents another type of project source. known as a three-tier
project source. The first tier is MicroStrategy Developer, the second tier is
Intelligence Server, and the third tier is the metadata database. This type of
project source points to an Intelligence Server that is, in turn, connected to a
MicroStrategy metadata database.
Intelligence Server provides the core analytical processing and job
management for all reporting, analysis, job management and monitoring in
implementations in which it is used.
With MicroStrategy Intelligence Server in your project environment, you can:
Manage, monitor and maintain the project as its data volume and user base
grows
All other icons are project icons that represent the MicroStrategy projects
stored in the metadata to which the project source is connected.
Administration Icon
The Administration icon provides access to all of the administrative functions
for a project source.
default, only users with administrative privileges can see the
ByAdministration
icon.
Without Intelligence Server, you are limited to the following administration
tools:
45
User ManagerEnable you to create and manage users and user groups.
With Intelligence Server, you get many additional administrative tools that
enable you to control and monitor most aspects of the MicroStrategy
environment.
more information on administration functionality, refer to the
For
MicroStrategy Administration courses.
Project Icons
A project is the intersection of a data warehouse, a metadata database, and a
user community. It contains objects such as reports, filters, templates, and
metrics.
To see the contents of a project:
Description
History
My Personal You use these folders to store objects you create, that are
Objects
only visible to you. You can always create additional
subfolders here.
Public
Objects
Description
Schema
Objects
Data
Explorer
If the Data Explorer does not display in the Folder List, in MicroStrategy
Developer,
on the Tools menu, select Preferences. In the Categories
list, below the Developer category, select General. In the Developer General pane, under Data Explorer, select the Show the Data Explorer
in the developer check box, and click OK. The Data Explorer should
now display in the Folder List.
47
In the MicroStrategy Developer interface, there are three main areas: the
Folder List, the Object Viewer, and the Shortcut Bar.
Folder List
By default, the Folder List is the middle pane in the MicroStrategy Developer
interface. It shows all of the project sources, projects, application and schema
object folders, as well as the administrative functions for the business
intelligence system.
The Folder List may not automatically display when you initially log in to
Developer.
Object Viewer
The right pane of the Developer interface is called the Object Viewer. Much like
Microsoft Windows Explorer, you navigate through the folder structure in the
Folder List, and the objects contained in the folders are displayed in the Object
Viewer.
Shortcut Bar
The area to the left of the Folder List is called the Shortcut Bar. It displays
shortcuts to various MicroStrategy Developer functionality and folders. Again,
like Microsoft Windows Explorer, you can add shortcuts to any location that
displays in your Folder List. The individual shortcuts can also be organized into
user-defined shortcut groups, which is especially useful for large MicroStrategy
implementations.
When you open MicroStrategy Developer, you will already have two shortcut
groups by defaultTutorial Shortcuts and Other Shortcuts.
To show the Shortcut Bar:
1 On the Shortcut bar, click the shortcut group to which you want to add the
shortcut.
2 In the Folder List, right-click the location, such as a project or folder, you
want to add to the Shortcut Bar and select Add to Shortcut Bar.
1 On the Shortcut Bar, right-click the shortcut and select Remove from
Shortcut Bar.
2 In the confirmation window, click Yes if you are sure you want to remove
the shortcut.
49
1 On the Shortcut Bar, right-click an empty area and select Add Group.
2 In the Create a new shortcut group window, type a name for the shortcut
group.
3 Click OK.
Basic Navigation
After completing this topic, you will be able to:
Navigate and use the MicroStrategy Developer menus and toolbars.
Description
File
Edit
View
Go
Tools
Window
Help
Basic Navigation
51
52 Basic Navigation
Button
Description
New object
Cut
Copy
Paste
Rename the
object selected
View object
properties
Run
View
Button
Description
Refresh object
with latest
definition
Go to project
Go one level up
Update Schema
Basic Navigation
53
Creating Objects
There are three ways to access the editors and wizards used to create new
objects in MicroStrategy Developer:
On the File menu, select New, followed by the object you want to create,
like a report or filter.
Saving Objects
Depending on which object editor or wizard you are using, you can save objects
in the following ways:
The first time you save an object, the Save As window opens, which enables you
to specify the name and the location where the object will be saved. The default
save location is the folder in which you are working when you open the object
editor or wizard.
Shortcuts to Objects
After completing this topic, you will be able to:
Create shortcuts to MicroStrategy objects.
On the File menu, point to New and select Shortcut. In the Open window,
locate the object for which you want to create the shortcut, and click Open.
Right-click the object to which you want to create a shortcut and select
Create Shortcut. In the Browse for Folder window, select the location in
which you want to create the shortcut and click OK.
Shortcuts to Objects
55
56 Shortcuts to Objects
Lesson Summary
In this lesson you learned:
Lesson Summary
57
58 Lesson Summary
3
REPORTS
Lesson Description
This lesson introduces you to report definition and report creation in
Developer.
59
Reports
Lesson Objectives
After completing this lesson, you will be able to:
Define the components that comprise a report and create simple reports using
Developer.
After completing the topics in this lesson, you will be able to:
Use the Report Editor to create and save reports. Execute reports and
change their display view. (Page 63)
60 Lesson Objectives
Reports
What Is a Report?
After completing this topic, you will be able to:
Explain the components that make up a report.
Reports are the focus of business intelligence analysis. They enable users to
gather business insight through data analysis. The results from any Developer
report are often just a starting point for further business intelligence
investigations.
A report is a request for specific, formatted data from the data warehouse. It
consists of a template plus any desired filtering criteria, as shown below:
Components of a Report
A template specifies what information to retrieve from the data warehouse and
how this information will be displayed in the report results.
A report filter specifies the conditions that the data must meet to be included
in the report results.
What Is a Report?
61
Reports
62 What Is a Report?
Reports
You use the Report Editor to create and modify reports. It is a combination of
the Filter Editor, the Template Editor, the Object Browser, the Shortcut Bar,
the Report objects pane, and the View Filter definition pane. You can use this
one editor enables to create the template and report filter for a specific report.
These components perform the following functions:
63
Reports
Report objects paneEnables you to see a summary of all of the objects you
have included on your template, even if they are not initially displayed in
the report view. The MicroStrategy Engine generates SQL that includes all
of the objects in this window, not just the ones that are displayed when the
report is run.
Report objects pane and the View Filter definition pane are only
The
available if you have MicroStrategy OLAP Services. For more
information on MicroStrategy OLAP Services, see MicroStrategy
OLAP Services starting on page 279. For more information on the
MicroStrategy Engine, refer to the MicroStrategy Engine Essentials
course.
View Filter definition paneEnables you to filter on any object that is in the
Report objects pane. View filters do not modify the SQL for the report.
more information on View Filters, see the View Filters lesson
For
starting on page 285.
Creating Reports
As mentioned, whenever you create a report you also create a template and a
report filter. Though you may not specifically define and use a separate
template or report filter object, these are the objects that logically make up a
report definition.
Reports
The Template
A template specifies what information to retrieve from the data warehouse and
how this information will be displayed in the report results. You can create
template objects separately using the Template Editor, or you can create them
in the Report Editor.
To define the template, you can either drag objects from the Object Browser to
the template definition pane, or you can right-click the object in the Object
Browser and select Add to Rows or Add to Columns. Each object placed on
the template becomes a row or column header, which organizes the data in the
final report result display. The empty cells below the headers in the template
are place holders for the actual data that will be returned from the data
warehouse after the report is executed.
The layout of a template can be cross-tab or tabular:
Sales ($)
North
Atlanta
Miami
Boston
New York
100
200
300
400
Store
Sales($)
South
Atlanta
100
South
Miami
200
North
Boston
300
North
New York
400
65
Reports
this example, there are no low, middle, and high income levels
Indefined
in the data warehouse, so you create these levels by grouping
together income ranges, which do exist in the data warehouse. For more
information on consolidations, refer to the MicroStrategy Developer:
Advanced Reporting course.
Reports
MetricCalculation built from facts in the data warehouse. All the metrics
are grouped together and bound to one axis (the rows or the columns).
67
Reports
You can create report filter objects separately using the Filter Editor, or you
can create them in the Report Editor. For this lesson, you will use the Report
Editor.
To define the report filter, you can drag objects from the Object Browser onto
the report Filter definition pane.
Reports
OR
Right-click the attribute and select Add to Rows or Add to Columns.
To add a metric to the template definition pane:
6 In the Object Browser, locate the metric you want to add to the template.
7 Double-click the metric to add it to the columns of the template.
OR
Drag the metric to the template definition pane.
OR
Right-click the metric and select Add to Rows or Add to Columns.
that all metrics are grouped together and bound to one axis
Recall
(the rows or the columns).
To add a basic report filter condition:
8 In the Object Browser, double-click the desired hierarchy to display the list
of attributes included in that hierarchy.
9 Double-click an attribute to see a list of its attribute elements.
10 Select the attribute elements for which you want data returned and drag the
attribute elements to the Filter definition pane.
69
Reports
Replace with copy of template: Changes you make to the template from
within the Report Editor are not propagated to the original template.
Similarly, changes made to the template object from within the Template
Editor are not propagated to the report. This is also called a local template
and is the same as creating a template on the fly in the Report Editor.
1 In the Report Editor, in the Object Browser, browse to the template object
you want to add to the report definition.
2 Right-click the template object and select Replace with shortcut to
template or Replace with copy of template.
OR
On the Template menu, select Replace with shortcut to template or
Replace with copy of template.
If using an existing report filter object in a report, you have three options:
Add to Report Filter: Adds the report filter object to the report. You cannot
make changes to the report filter object from within the Report Editor, but
changes made to the report filter object from within the Filter Editor are
propagated to the report and any other reports that use the report filter
object.
can continue to add other report filter conditions to the report
You
from within the Report Editor.
Reports
Replace Report Filter with a copy of this filter: Changes you make to the
report filter from within the Report Editor are not propagated to the
original report filter. Similarly, changes made to the report filter object
from within the Filter Editor are not propagated to the report. This is also
called a local or embedded filter and is the same as creating a filter on the
fly in the Report Editor.
Embed a copy of the template in the report: Changes you make to the
stand-alone template are not propagated to this report. Changes that you
make to the embedded template within this report are not propagated to
the template.
1 In the Report Editor, in the Object Browser, browse to the report filter
object you want to add to the report definition.
2 Right-click the report filter object and select Add to Report Filter, Replace
Report Filter with a shortcut to this filter or Replace Report Filter with
a copy of this filter.
OR
Double-click the report filter object.
71
Reports
Saving Reports
After you create a report, you can save the report, so you can execute it again in
the future. When you save a report, its name and definition (the template, all
report filtering criteria, and any report formatting) are stored in the
MicroStrategy metadata database. When you want to execute the report again,
you can double-click it to retrieve the latest results. Saving a report creates a
predefined report.
To save a report:
The template and the report filter objects can also be saved as standalone
MicroStrategy objects, separate from the report, allowing them to be reused
later.
To save a template from the Report Editor:
Reports
Create a local copy of the filterIf you choose this option, changes you
make to the report filter in the Report Editor are not propagated to the
original filter object, and vice versa. This is also called a local or embedded
filter.
Retain the shortcut to the filterIf you choose this option, changes you
make to the report filter in the Report Editor are propagated to the original
filter object, and vice versa. Creating shortcuts allows you to take advantage
of the benefits of object reuse.
Create a local copy of the templateIf you choose this option, changes
you make to the template in the Report Editor are not propagated to the
original template object, and vice versa. This is also called a local or
embedded template.
Retain the shortcut to the templateIf you choose this option, changes
you make to the template in the Report Editor are propagated to the
original template object, and vice versa. Creating shortcuts allows you to
take advantage of the benefits of object reuse.
Remember options next timeIf you choose this option, your advanced
save options become the new default options for future advanced save
actions.
73
Reports
Running Reports
To run a report:
report results display in the default report display view. The default
The
report display view is the report display view that was selected when the
report was last saved. Report display views are discussed in the
following section.
Design ViewDisplays the Report Editor, so you can view and modify the
report definition
SQL ViewDisplays the SQL used to generate the report. Any Analytical
Engine steps that are taken after all of the data has been returned from the
data warehouse to produce the final report results are also displayed.
Reports
1 In the report results window, on the View menu, select the report display
view you want to see.
OR
In the report results window, on the toolbar, beside the View button, click
the arrow, and select the report display view you want to see.
To change a grid reports formatting using autostyles:
75
Reports
The Report Details Properties window consists of the four tabs described in the
following sections.
General
The General tab of the Report Details Properties window contains
configuration options for the report, prompt, and filter details. The window
contains the following sections:
Reports
default, each setting on this tab inherits the project setting defined in
ByProject
Configuration/Project Definition/Document and Report setting.
Filter DetailsContents
The Filter DetailsContents tab of the Report Details Properties window
contains configuration options for the filter details, which displays information
about filters on the report. This tab enables you to select which filter
expressions to include (report filter, view filter, report limits, and so on) and
how the filters are displayed. For example, you can select whether to include
labels (that is, Report Filter, Report Limits, and so on) and the order in which
the filter expressions are displayed.
default, each setting on this tab inherits the project setting defined in
ByProject
Configuration/Project Definition/Document and Report setting.
The window contains the following sections:
Additional OptionsYou can configure how the filters are displayed in the
Filter Details.
Filter DetailsOther
The Filter DetailsOther tab enables you to specify how logical operators and
other components of different qualification types are displayed
77
Reports
Template Details
The Template Details tab contains configuration options for the template
details, including attribute details and metric details.
To configure report details properties:
1 Open a report.
2 On the Data menu, select Report Details Properties.
3 Modify the properties as needed.
4 Click OK.
you do not see the report details display in the Report details
Ifwindow,
you need to clear the Apply these Developer preferences
to the report details check box under Preferences.
Reports
Lesson Summary
In this lesson your learned:
A report is a request for specific, formatted data from the data warehouse.
Each report contains a template and a report filter, even if they are empty.
A report filter specifies the conditions that the data must meet to be
included in the report results.
You use the Report Editor to create and modify reports. It is a combination
of the Filter Editor, the Template Editor, the Object Browser, the Shortcut
Bar, the Report objects pane, and the View Filter definition pane, and it
enables you, through one editor, to create your template and report filter
for a specific report.
After you create a report, you can save the report, so you can execute it
again in the future.
There are five report display viewsDesign View, Grid View, Graph View,
Grid Graph View, and SQL View.
Lesson Summary
79
Reports
80 Lesson Summary
Exercises: Reports in Developer
Complete these exercises in the MicroStrategy Tutorial project located in the
MicroStrategy Analytics Modules project source. This project source is
three-tier.
81
Create a Report
Overview
In this exercise, you will create a new folder called My Reports Exercises in the
My Reports folder. In the My Reports Exercises folder, you will create a report
to show the Revenue and Profit for all Call Centers during 2012. This report
will also show the Region to which each Call Center belongs. The first few rows
of the results should look like the following:
You will save this report as Revenue and Profit for 2012. You can use the
detailed instructions that follow if you want help.
Detailed Instructions
Create the My Reports Exercises folder
6 In the Folder List, select your new My Reports Exercises folder to begin
working in it.
7 On the File menu, point to New and select Report.
8 In the New Grid window, leave Blank Report selected and click OK.
the Report Editor opens, the hierarchies created for the
When
project are listed.
Define the template
83
21 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
Save the report
You will save this report to the My Reports Exercises folder and name it East
Revenue and Profit for 2012. You can use the detailed instructions that follow
if you want help.
Detailed Instructions
1 In MicroStrategy Developer, in the My Reports Exercises folder, right-click
the Revenue and Profit for 2012 report you created in the previous
exercise and select Edit.
2 In the Report Editor, in the Object Browser, double-click the Geography
hierarchy.
3 Double-click the Region attribute.
4 Select Northeast.
5 While holding down the CTRL key on your keyboard, select Mid-Atlantic
and Southeast.
6 Drag the three regions to the report Filter definition pane to add them to
your existing report filter condition, Year In list (2012).
Save the report
85
11 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
12 In the report, click Save and Close to close the report.
You will save this template in a new folder, My Templates Exercises. You can
use the detailed instructions that follow if you want help.
Detailed Instructions
1 In MicroStrategy Destkop, in the Folder List pane, expand the My Personal
Objects folder and select the My Objects folder.
2 On the File menu, point to New and select Folder.
3 Name the folder My Templates Exercises.
4 In the Object Viewer, double-click the new My Templates Exercises folder
to begin working in it.
5 On the File menu, point to New and select Template.
6 In the New Template window, leave Empty Template selected and click
OK.
the Template Editor opens, the Data Explorer is automatically
When
selected in the Object Browser. The System Hierarchy and other
user-defined hierarchies created for the project are listed.
87
17 Click Save.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Create the report
1 In the Folder List, under My Personal Objects, under My Reports, select the
My Reports Exercises folder to begin working in it.
2 On the File menu, point to New and select Report.
3 In the New Grid window, keep Blank Report selected and click OK.
4 In the Report Editor, in My Shortcuts, click My Personal Objects.
For this report, you will not include any filtering criteria.
Save the report
89
Optional Advanced Exercise
The following exercise is optional and is intended to challenge your knowledge
of the concepts covered in this lesson. It does not include step-by-step
instructions. Instead, the exercise provides a list of report requirements and
describes the features and functionality that you can use in order to meet the
report requirements
You may save the report in the My Reports Exercises folder with a name of
your choosing.
Now modify the previous report to find out the Revenue in 2012 for the
Mid-Atlantic customer region when customers used Visa as their preferred
payment method. This report would be useful when you need to decide which
items should go on promotion. The report result set should now look like the
following:
After saving the report, answer the following questions when you have
completed the exercise.
How can you find the number of rows without actually counting them?
_______________________________________
_______________________________________
_______________________________________
91
4
REPORT DATA
MANIPULATIONS
Lesson Description
This lesson describes data manipulations that you can perform in Developer
reports.
93
Lesson Objectives
After completing this lesson, you will be able to:
Define the different types of report manipulations available and perform these
report manipulations using Developer.
After completing the topics in this lesson, you will be able to:
Describe and perform manipulations that enable you to look at report data
from different perspectives. (Page 95)
Deliver reports to the history list, update caches, and mobile devices. (Page
130)
94 Lesson Objectives
Data Manipulation
After completing this topic, you will be able to:
Describe and perform manipulations that enable you to look at report data
from different perspectives.
This section covers report manipulations that enable you to change how data is
presented in a report, so you can see the data from different perspectives.
The following report data manipulations are covered in this section:
Drilling
Page-by
Data pivoting
Subtotals
Data sorting
Outline mode
Adding notes
Data Manipulation
95
Drilling
After completing this topic, you will be able to:
Explain the purpose of drilling and drill on reports in Developer using a variety
of drilling methods and options.
What Is Drilling?
Drilling enables you to see data at levels other than that of the original grid or
graph. It helps you investigate the data on your report quickly and easily. The
following diagram shows how you can display additional detail through
drilling:
Drilling
96 Drilling
Drilling down enables you to access data at a lower attribute level in the
same hierarchy. For example, if a report shows you sales by Month, you can
drill down to see sales by Day.
Drilling up does the opposite of drilling down. You can see data at a higher
attribute level in the same hierarchy. For example, you can drill up from the
Day level to the Month or Quarter levels.
Drilling to other directions lets you view data at any level in any hierarchy.
For example, you could drill from Day in the Time hierarchy across to
Region in the Geography hierarchy.
By default, when you drill on a report, the original report remains open, and
the drilled-to report displays in a new window.
Drilling
97
Use the Drill menu option or toolbar buttonDrills on either the entire
report or only selected items.
1 Run a report.
2 On the Data menu, select Drill.
OR
On the toolbar, click Drill.
the toolbar buttons are not visible by default, on the View menu, click
IfToolbar,
and select Data.
98 Drilling
3 In the Drill window, in the Selected object drop-down list, select the object
on which you want to drill. You can drill on attributes, compound metrics,
consolidations, and custom groups, as shown below:
4 In the Drilling options window, browse to the attribute to which you want
to drill.
5 Choose whether to keep the parent.
6 Choose whether to keep the thresholds.
7 Choose whether to inherit subtotals from parent.
8 Click OK to drill.
the page-by functionality on the original report, you
Ifwillyoualsoareseeusing
the When drilling, add the current page-by element
as part of the filter check box. For more information on page-by, see
Page-by starting on page 103.
Drilling
99
Keep Parent
The Keep parent option in the Drill window lets you determine whether or not
you want to add the attribute from which you drilled to the new drilled-to
reports template.
For example, consider the following report showing revenue by year. The
original report from which you are drilling is shown below:
Yearly Revenue Report
If you drill down to Month from Year 2010 and do not set Keep parent to Yes,
you see the following report, where Year has been replaced by Month:
Keep Parent Set to No
100 Drilling
If, instead, you set Keep parent to Yes, you see the following report, where
Month is added to the template along with Year:
Keep Parent Set to Yes
1 Run a report.
2 On the Data menu, select Report Data Options.
3 In the Categories list, expand General.
Drilling
101
5 Click OK.
6 In the report results window, on the File menu, select Save.
To set the Keep parent setting at the project level:
102 Drilling
Page-by
After completing this topic, you will be able to:
Explain the purpose of page-by. Use page-by to segment data on a report in
Developer.
What Is Page-by?
Page-by enables you to select and display subsets of your report results as
separate pages. This feature is most useful when you have extremely long
report results and scrolling is necessary to see all of the data.
Suppose you have the following report showing Revenue and Profit data
organized by Region and Quarter. Notice that only the first few result rows are
shown below:
Quarterly Region Revenue and Profit Report
Page-by
103
You can page by Quarter to see only one quarters worth of data at a time:
Page-by Quarter
Attributes
Metrics
Hierarchies
Consolidations
Custom groups
1 Run a report.
2 On the toolbar, click View Page-by.
104 Page-by
3 Drag the objects you want to page by to the Page-by fields pane that display
above the report results.
4 Use the drop-down lists to select the specific data you want to see on the
report.
5 In the report, on the File menu, select Save to save your page-by field
selections to the report definition.
State first, then ItemIf Alaska is selected for State, the list of attribute
elements for Item does not include surfboards. Similarly, if Hawaii is
selected for State, the list of attribute elements for Item does not include
snowshoes.
Item first, then StateIf snowshoes is selected for Item, the list of attribute
elements for State does not include Hawaii. Similarly, if surfboards is
selected for Item, the list of attribute elements for State does not include
Alaska.
Page-by
105
Data Pivoting
After completing this topic, you will be able to:
Explain the purpose of data pivoting. Pivot data on a report in Developer by
changing the order of objects in the rows or columns and moving objects
between the rows and columns.
Data pivoting enables you to rearrange the columns and rows in a report, so
you can view data from different perspectives. With data pivoting, you can do
the following:
Move objects from the row header to the column header and vice versa
Change the order of objects in the row header or in the column header
Move objects from the row header or the column header to the page field
pane
Select an object, and choose a data pivoting option from the Move menu.
Right-click an object, point to Move, and select an option from the menu.
Select an object and use one of the data pivoting buttons 0n the toolbar:
Data Pivoting Buttons
Name
Button
Move to Row
Move to Column
Move to Page
Move Up
Move Down
Move Left
Move Right
Remove from
Grid
Data Pivoting
107
Subtotals
After completing this topic, you will be able to:
Apply subtotals to a report in Developer.
1 Run a report.
2 On the Data menu, select Subtotals.
3 In the Subtotals window, on the Definition tab, select the subtotals you
want to see on your report, as shown below:
4 Click OK.
108 Subtotals
5 In the report, on the File menu, select Save to save the subtotals to the
report definition.
Subtotals by Position
Consider a report with four attributes. You may want to suppress all subtotals
except for a grand total, in order to simplify a report:
Subtotals by Position
1 Run a report.
2 On the Data menu, select Subtotals.
3 In the Subtotals window, on the Definition tab, select the subtotals you
want to see on your report.
4 Click Advanced.
Subtotals
109
110 Subtotals
The second report shows subtotals across Quarter only, as shown below:
Subtotals Across Quarter
This functionality gives you more control over the display of subtotals on your
report.
To display subtotals for selected attributes:
Subtotals
111
Subtotals Group By
Subtotals are typically accumulations of metrics based on the layout of
attributes on a report. However, subtotals may be grouped by any attribute on
a report regardless of the report layout. For example, compare the following
two reports. The first report shows subtotals across quarters. The Quarter
subtotal is broken down by Manager because the Manager attribute is listed to
the left of the Quarter attribute, as shown below:
Subtotals By Manager
112 Subtotals
The second report uses the subtotals group by functionality and displays
subtotals for each Quarter, regardless of the Manager:
Subtotals by Quarter
Subtotals
113
6 Click Add.
7 In the Group by Selection window, select the attributes on which you would
like to group subtotals.
8 Click OK to close the Group By Selection window.
9 Click OK to close the Advanced Subtotals Options window.
10 Click OK again to close the Subtotals window.
11 In the report, on the File menu, select Save to save the subtotals to the
report definition.
114 Subtotals
Sorting
After completing this topic, you will be able to:
Sort data in a report in Developer using a quick sort or an advanced sort.
Sorting enables you to specify the order in which the data in a report for a
particular row or column is presentedeither ascending or descending. You
can sort based on any object that you place on the template. You can also select
the sorting criteria and the sorting order.
Quick sortEnables you to select one column or row and sort it in either
ascending or descending order based on the data displayed. This option is
only available in grid view and grid and graph views.
Quick Sort
The first thing you must do to perform a quick sort is to run a report. Then
select the row or column header by which you want to sort the report. You can
then sort in the following ways:
Right-click the column or row header and select Sort rows by this column
(or just Sort if you right-clicked a row header), followed by either
Ascending or Descending.
Sorting
115
Button
Description
Sort
Ascending
Sort
Descending
the toolbar buttons are not visible by default, on the View menu, click
IfToolbar
and select Data.
can only sort by one row or one column when using the quick sort
You
method. If you sort by one column and then sort by another, you will
lose the order for the first sort. Advanced sorting lets you sort by
multiple rows and columns.
Advanced Sort
Advanced sort enables you to configure multiple sorts. You can select the
attributes or metrics you want to use to sort the report and the order in which
you want to sort by them. For attributes, you can also choose the attribute form
(for example, ID or description) by which to sort the attribute data.
Every sort has the following fields that you can change to create completely
customized sorting criteria:
Sort Columns
116 Sorting
Column
Description
Sort By
Criteria
Order
Sort Columns
Column
Description
Total
Position
Parent
Position
Sorting
117
2 In the Sorting window, click the appropriate tab, Rows, Columns, or Pages,
depending on what you want to sort, as shown below:
118 Sorting
Sorting on Page-by
Within the Advanced Sorting options, you can sort the page-by elements
(ascending or descending) based on either their ID or description. The image
below shows the Pages tab of the Sorting window:
Sorting on Page-by
For example, if you have a report with the Year attribute in the page-by field,
you can set the elements of the year to be displayed in ascending or descending
order. The image below shows the Year attribute elements sorted in
descending order:
Page-by on Year Attribute
Sorting
119
To sort on page-by:
120 Sorting
Outline Mode
After completing this topic, you will be able to:
Explain the purpose of outline mode. Display a report in outline mode in
Developer.
Outline Mode
121
The same report displayed in outline mode looks much better, as shown below:
Product Revenue Report With Outline Mode
Expanding and collapsing the different levels of the report does not execute
any SQL against the data warehouse. Outline mode is only available when you
have more than one object in the rows of the report template.
You can expand and collapse levels by clicking the numbered buttons above the
report. There will be one button for each column in the report. See the three
reports below for an example of how clicking these buttons can affect the look
of a report in outline mode. The initial report is shown below:
All Levels Displayed
Outline Mode
123
Finally, when you click the 1 button, the information is completely rolled up
as follows:
Category Revenue Only
data totals for a collapsed level, you must enable subtotals. For
Tomoreseeinformation
on subtotals, see Subtotals starting on page 108.
By default, reports in outline mode are displayed with all levels expanded.
To set an outline mode report to initially display with all levels collapsed:
Printing
After completing this topic, you will be able to:
Print a boardroom quality report.
You can print a report in Grid, Graph, Grid and Graph, or SQL view. The
formatting you apply to the report in Developer also applies to the printed copy
of the report.
You can print a report using one of the following methods:
Clicking Print Preview opens the Print Preview window for your report, as
shown below:
Print Preview Window
Printing
125
In the Print Preview window, click Setup to open the Page Setup window,
which enables you to:
Choose the order in which to print pages if the report is particularly long
or has numerous page fields.
126 Printing
Microsoft Excel
Microsoft Word
Microsoft Access
Plain text
HTML
To export a report:
1 Run a report.
2 On the Data menu, point to Export To and select the application format in
which you want to see the report results.
You can manipulate the behavior of the export function using export options.
To access export options:
1 Run a report.
2 On the Data menu, select Export Options.
3 In the Export Options window, in the Application drop-down list, select the
application to which you are exporting.
127
1 Run a report.
2 On the File menu, point to E-mail report as and select the application
format that you want to use to e-mail the report as an attachment.
you select the attachment type, an e-mail message window opens
After
with the report file as an attachment. Depending on the size of the
report, this action may take a few moments.
5 Click OK.
6 Save and close the report.
will be able to see this change when viewing the report in
You
MicroStrategy Web or when you view the exported report in PDF or
HTML.
129
In Developer, you can subscribe reports and documents to history list, cache
and mobile.
2 Select a schedule and appropriate options and click OK. The different
options are depicted below:
131
To update the cache of a report or document, you must subscribe to that report
or document. You can use the Cache Update Subscription Editor to subscribe
to this update, as shown below:
Cache Update Subscription Editor
133
Within the Mobile Subscription Editor, you can specify your desired schedule.
This schedule controls how often the report or document is sent, and when you
want this subscription to end, as depicted below:
Mobile Subscription Editor
135
You can actively collaborate online with other Developer users using notes. You
can think of notes as annotations or comments attached to a report or a
document, which enable you to communicate important information about the
report to the end users. For example, you can educate users how to navigate
through report results, find optimal drill paths, interpret thresholds, and so on.
End users, on the other hand, can share their feedback by adding comments
about the usability of the design or the relevance of metrics.
are linked to the report and document definition, but are not
Notes
saved with it. When you add, modify, or delete notes, you do not
invalidate the report or document cache.
1 In Design View or Grid View, on the toolbar, click Notes, as shown below:
OR
2 In Design View or Grid View, on the View menu, select Notes.
3 Type your desired note in the lower text box, as shown below:
4 Click Submit.
5 Click Close.
137
To modify notes:
Lesson Summary
In this lesson you learned:
Drilling enables you to see data at levels other than that of the original grid
or graph. It helps you investigate the data on your report quickly and easily.
Page-by enables you to select and display subsets of your report results as
separate pages. This feature is most useful when you have extremely long
report results and scrolling is necessary to see all of the data.
Data pivoting enables you to rearrange the columns and rows in a report, so
you can view data from different perspectives.
Sorting enables you to specify the order in which the data in a report for a
particular row or column is presentedeither ascending or descending.
You can sort based on any object that you place on the template. You can
also select the sorting criteria and the sorting order.
You can print a report in grid, graph, grid and graph, or SQL view. The
formatting you apply to the report in Developer also applies to the printed
copy of the report.
You can actively collaborate online with other Developer users using notes.
Lesson Summary
139
Exercises: Report Data Manipulations in
Developer
Drilling and Page-By
Overview
Create a report with Region and Category in the rows and Year and Revenue in
the columns. The first few rows of the initial report should look like the
following:
141
After creating this report, modify it so that the data displays at a lower level
and is easier to read. The modified report will look like the following:
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Create the report
143
21 On the Report Data Options window, expand the General menu and select
Drilling.
22 In the GeneralDrilling pane, in the Keep parent while drilling drop-down
list, select No.
.
23 Click OK.
24 Click Yes to agree to re-execute the report.
26 In the new report, right-click the Category header, point to Drill, point to
Down, and then select Subcategory.
new Report Editor window opens and displays data at the
ASubcategory
level. The first few rows and columns of your results
should now look like the following:
145
Use pivoting and advanced sorting to change the report display to look like the
following:
Detailed Instructions
Create the report
147
18 Click Add.
20 In the Order column, select Descending. Leave the other defaults. Your
Sorting window should now look like the following:
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Search for report
149
4 Click Find Now. The search should look like the following:
9 In the Summary screen, click Finish. The first few rows of the initial report
look like the following:
Be sure you select Remove from Report and not Remove from Grid.
13 In the template definition pane, right-click the Region attribute and select
Remove from Report.
14 In the Developer window, click Yes.
151
Enabling subtotals
22 In the Report Editor, on the Grid menu, select Display Outline Results.
The first few rows of the report now look like the following:
153
Exporting Reports
Overview
Export the Employee Birthdays report (found in the Public
Objects\Reports\Subject Areas\Human Resources Analysis folder) to
Microsoft Excel so you can save it in your local machine. The first few rows of
the exported report should look like the following:
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In the Folder List, expand the Public Objects folder, followed by the
Reports folder, followed by the Subject Areas folder, and select the
Human Resources Analysis folder.
2 In the Object Viewer, double-click the Employee Birthdays report to
execute it.
3 In the Report Editor, on the Data menu, point to Export To and select MS
Excel.
can specify pre-export and post-export Microsoft Excel macros,
You
a destination file, and whether or not to include Report Details and
4 Compare your results to the expected results in the Overview section at the
beginning of this exercise.
5 Close the Microsoft Excel workbook without saving it.
6 In Developer, close the Employee Birthdays report without saving it.
155
5
REPORT STYLE
MANIPULATIONS
Lesson Description
This lesson describes style manipulations that you can perform in reports in
Developer.
157
Lesson Objectives
After completing this lesson, you will be able to:
Define the different types of style manipulations available and perform these
style manipulations using Developer.
After completing the topics in this lesson, you will be able to:
Lock row and column headers and resize columns in Developer. (Page 174)
Describe some of the basic graph properties and modify a graph report in
Developer. (Page 177)
Style Manipulation
After completing this topic, you will be able to:
Describe and perform style manipulations in Developer that enable you to
change the formatting of report data.
This chapter covers style manipulations that enable you to determine how
report data is formatted. You can change the look and feel of a report in
Developer using various formatting methods.
The following report style manipulations are covered in this section:
Formatting in Developer
Thresholds
Banding
Resizing columns
Style Manipulation
159
Formatting
After completing this topic, you will be able to:
Make formatting changes to reports in Developer. Create, save, and use
autostyles.
Formatting involves changing the display of a report. You can format the look
and feel of your report by altering the number display, alignment, font, border,
and patterns for column and row axes, template object headers and values, and
subtotal headers and values.
You can right-click any object on your template and select Formatting. You
can also right-click the word Metrics to format all of the metrics on the
report in the same way. The Format Cells window opens for you to make
formatting changes. For example, if you run a report with Category on the
template, and you right-click the Category header, you would see the
following formatting options:
Formatting Options
160 Formatting
You can use the Formatting toolbar to select the objects you want to format
and to make formatting changes:
Formatting Toolbar
You can use the Format menu to select the objects you want to format using
the menu shown below:
Format Menu
The Format Cells window opens for you to make formatting changes.
To format objects on a report:
1 Right-click an object on the report, point to Formatting, and select the part
of the object you want to format (for example, headers, values, and so
forth).
You can also use the Formatting toolbar or the Format menu to select the
object you want to format. If you are using the Formatting toolbar, you use the
drop-down lists and buttons on the toolbar to select the object and to make
your formatting changes.
Formatting
161
3 Click OK.
Remember to save the report with its new formatting.
can also use the Find and Replace tool to modify the format of sets
You
of metrics throughout a MicroStrategy project. For more information on
the Find and Replace tool, refer to the MicroStrategy Developer:
Advanced Reporting course.
Autostyles
Autostyles are predefined formatting schemes that are available when viewing
a report in grid view or grid graph view.
162 Formatting
1 Run any report in grid mode and customize the formatting using any of the
methods discussed in the previous section.
2 On the Grid menu, select Save AutoStyle As.
3 In the Save AutoStyle As window, select a location and name your autostyle.
default save location for a custom autostyle is My Objects. If you
The
save an autostyle to this folder, it will appear in only your autostyle
Formatting
163
4 Click Save.
To define a project default autostyle:
164 Formatting
Thresholds
After completing this topic, you will be able to:
Explain the purpose of thresholds and apply thresholds to a report in
Developer.
Thresholds are also applied to the Profit and Profit Margin metrics.
Thresholds
165
You can copy and paste threshold definitions, which enables you to save time
by reusing them when the same definition is needed to define thresholds on
multiple metrics. You are also provided four shortcut thresholds. These
shortcut thresholds include highest and lowest rank and percentage.
To create and apply a threshold to a grid report:
1 Run a report.
2 On the Data menu, select Thresholds.
OR
Right-click the appropriate metric and select Thresholds.
OR
On the toolbar, click Thresholds.
Threshold icon is not visible by default, on the View menu,
IfclicktheToolbar
and select Data.
166 Thresholds
3 In the Thresholds Editor, on the toolbar, in the drop-down list, select the
metric to which you want to apply the threshold, as shown below:
you create a threshold for one metric, you can easily copy it to
After
multiple metrics on the report.
4 Select the New Threshold check box to ensure your threshold is enabled.
5 Click New Threshold text box.
6 In the text box, type a name for the threshold.
7 Click Click here to start a new qualification. The parts of the condition
are displayed, each of which must be defined:
Click Field to select the attribute or metric that is part of your condition.
Replace TextSelect this option to define your own text. This action
replaces the value that meets your threshold condition with text. Type
the text in the empty text field. The text should be limited to 255
characters.
Thresholds
167
ImageSelect this option to replace the value that meets your threshold
condition with an image file.
Quick SymbolSelect this option to replace the value that meets your
threshold condition with a symbol, as shown below:
ImageIf you selected Image, in the Absolute path box, click browse to
provide the location of the image.
Quick SymbolIf you selected Quick Symbol, select a symbol from the
right. On the toolbar, click Edit the threshold formatting to define the
alignment, size and color (font), cell border, cell background, and cell
pattern for the symbol you have chosen.
168 Thresholds
When you edit a threshold, it does not affect the copied thresholds.
To copy a threshold:
1 In the Thresholds editor, select the threshold to copy and, on the toolbar,
click Copy.
2 On the toolbar, in the drop-down list, select the metric to which you want to
copy the threshold.
Thresholds
169
4 To rename it, click the threshold name and type the new name.
5 Edit the threshold, if necessary.
6 Click OK to save the threshold and return to the report.
170 Thresholds
Banding
After completing this topic, you will be able to:
Explain the purpose of banding and apply custom banding to a report in
Developer.
Banding
171
172 Banding
Banding
173
Developer enables you to lock row and column headers on a grid report, so
while viewing report results, you can scroll horizontally and vertically without
losing sight of the row or column headers. This property is particularly
advantageous when you want to view information that spans more rows or
columns than can be displayed at one time.
To lock row and column headers:
175
The second report does not have the wordwrap feature enabled, so the metric
names make the columns much wider:
Wordwrap Feature Not Enabled
Graph Properties
After completing this topic, you will be able to:
Describe some of the basic graph properties and modify a graph report in
Developer.
There are numerous graph properties that enable you to customize nearly
every aspect of a graphs appearance. You can choose from dozens of different
graph types and styles. After you choose an overall graph type and graph style,
other options enable you to adjust various aspects of the graph, such as the
data labels, a legend, its axes, and its titles. This topic describes a few of the
more common graph properties you may use.
in the same manner). However, you can also manually set the format
of the data labels.
Graph Properties
177
5 In the Category - Axis Labels pane, select the positioning of the labels in the
graph.
6 In the Properties Categories list, expand Axis Labels, and select Axis Line
to format the axis line.
7 Under Axis Labels, click Font to format the axis label font. In the Properties
categories list, under Axes, expand Y, followed by Axis Labels, and select
Number Formatting to format the axis numbers.
8 In the Axis Labels - Number Formatting pane, under the Category list,
select the type of formatting you want to apply.
9 Click OK to close the Preferences window.
Graph Title
By default, the title of a graph is the name of the report, but you can manually
change the title using static text or graph title variables. A graph title can also
be reformatted.
4 In the Properties Categories list, under Titles, under All, select Font.
5 In the All - Font pane, make the appropriate changes to format the title font
and frame.
6 In the Properties Categories list, under All, click Fill. Make the appropriate
changes to format the title fill.
7 In the Properties Categories list, under All, click Border. Make the
appropriate changes to format the title border.
8 In the Preferences window, click Apply
Graph Properties
179
9 Click OK.
can also use the Find and Replace tool to apply a font of your choice
You
to graph titles and labels in selected sets of reports and templates
throughout a MicroStrategy project. For more information on the Find
and Replace tool, refer to the MicroStrategy Developer: Advanced
Reporting course.
Graph Properties
181
Nested Labels
When there are several attributes in the rows of a report, all of the attributes
are displayed in each label on the category axis, resulting in a cluttered look, as
shown below:
Graph with Many Attributes in the Legend
In addition, when you enable nested labels, you can also draw brackets for each
attribute level for added effect, as shown below:
Nested Labels with Brackets
1 In the Options - General pane, under Graph Labels, select the Use nested
labels check box, as shown below:
Graph Properties
183
2 To show or hide the individual labels of graphs that have several data series,
select the Concatenate labels for multiple series check box.
option only works for graphs that require multiple data for one
This
data point, such as bubble, scatter, and stock graphs.
3 To show or hide the last level labels of graphs that have several data series,
select the Suppress last level labels check box. This option applies to all
data series in the graph.
option is useful for graphs that require multiple data for one
This
data point, such as bubble, scatter, and stock graphs.
4 Click OK to apply the changes and close the Preferences window.
5 In the graph report, on the File menu, select Save to save the nested labels
to the report definition.
Graph Undo/Redo
The undo function allows a user to easily reverse actions that resulted in an
undesirable outcome on a graph. The redo function allows a user to reverse the
undo command on a graph.
Both the redo and undo functions maintain a history list of the actual actions
that can be reversed. The history list provides you with the option to reverse
any action in the list, not just the last action. For example, assume you change
the title, graph type, number of series, and number of categories on a graph.
After looking at the final graph you decide that a different graph type would
look better. You can undo only the graph type and do not have to also reverse
all actions prior to the graph type in the history list.
To undo or redo the last action on a graph:
1 In the graph report, on the toolbar, click the drop-down arrow on redo or
undo.
3 After a graph is saved, the redo and undo history lists are erased. In
addition, if a graph contains a page-by field, selecting a different page will
erase the history lists.
Graph Properties
185
Lesson Summary
In this lesson you learned:
Formatting involves changing the display of a report. You can format the
look and feel of your report by altering the number display, alignment, font,
border, and patterns for column and row axes, template object headers and
values, and subtotal headers and values.
Developer enables you to lock row and column headers on a grid report, so
while viewing report results, you can scroll horizontally and vertically
without losing sight of the row or column headers.
There are numerous graph properties that enable you to customize nearly
every aspect of a graphs appearance. You can choose from dozens of
different graph types and styles. After you choose an overall graph type and
graph style, other options enable you to adjust various aspects of the graph,
such as data labels, legend, axes, and titles.
Exercises: Report Style Manipulations in
Developer
Formatting and Autostyles
Overview
Change the formatting on your Region, Category, Year Sales report that you
created earlier so that the first few rows look like the following:
Save the formatting changes as a new autostyle and reuse it on the Category
Sales Report report.
You can use the detailed instructions that follow if you want help.
187
Detailed Instructions
1 In the Folder List, in the My Personal Objects folder, in the My Reports
folder, select your My Reports Exercises folder.
2 In the Object Viewer, double-click the Region, Category, Year Sales
report to run it.
Format the report
4 In the Format Cells window, click the Font tab and make the following
changes:
Font: Garamond
Size: 12
Bold: Yes
Color: Grey-25%
Font: Garamond
Font: Garamond
Size: 12
Bold: Yes
Color: Grey-25%
14 Click the Background tab and, from the Background style drop-down
menu, select Solid.
15 Click the Fill color drop-down menu and select Dark Red.
16 Click OK to close the Format Cells window.
17 In the report, right-click the Year header, point to Formatting, point to
Column Axis, and select Values.
18 Repeat the formatting changes in steps 13 to 16.
19 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
189
20 In the report, from the Grid menu, select Save AutoStyle As.
21 In the Save AutoStyle As window, navigate to the My Objects folder and
save your autostyle as My New AutoStyle.
default save location for a custom autostyle is My Objects. If you
The
save an autostyle to this folder, it will display in only your autostyle
22 Close the Region, Category, Year Sales report without saving it.
23 In the Folder List, expand the Public Objects folder, followed by the
Reports folder, followed by the Business Roles folder, and select the
Category Managers folder.
24 In the Object Viewer, double-click the Category Sales Report report to
run it.
25 In the report, from the Grid menu, point to Auto Style Selected and select
My New Autostyle. The report should now look like the following:
Thresholds
Overview
Configure thresholding conditions to format the US Revenues by Region Pivoting and Sorting report, as shown by the following image:
To make the report look like the above image, follow the formatting guide
below:
For Revenue greater than $2,500,000, substitute the data value with a
green diamond.
For Revenue between $1,500,000 and $2,500,000, substitute the data with
an orange diamond.
For Revenue below $1,500,000, keep the data value and make the font bold
and red.
191
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In Developer, in the Folder List, in the My Personal Objects folder, in the
My Reports folder, select the My Reports Exercises folder.
2 In the Object Viewer, double-click the US Revenues by Region Pivoting and Sorting report to run it.
Create thresholds
15 Under Settings, in the Color box, select Green and click OK.
193
195
Then, run the Inventory Received from Suppliers by Quarter, which can be
found by using the search functionality. Notice that there are more rows in the
report than you can view on one page. Your results should match the image
below:
Lock the column headers so that when you scroll down you will still be able to
see them.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Enable wordwrap
197
The column handles display above the row and column headers.
11 Use the column handles to adjust the width of the metric columns until
your report looks like the following:
12 Close the Average and Maximum Revenue per Call Center Transaction
report without saving it.
Locking columns headers
13 If the New Search window is not open, on the Tools menu, select Search
for Objects.
14 On the Name & Location tab, in the Named box, type Inventory Received
from.
15 In the Look in box, browse to the \MicroStrategy Tutorial\Public
Objects\Reports folder and click Find Now.
16 In the Search Results window, double-click the Inventory Received from
Suppliers by Quarter report to run it.
17 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
18 On the report, scroll down and notice that the column headers no longer
display.
19 In the report, on the Grid menu, select Lock Column Headers.
20 Scroll down the report and notice that the column headers now display.
21 Close the Inventory Received from Suppliers by Quarter report without
saving it.
22 Close the New Search window. If prompted to save the search, click No.
199
Bar Graph
Overview
Run the Yearly Revenue Growth by Customer Region report (which you can
find by using the search functionality) in graph view and make changes to the
graph display to make it easier to read. The graph initially looks like the
following:
It is not possible to distinguish the values for Percent Growth. To fix this, you
will change the graph type to split dual axes. You will also add data labels to the
bars to show the exact value for each data point. Finally, you will change the
title of the graph to Revenue and Percent Growth by Customer Region.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Search for report
201
20 Click OK.
203
25 In the Properties Categories list, expand Series and select Labels And
Values.
26 In the Series - Labels And Values pane, select the Show Data Labels check
box.
27 In the Labels Location drop-down list, select Outside Maximum.
Change the graph title
31 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
Save the report
You can use the detailed instructions that follow if you want help.
205
Detailed Instructions
1 In the Folder List, in the My Personal Objects folder, in the My Reports
folder, select the My Reports Exercises folder.
Create a copy of a report
2 In the Object Viewer, right-click the Sales by Quarter and Month report
you created earlier and select Copy.
3 In Developer, on the Edit menu, select Paste.
of the report is created and named Copy of Sales by Quarter
AandcopyMonth.
4 Right-click the Copy of Sales by Quarter and Month report and select
Rename.
5 Rename the report Sales by Quarter.
Remove Units Sold and Month from the report
6 In the Object Viewer, double-click the Sales by Quarter report to run it.
7 In the report template, right-click the Units Sold header and select
Remove from Report.
Ensure you select Remove from Report and not Remove from Grid.
8 To confirm that you want to remove the metric, in the pop up window, click
Yes.
9 To confirm that you want to re-execute the report, in the pop-up window,
click Yes.
10 In the report template, right-click the Month header and select Remove
from Report.
11 To confirm that you want to remove the attribute, in the MicroStrategy
Developer window that pops up, click Yes.
12 To confirm that you want to re-execute the report, in the MicroStrategy
Developer window that pops up, click Yes.
Switch to Graph View
14 In the Graph Type window, in the list of graph types, select Advanced.
15 Click the Gauge tab and select the Gauge:Gauge graph.
16 Click OK to close the Graph Type window.
Format the gauge graph
207
6
FILTERS
Lesson Description
This lesson introduces you to report filters. Understanding how to create
report filters is a crucial part of creating reports that retrieve only the data that
you want to analyze.
In this lesson, you will learn about the different types of report filters, see
examples of when you would use each type, and learn how to create them using
Developer.
209
Filters
Lesson Objectives
After completing this lesson, you will be able to:
Define the different types of report filters available in Developer and create
each type using the Filter Editor.
After completing the topics in this lesson, you will be able to:
Explain the purpose of a report filter and describe the differences between
report filters and view filters. (Page 211)
Use the Filter Editor to create and save report filters. (Page 215)
Define the different types of report filters, and create each type of report
filter using the Filter Editor in Developer. (Page 218)
Define the set operators available in the Filter Editor, and describe how you
can use them to combine multiple filter conditions inside a report filter.
(Page 226)
Filters
What Is a Filter?
After completing this topic, you will be able to:
Explain the purpose of a report filter and describe the differences between
report filters and view filters.
A report filter specifies the conditions that the data must meet to be included
in report results. If you are familiar with SQL syntax, the report filter is usually
equivalent to the WHERE clause in a SQL statement.
For example, consider the following diagram, which shows a table of data
filtered by three different report filter conditions:
Filter Conditions
As you can see, each report filter condition returns a different result set. You
need to know how to design the correct report filter in order to retrieve the
desired data.
What Is a Filter?
211
Filters
can open and close the Report Details window for a report by
You
selecting Report Details from the View menu.
The following illustration shows a report that is filtering on specific
regions, even though the Region attribute is not on the template.
Report Filter Based on Specific Regions
Filters
View FilterEnables you to create a filter on the fly, based only on those
objects that exist in the Report objects pane. (These objects may or may
not be displayed on the template.) View filters do not affect the SQL
generated to create a report. Rather, view filters are applied after the
data is retrieved from the warehouse, so only a subset of the result set
displays in the report view. You can create a view filter with the View
Filter window of a report, which you can also use to view the details of
existing view filter conditions.
filters and the Report objects pane are only available with
View
MicroStrategy OLAP Services. For more information on MicroStrategy
OLAP Services, see MicroStrategy OLAP Services starting on
page 279.
What Is a Filter?
213
Filters
The differences between report filters and view filters are summarized in the
following table:
Summary of Differences: Report Filters vs. View Filters
Filter Type
When Applied
Report Filter
Every time a
change is made;
often affects the
WHERE clause
of a SQL
statement
Any object,
whether or not it
is part of the
report
View Filter
None
Only objects in
the Report
objects pane
Filters
215
Filters
1 In the Filter Editor, in the Object Browser, navigate to the Data Explorer.
2 Double-click the hierarchy that contains the attribute on which you want to
qualify to display the list of attributes included in that hierarchy.
3 Double-click the attribute on which you want to qualify to expand it to its
list of attribute elements.
4 In the list of attribute elements, select the attribute elements you want to
see in the report results and drag them to the Filter definition pane.
Filters
Saving a Filter
To save a filter:
217
Filters
Attribute qualification
Set qualification
Each of the above listed types of report filters is described in the following
sections.
following sections include steps on how to create different types of
The
report filter using the Filter Editor. However, you can create the same
types of report filters by following the same steps from within the
Report Editor.
Attribute Qualification
Attribute qualification filters enable you to specify the conditions that attribute
elements must satisfy to be included in the report results.
There are various ways to qualify on an attribute. The following sections
explain how to create the most common types of attribute qualification filters.
Filters
1 In the Filter Editor, in the Object Browser, locate the attribute with
elements on which you want to qualify.
2 Drag the attribute to the Filter definition pane.
3 In the Attribute Qualification window, in the Operator drop-down list,
select either In list or Not in list, as shown below:
219
Filters
You can use filters to qualify on attribute forms. For example, you can create an
attribute form qualification on the Last Name attribute form of the Customer
attribute that only returns data for those customers whose last names begin
with the letter H.
To qualify on an attribute form:
1 In the Filter Editor, in the Object Browser, locate the attribute with the
attribute form on which you want to qualify.
must use the Data Explorer folder to browse to attribute
You
elements. There is a shortcut to the Data Explorer in the My
Shortcuts panel.
Filters
5 Below the operator drop-down list, in the text box, type the value you want
to use to qualify on the attribute form.
6 Click OK to close the Attribute Qualification window.
Date Qualification
This type of filter enables you to qualify on an attribute of the date data type.
For example, you can create a date qualification on the Day attribute to only
return data for days between January 1, 2012, and February 12, 2012.
To qualify on a date:
1 In the Filter Editor, in the Object Browser, locate the attribute of a date data
type on which you want to qualify.
2 Drag the attribute to the Filter definition pane.
3 In the Attribute Qualification window, in the Qualify On drop-down list,
select the ID attribute form.
4 In the Operator drop-down list, select an operator.
221
Filters
5 Below the operator drop-down list, in the second drop-down list, type a
date or use the drop-down list to select a date from the calendar, as shown
below:
Set Qualification
Set qualification filters enable you to restrict report results based on a metric.
You can qualify on a metric in the following ways:
The metric may or may not appear on the report template. For example, a store
manager might want to see sales numbers for products whose current
inventory levels are below a certain level. However, the report does not have to
display the inventory figures for those products.
Filters
To qualify on a metric:
1 In the Filter Editor, in the Object Browser, locate the metric on which you
want to qualify.
2 Drag it to the Filter definition pane.
3 In the set qualification pane, in the Function drop-down list, select the
method of qualificationMetric Value, Rank, or Percent, as shown below:
223
Filters
For example, you may be assessing customers and the items these customers
purchase. Specifically, you would like to find your most valued customers and
see what items they are purchasing in specific categories. In this example, Top
5 Customers by Revenue and Customers who spent more than $2,000, are
existing reports that are used to filter a third report, as shown below:
Reports As Filters
1 In the Filter Editor, in the Object Browser, locate the reports with which
you want to filter, and drag them to the Filter definition pane.
Filters
1 In the Filter Editor, in the Object Browser, locate the filters with which you
want to filter and drag them to the Filter definition pane.
225
Filters
Set Operators
After completing this topic, you will be able to:
Define the set operators available in the Filter Editor, and describe how you
can use them to combine multiple filter conditions inside a report filter.
When a report filter has multiple conditions, they are always combined with set
operators. Set operators govern the interaction between different filter
conditions. Whenever you have more than one condition in a report filter, you
can change the set operator to any of the following:
AND
OR
OR NOT
AND NOT
For example, suppose you have a filter with the following conditions:
Year = 2012
Region = Northeast
Filters
Set Operators
227
Filters
In this case, revenue generated in 2012 in any region (including the Northeast)
or revenue generated in all other years in any region except for the Northeast is
returned in the result set.
Filters
Finally, the following illustration shows the impact of the set operator AND
NOT on a result set:
Set Operator AND NOT
As shown above, revenue generated in 2012 in any region except the Northeast
is returned in the result set.
Set Operators
229
Filters
1 In the Filter Editor, add more than one condition to the Filter definition
pane.
2 In the Filter definition pane, right-click the set operator, point to Toggle
Operator, and select the desired set operator, as shown below:
Filters
Lesson Summary:
In this lesson you learned:
A report filter specifies the conditions that the data must meet to be
included in report results. If you are familiar with SQL syntax, the report
filter is usually equivalent to the WHERE clause in a SQL statement.
The Report Filter enables you to apply filter conditions to a report that
display in the SQL used to retrieve the report result set. The report filter is
created as part of the report and is saved with the report definition.
The View Filter enables you to create a filter on the fly, based only on those
objects that exist in the Report objects pane.
View filters do not display in the report SQL. Rather, view filters are applied
after the data is retrieved from the warehouse, so only a subset of the result
set appears in the report view.
Using existing report filter objects to define other report filters can be
thought of as embedding filters. It provides a useful means of managing
and leveraging existing report filter objects.
When a report filter has multiple conditions, they are always combined with
set operators. Set operators govern the interaction between different filter
conditions. If you have more than one condition in a report filter, you can
change the set operator to any of the followingAND, OR, OR NOT, and
AND NOT.
Lesson Summary:
231
Filters
Exercises: Filters in Developer
Creating a Filter
Overview
In this exercise, you will create a new folder in the My Objects folder and name
it My Filters Exercises. You will then create a filter for the year 2012 and save it
in the My Filter Exercises folder.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Create the My Filters Exercises folder
233
Detailed Instructions
Create the filter
2 In the New Filter window, leave Empty Filter selected and click OK.
3 In the Filter Editor, in the Object Browser, double-click the Products
hierarchy.
4 Double-click the Subcategory attribute.
5 Double-click Business.
6 Double-click Item.
7 Select Jump Start Your Brain and, holding down the CTRL key on the
keyboard, select The Joy of Work.
8 Drag both of the attribute elements you selected to the Filter definition
pane.
9 In the Object Browser, click Go one level up twice to get back to the list of
attribute elements for the Subcategory attribute.
235
Qualifying on a Metric
Overview
Create a filter for Revenue over $5,000,000. Run a report with this new filter
and a template that has Region in the rows and Revenue in the columns. The
final report should look like the following:
When you are finished, keep the report open for the next exercise.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Create a metric qualification report filter
237
27 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
28 Keep the report open for the next exercise.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In the report from the last exercise, on the toolbar, click Design View.
9 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
Save the report
239
7
METRICS
Lesson Description
This lesson focuses on creating metrics in Developer. Metrics define the
analytical calculations you want to perform against your data warehouse; they
produce the results that you analyze for decision-making purposes.
This lesson begins with a brief look at facts. Facts are the MicroStrategy objects
on which metrics are based. Distinguishing between facts and metrics and
understanding how facts are used to build metrics is essential to understanding
metrics.
In this lesson, you will learn how to create a variety of metrics, including
simple and compound metrics. More advanced metrics such as level metrics
and transformation metrics are covered in the MicroStrategy Developer:
Advanced Reporting course.
241
Metrics
Lesson Objectives
After completing this lesson, you will be able to:
Define the different types of metrics, and create them using the Metric Editor
in Developer.
After completing the topics in this lesson, you will be able to:
Define the components of a metric, and use the Metric Editor to create and
save metrics. (Page 252)
Metrics
What Is a Fact?
After completing this topic, you will be able to:
Explain the purpose of facts.
Facts are found in the metadata. In a MicroStrategy project, you build fact
schema objects that point to those columns that store fact data. For example,
the MicroStrategy Tutorial project has facts such as Revenue, Cost, and Freight
that point to columns in tables that store values for these measurements.
The image below displays some of the fact schema objects in the MicroStrategy
Tutorial project:
Fact Schema Objects
What Is a Fact?
243
Metrics
If you open a fact with the Fact Editor, you see the warehouse columns and
tables to which it is mapped. The following image displays the definition of the
Revenue fact in the MicroStrategy Tutorial project:
Fact Editor for Revenue Fact
As shown above, one of the columns to which the Revenue fact is mapped is the
ORDER_AMT column in the ORDER_FACT table. The fact definition dictates
where in the data warehouse the MicroStrategy Engine goes when it needs to
retrieve Revenue data.
more information on the Fact Editor and creating facts refer to the
For
MicroStrategy Architect: Project Design Essentials course.
Metrics
What Is a Metric?
After completing this topic, you will be able to:
Explain the purpose of metrics.
In the last section, you learned that a fact is a MicroStrategy schema object that
points to columns in the data warehouse that store fact data. A metric is an
object you create in Developer that performs a calculation on a fact. A metric
can employ everything from basic function, like sum, average, or standard
deviation to more advanced functions, like moving average, correlation, or
n-tiling.
provides over 200 built-in functions and operators for use in
Developer
creating metric calculations, including statistical, mathematical, and
financial calculations. You can view these functions in Developer in the
Schema Objects\Functions and Operators folder.
For example, if you want to see Average Revenue on a report, you need to build
a metric that averages the Revenue fact values. The formula for an Average
Revenue metric would look like the following:
Average Revenue Formula
What Is a Metric?
245
Metrics
To better understand the relationship between facts and metrics and how they
are used together to display calculations in reports, consider the following
example.
In your data warehouse, you have the following ORDER_FACT table, as shown
below:
ORDER_FACT Table
In this table, the ORDER_AMT column stores the revenue amount for each
order. You want to be able to access the revenue data in this table, so you create
a Revenue fact schema object that points to the ORDER_AMT column in the
ORDER_FACT table. The Revenue fact now enables the MicroStrategy Engine
to retrieve revenue data from the ORDER_AMT column of the ORDER_FACT
table.
Next, you want to view both average and total revenue figures on a report. To
calculate average revenue, you create an Average Revenue metric whose
formula is Avg(Revenue), where Revenue is the Revenue fact you created
earlier. The Avg function calculates the average revenue based on the values in
the ORDER_AMT column.
To calculate total revenue, you create a Total Revenue metric whose formula is
Sum(Revenue), where Revenue is again the Revenue fact you created earlier.
The Sum function calculates the total revenue based on the values in the
ORDER_AMT column.
Metrics
After you have created these two metrics, you then place them on a report like
the following:
Report with Metrics
The above report shows the average and total revenue by day. Each metric
employs a different calculation, but both are based on the same Revenue fact.
You can use the same fact to build any number of metrics. You can also create
much more advanced metrics that have more complex expressions and
perform more advanced calculations. You can even combine metrics to create
new metrics.
more information on creating basic metrics, see Metric Creation
For
starting on page 252. For more information on creating advanced
metrics, refer to the MicroStrategy Developer: Advanced Reporting
course.
What Is a Metric?
247
Metrics
Types of Metrics
After completing this topic, you will be able to:
Define the different types of metrics.
Simple
Nested
Compound
Derived
metrics are not covered in this lesson. For more information
Derived
on derived metrics, see the MicroStrategy OLAP Services lesson
starting on page 279.
Simple Metrics
As the name implies, simple metrics are the most basic metrics. You can use
simple metrics to create other types of metrics.
In their structure, simple metrics:
Sum(Cost){~}
Count(Customer){~}
Metrics
The {~} in these examples means the metric values are to be calculated at the
report level, the lowest attribute level on the report. For example, if the report
shows sales by year and month, the numbers will be calculated to reflect
monthly sales data. Creating metrics that use levels, conditions, and
transformations is covered in the MicroStrategy Developer: Advanced
Reporting course.
Nested Metrics
Nested metrics are metrics that perform multiple aggregations by placing one
calculation formula inside, or nested, in another. They provide a convenient
way to use metric functionality when tables in the data warehouse do not
include data at the level needed for a specific type of analysis. The result of the
inner calculation formula is stored in an intermediate table, which is then used
to calculate the result of the outer calculation formula. As such, you can obtain
and analyze data at levels not physically available in the data warehouse.
For example, you may want to see profit data averaged at the year level, but
existing fact tables provide only month-level profit data. You can use nested
aggregation to obtain the desired results. To calculate a yearly average for
profit, create a nested metric with the following metric formula:
Avg(Sum(Profit){~, Month}){~, Year}
In calculating the above metric, the MicroStrategy Engine first sums the profit
for each month and stores those results in an intermediate fact table. The
MicroStrategy Engine then uses those results to calculate an average profit for
each year.
the inner calculation formula, the {~, Month} applied to
InSum(Profit),
which means that the calculation formula is calculated
at the month level, regardless of what attributes appear on the report.
Types of Metrics
249
Metrics
May include one or more transformations, which are applied prior to its
calculation
Essentially, nested metrics are a special type of simple metric, in which one
simple metric formula is used to enable the calculation of another simple
metric. You only need nested metrics when the level at which data is stored in
the data warehouse prevents it from being calculated and analyzed at a desired
level. Nested metrics provide an alternative to modifying the physical data
warehouse tables.
more information on how to create nested metrics with the Metric
For
Editor, refer to the MicroStrategy Developer: Advanced Reporting
course.
Compound Metrics
Compound metrics are created by combining one or more metric objects with
one or more mathematical operators or constants. You can create compound
metrics using simple, nested, or other compound metrics.
Metrics
[Profit] *.15
The table below shows what can and cannot be used to define a compound
metric:
Components of Compound Metrics
Component
Allowed
Simple metrics
Nested metrics
Compound metrics
Numeric constants
Not Allowed
Types of Metrics
251
Metrics
Metric Creation
After completing this topic, you will be able to:
Define the components of a metric, and use the Metric Editor to create and
save metrics.
Metric Editor
When you choose to create a new metric, the Metric Editor opens displaying
several tabs and panes, as shown below:
Metric Editor
Formula Tab
This tab is used to define a metric. The Formula tab contains the following:
Metrics
Subtotals/Aggregation Tab
This tab is used to configure subtotal and dynamic aggregation settings for a
metric. The Subtotals/Aggregation tab contains the following:
Select the subtotals you want available for this metricEnables you to
specify which subtotals you want to be available for the metric when it is
placed on a report template that displays subtotals.
Metric Creation
253
Metrics
The Metric Editor also contains the Insert Function Wizard, which enables you
to define a metric formula using a wizard interface. You can access the Insert
Function Wizard from the toolbar above the metric Definition pane:
Insert Function Wizard
The Insert Function Wizard enables you to use any of the functions provided in
Developer, as shown in the table below:
Metrics
Metric Components
Metrics have the following components:
Metric Components
Formula
Level (Dimensionality)
Metric Creation
255
Metrics
Metric Components
Conditionality
Transformation
The formula and level (dimensionality) metric components are required for all
metric definitions. If you do not explicitly specify a level, the metric defaults to
report level. You can modify any of the above listed metric components with
the Metric Editor.
more information on the level, condition, or transformation
For
components of a metric, refer to the MicroStrategy Developer:
Advanced Reporting course.
Metrics
2 In the New Metric window, select Empty Metric from the list of metric
object templates.
3 Click OK.
To create a simple metric formula:
1 In the Metric Editor, on the Formula tab, in the Object Browser, locate the
fact or attribute you want to use in the metric formula and drag it to the
Definition pane.
default aggregate function applied to a fact is Sum. For example,
The
if you drag the Revenue fact to the Definition pane, the resulting
metric formula would be Sum(Revenue). The default aggregate
function applied to an attribute is Count.
2 Click the Subtotals / Aggregation tab and make changes to the settings as
needed.
more information on modifying the settings on the Subtotals /
For
Aggregation tab, see Subtotals/Aggregation Tab starting on
page 259.
Saving a Metric
To save a metric:
Metric Creation
257
Metrics
Metric Formatting
After completing this topic, you will be able to:
Define metric formatting properties, including the number format, header
display, and available subtotals.
Metrics
FontEnables you to format the font and color of the metric header or
metric values
1 In the Metric Editor, on the Tools menu, point to Formatting and select
Headers or Values.
2 In the Format Cells window, click the appropriate tab and format the metric
header or values as desired.
3 Click OK to close the Format Cells window.
Subtotals/Aggregation Tab
Subtotals
After you define a metric formula, you can determine which subtotals are
available for the metric. By default, all subtotals are available. The following
steps describe how to disable unwanted subtotals for a metric.
Metric Formatting
259
Metrics
subtotals you disable are not displayed, even when the metric is
The
used on a report where subtotals are selected.
Since the same item could have been sold on more than one date in more than
one month, simply summing across the Count Distinct (Items Sold) metric
values for each month can no longer be used to calculate an accurate Total
subtotal for the metric. In other words, 522 may not be the number of distinct
items that sold across the five months. Disabling subtotals for the Items Sold
metric will prevent an incorrect Total subtotal value from displaying.
Metrics
1 In the Metric Editor of the metric for which you want to disable the Total
subtotal, click the Subtotals / Aggregation tab.
2 In the Total subtotal function drop-down list, select None.
Total subtotal function setting enables you to either completely
The
disable the Total subtotal or simply change the aggregate function
used to calculate the Total subtotal values for a metric. Selecting
Default uses the default operator for that type of metric, which is
typically Sum. Selecting None disables the Total subtotal entirely.
You can also select from a variety of other aggregate functions (for
example, Average or Maximum) to calculate the Total subtotal
values.
Metric Formatting
261
Metrics
Smart Metrics
You may need to select the Allow Smart Metric check box for compound
metrics and some simple metrics (those that combine two or more calculation
formulas with arithmetic operators). When the Allow Smart Metric check box
is selected for a metric, it changes the manner by which its metric values,
including any of its subtotals, are calculated. Select the Allow Smart Metric
check box any time strictly summing the metric values does not produce a
meaningful Total subtotal value.
For example, consider the following report:
Yearly Sales without Smart Metrics Enabled
The Total value in the last column is incorrect; it is strictly a sum of the
percentages of the Ratio of Discount to Revenue metric. To calculate a
meaningful Total value for this metric, the Total value of the Discount metric
must be divided by the Total value of the Revenue metric, and to do this you
must select the Allow Smart Metric check box.
Metrics
The Allow Smart Metric setting ensures that the Total value for the Ratio of
Discount to Revenue metric is calculated using the Total values of the Discount
and Revenue metrics, rather than simply summing across the percentages of
the Ratio of Discount to Revenue metric. You can refer to this behavior as
smart totaling. If you enable smart totaling in this case, you get the following,
correct results:
Yearly Sales with Smart Metrics Enabled
1 In the Metric Editor of the metric for which you want to enable smart
totaling, click the Subtotals / Aggregation tab.
2 Select the Allow Smart Metric check box.
check box is only available for compund metrics and some
This
simple metrics (those that combine two or more calculation
formulas with arithmetic operators).
Metric Formatting
263
Metrics
Lesson Summary
In this lesson you learned:
Facts are values that represent business performance. They are typically
numeric and they can be aggregated to produce meaningful results.
Simple metrics are the most basic metrics. You can use simple metrics to
create other types of metrics.
Using the Format Cells window, you can specify formatting properties for a
metrics report header and for the numeric values it displays.
After you define a metric formula, you can determine which subtotals are
available for the metric. By default, all subtotals are available.
You should select the Allow Smart Metric check box any time strictly
summing the metric values does not produce a meaningful Total subtotal
value.
Exercises: Metrics in Developer
Create a Simple MetricCost
Overview
In this exercise, you will create a Cost metric and save it in a new folder called
My Metrics Exercises. Define the Cost metric as a sum of the cost fact and
format the values as currency with two decimal points. Format the values so
that negative numbers display in red with no negative sign or parentheses.
You can use the detailed instructions that follow if you want help.
Detailed Instructions
Create the My Metrics Exercises folder
Exercises: Metrics
265
7 In the Metric Editor, in the Object Browser, drag the Cost fact to the
Definition pane.
Default, MicroStrategy Developer uses Sum as the aggregation
Byfunction.
8 In the Metric Editor, on the Tools menu, point to Formatting and select
Values.
9 In the Format Cells window, on the Number tab, set the Category to
Currency, change Decimals places to 2, and set the Negative numbers to
display in red with no negative sign and no parentheses, as shown
below:
Detailed Instructions
Create the metric
Exercises: Metrics
267
5 In the Format Cells window, on the Number tab, set the Category to
Currency, change the Decimals places to 2, and set the Negative numbers
to display in red with no negative sign and no parentheses.
6 Click OK to close the Format Cells window.
Save the metric
Detailed Instructions
Create the report
1 In the Folder List, expand the My Reports folder and select the My
Reports Exercises folder.
2 In the Object Viewer, right-click in a blank area, point to New, and select
Report.
3 In the New Grid window, keep Blank Report selected and click OK.
4 In the Report Editor, in the Object Browser, double-click the Products
hierarchy.
Exercises: Metrics
269
Detailed Instructions
1 In the Folder List, select the My Metrics Exercises folder.
Exercises: Metrics
271
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In the Folder List, select your My Reports Exercises folder
2 In the Object Viewer, right-click the Item, Cost, Revenue report, and
select Edit.
3 In the Object Browser, double-click the Products hierarchy.
4 Drag Category to the left of Item in the template definition pane.
5 In My Shortcuts, click My Personal Objects.
6 In the Object Browser, double-click the My Objects folder.
7 Double-click the My Metrics Exercises folder.
8 Drag Profit Margin to the right of Cost in the template definition pane.
Save the report
15 In the Metric Editor, on the Tools menu, point to Formatting and select
Values.
16 In the Format Cells window, on the Number tab, set Category to Percent
and the Decimal places to 2.
17 Click OK to close the Format Cells window.
18 In the Metric Editor, click Save and Close.
Exercises: Metrics
273
26 In the report template, right-click the column header for the Profit Margin
metric, and select Edit to calculate the meaningful Total value for the Profit
Margin metric.
a Report Editor warning window opens, click OK to close the
Ifwindow.
27 In the Profit MarginMetric Editor, click the Subtotals / Aggregation tab.
28 In the bottom left corner of the Metric Editor, select the Allow Smart
Metric check box.
29 Click Save and Close.
30 In the Report Editor, click Save and Close.
31 In the Object Viewer, double-click the Compound MetricCompound
Metric- Profit Margin- Profit Margin report to run it.
32 Scroll to the bottom of the report and notice the change in the percentage
total for the Profit Margin metric.
Display Subtotals
Overview
There are several steps to this exercise. First, modify the Cost metric to disable
the Total and Average subtotals for the metric. Second, create a new report
using Item, Revenue, and Cost. Finally, display Average, Maximum, and
Standard Deviation subtotals on the new report.
The first few rows of the report should look like the following:
Exercises: Metrics
275
Detailed Instructions
Disable Total and Average subtotals for the Cost metric
Exercises: Metrics
277
8
MICROSTRATEGY OLAP
SERVICES
Lesson Description
This lesson describes the functionality provided by MicroStrategy OLAP
Services, an optional, add-on application to Intelligence Server, that enables
you to enhance the power of the reports you create.
279
Lesson Objectives
After completing this lesson, you will be able to:
Describe the features provided by MicroStrategy OLAP Services, including
report objects, view filters, and derived metrics. Use the Report objects pane,
and create view filters and derived metrics in reports.
After completing the topics in this lesson, you will be able to:
List the types of analysis that are provided by OLAP Services. (Page 281)
Add and remove objects to and from the template and the Report objects
pane. (Page 282)
281
Report Objects
After completing this topic, you will be able to:
Add and remove objects to and from the template and the Report objects pane.
In the report, drag objects from the Object Browser onto the template or the
Report objects pane.
the object is placed in the template definition pane, it is displayed
Ifwhen
the report runs. If the object is placed in the Report objects
pane, it is included in the generated SQL, but is not initially
displayed when the report runs.
In the report, right-click an object in the Object Browser, and select Add to
Rows, Add to Columns, Add to Page-by, or Add to Report Objects.
With MicroStrategy OLAP Services, when attributes are added to the Report
objects pane, they look like the following:
Report objects pane
In the above example, notice the + signs next to the attributes. By clicking the
+ sign, you expand an attribute to view its attribute forms. You can then
easily drag specific attribute forms of the attribute onto the template. For
example, to view just the last names of customers in the initial report view,
simply drag the Last Name attribute form of the Customer attribute from the
Report objects pane onto the template. As with objects, attribute forms that are
displayed on the template display in boldface type in the Report objects pane,
while those not displaying on the template display in plain text type.
Report Objects
283
In a report, drag an object from the template or the Report objects pane
into the Object Browser. Since you are changing the report definition, new
SQL will need to be generated.
In a report, drag an object from the template to the Report objects pane. If
you want to add the object back to the template, you can do so at any time
without regenerating any SQL.
View Filters
After completing this topic, you will be able to:
Create view filters.
A view filter enables you to further narrow down a report view, using only
those objects in the Report objects pane, (even if they are not displayed on the
template). When you add or change a view filter, the original report filter
remains intact. (Recall that report filter conditions are applied in the SQL of a
report when the report runs.) Only after a report result set is retrieved, are the
view filter conditions applied, so only a subset of the report results is displayed
in the report view.
Another key difference between report filters and view filters is that view filter
conditions of a report are local to that report. In other words, view filter
conditions cannot be reused or shared across reports like report filters. View
filters can, however, be saved with the report definition.
For example, the following report has Region and Call Center in the rows and
Revenue in the columns of the report view:
Regional Call Centers Revenue Report
The View Filter window, which is shown above the report grid, enables you to
create view filter conditions.
View Filters
285
1 In a report, if the View Filter window is not already showing, on the View
menu, select View Filter.
2 In the View Filter window, click Click here to start a new qualification.
View Filter window displays three parameters for creating view
The
filter conditionsField, Operator, and Value.
3 Click Field to display a drop-down list of objects that exist in your Report
objects pane.
4 Select the object with which you want to create the view filter condition.
you select an attribute, you will have the option to qualify on any
Ifattribute
form that is being displayed in the report view or to choose
from a list of attribute elements.
7 Click Apply to apply your view filter condition to the report view, as shown
below:
8 Click New .
9 Repeat steps 3 to 7.
you have multiple view filter conditions, the default set operator
When
is AND. Click a set operator and select AND, AND NOT, OR, or OR NOT
to change it. For more information on set operators, see Set Operators
starting on page 226.
View Filters
287
Derived Metrics
After completing this topic, you will be able to:
Create derived metrics.
Derived metrics are metrics you can create within a report, using only those
objects in the Report objects pane (even if they are not displayed on the
template), as well as functions and operators.
In their structure, derived metrics:
Are based on the attributes and metrics in the Report objects pane
4 In the right-hand side window, define the derived metric formula using the
available objects in the Report Objects folder combined with functions and
operators.
like in the Metric Editor, you can use the Insert Function
Just
Wizard to define a derived metric formula.
5 In the Input Metric Formula window, click OK to add the derived metric to
the report template or the report view.
6 To format the derived metric, right-click its header, and select Formatting.
a derived metric is created, you can remove it from the report
After
display like you would any other object.
Derived Metrics
289
By selecting a metric header in your report view, and then clicking the Insert
menu, you can insert a derived Percent to Total, Transformation, or Rank
metric based on your selected metric.
Built-In Derived Metrics
Lesson Summary
In this lesson you learned:
The Report objects pane displays all of the objects that are part of the report
definition.These are the objects retrieved from the data warehouse and
stored in the report cache.
A view filter enables you to further narrow down a report view, using only
those objects in the Report objects pane.
When you add or change a view filter, the original report filter remains
intact. Only after a report result set is retrieved, the view filter conditions
are applied, so only a subset of the report results is displayed in the report
view.
Derived metrics are metrics you can create with the Report Editor, using
only those objects in the Report objects pane.
Lesson Summary
291
Exercises: MicroStrategy OLAP Services
Using the Report objects pane to Add Attributes
Overview
Create a simple report with a report filter for June 2012 and use the Report
objects pane to include attributes and metrics in the report definition without
displaying them on the template. The first few rows of the initial report results
should look like the following:
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In the MicroStrategy Tutorial project, in the Folder List, select the My
Reports Exercises folder.
2 On the File menu, point to New and select Report.
3 In the New Grid window, keep Blank Report selected and click OK.
293
18 Drag the Last Name attribute form to the rows of the template, to the right
of the Call Center attribute.
295
Save the report in the My Report Exercises folder as Using View Filters. You
can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In Developer, in the Folder List, select your My Reports Exercises folder.
2 On the File menu, point to New and select Report.
3 In the New Grid window, keep Blank Report selected and click OK.
4 In the Report Editor, in the Object Browser, double-click the Products
hierarchy.
5 Drag Category and Subcategory to the rows of the template definition
pane.
6 In the Object Browser, click Go one level up.
13 In the Report Editor, on the View menu, select Grid View to run the report.
14 If you do not see the View Filter window, in the report, on the View menu,
select View Filter.
15 In the View Filter window, select the Auto-Apply changes check box.
16 In the View Filter window, click Click here to start a new qualification.
17 Click Field and select Category.
18 In the Operator drop-down list, select In list.
19 In the Value drop-down list, select Select Elements.
20 In the Select elements for the qualification from the list below window, in
the Available objects list, hold down SHIFT on the keyboard and select
Books and Electronics.
21 Click the arrow button to add them to the Selected objects list.
22 Click OK to close the Select elements for the qualification from the list
below window.
297
23 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
Save the report
You can use the detailed instructions that follow if you want help.
Detailed Instructions
1 In Developer, in the Folder List, in the My Reports folder, select the My
Reports Exercises folder.
2 In the Object Viewer, right-click a blank area, point to New and select
Report.
3 In the New Grid window, keep Blank Report selected and click OK.
4 In the Report Editor, in the Object Browser, double-click the Geography
hierarchy.
5 Drag Call Center into the rows of the template definition pane.
6 In the Object Browser, in My Shortcuts, click My Personal Objects.
7 In the Object Browser, double-click the My Objects folder.
8 Double-click the My Metrics Exercises folder.
9 Drag the Revenue metric to the columns of the template definition pane.
10 In the Object Browser, in My Shortcuts, click Public Objects.
11 In the Object Browser, double-click the Metrics folder.
12 Double-click the Sales Metrics folder.
13 Double-click the Transformation Sales Metrics folder.
14 Drag the Last Years Revenue metric to the right of Revenue in the
template definition pane.
15 In the Object Browser, in My Shortcuts, click Data Explorer.
16 In the Object Browser, double-click the Time hierarchy.
17 Double-click Year.
18 Drag 2012 to the Report Filter definition pane.
299
19 In the Report Editor, on the View menu, select Grid View to run the report.
The report results should look like the following:
26 In the Metric Name box, type Growth. The Input Metric formula window
should now look like the image below:
27 Click OK.
28 In the template, right-click the Growth metric header, point to Formatting,
and select Growth Values.
29 In the Format Cells window, on the Number tab, select Percent.
30 Click OK to close the Format Cells window.
31 Compare your results to the expected report in the Overview section at the
beginning of this exercise.
Save the report
301
9
PROMPTS AND SEARCHES
Lesson Description
This lesson explains how to create and use prompts and searches. Prompts are
powerful objects that you can incorporate into a report. With prompts, you can
create reports that allow end-users to define the report content at run time. In
this way, you can create fewer reports, while still satisfying the requirements of
many users.
In addition, this lesson describes how to search for objects in Developer. As
you may have already noticed, the number of objects in a project can multiply
rapidly, and the ability to search for objects can be quite useful.
Prompts and searches can also be used in combination with each other to help
manage a reporting environment that changes dynamically as objects are
created and deleted.
303
Lesson Objectives
After completing this lesson, you will be able to:
Define the different types of prompts, and explain how you can use search
objects inside prompts. Create prompts and searches in Developer.
After completing the topics in this lesson, you will be able to:
Explain the purpose of a prompt. Define the different types of prompts. Use
the Prompt Generation Wizard to create the different types of prompts.
(Page 305)
Create filter definition prompts, and use them in reports. (Page 310)
Create prompts on the fly within the Report Editor. Use the Re-prompt
report button to modify prompt answers in a prompted report. Choose the
appropriate settings when saving a report containing prompt objects in its
definition. (Page 328)
What Is a Prompt?
After completing this topic, you will be able to:
Explain the purpose of a prompt. Define the different types of prompts. Use the
Prompt Generation Wizard to create the different types of prompts.
What Is a Prompt?
305
Creating Prompts
You create all types of prompts with the Prompt Generation Wizard, which
guides you through the prompt creation process, as shown below:
Prompt Creation Wizard
You can control several aspects of how prompts display and how they function,
including the following:
Types of prompts
Types of Prompts
Using the following prompt types, you can create a prompt for nearly every
part of a report:
Level promptEnables you to specify the level for a metric. A level prompt
is not directly placed in a report. Instead, you embed it in a metric object.
more information on level prompts, refer to the MicroStrategy
For
Developer: Advanced Reporting course.
What Is a Prompt?
307
Option
Description
Web Options
Required Answers
The image below displays the Web Options window for a hierarchy prompt:
Web Options Window
The image below shows the page on the Prompt Generation Wizard where you
define default prompt answers:
Default Prompt Answers
What Is a Prompt?
309
Filter definition prompts are used within report filters to specify conditions
that data must meet to be included in report results.
311
The procedures below covers the steps to create two types of filter definition
prompts: the Qualify on an Attribute prompt type and the Qualify on a Metric
prompt type. For detailed steps on the other types of filter definition prompts,
refer to the Basic Reporting Guide.
Qualify on an Attribute
This type of filter definition prompt can be used to create a more focused
prompt than the hierarchy prompt. After creating this type of filter definition
prompt, the user can qualify on only the attribute built into the prompt (rather
than from any attribute in a hierarchy) or any attribute that is returned by a
specific search object.
313
Only the option to qualify on the attribute built into the prompt is described
below, but the procedure for creating the other type of attribute prompts is
similar.
To create a qualify on an attribute prompt:
Select the Max number of elements for selection check box if you
want to specify the maximum number of attribute elements a user is
allowed to select per qualification. For example, a user is qualifying on
the Year attribute, and he is selecting from a list that contains the
following elements2010, 2011 and 2012. If this setting is set to 2, the
user can only select two (or less) of these year elements.
Select the Prompt answer required check box if you want to require
users to answer the prompt before running the report.
315
Qualify on a Metric
This type of filter definition prompt can be used to enable a user to qualify on a
metric. The user can qualify on the metric built into the prompt or any metric
that is returned by a specific search object. Users can qualify on the value, rank,
or percentage of the metric.
option to qualify on the metric built into the prompt is described
The
below, but the procedure for creating the other types of metric prompt is
similar.
AddOpens the Select Objects window, which enables you to select the
objects for the list
an element has been selected, this button is replaced by
After
Modify, which opens the Select Objects window so you can modify
the previous selection.
6 On the Provide general information for the prompt page, in the Display
properties section, define the following settings:
Select the Prompt answer required check box if you want to require
users to answer the prompt before running the report.
317
1 In the Report Editor, in the Object Browser, locate the filter definition
prompt you want to use and drag it to the Report Filter definition pane.
You can also drag it to the Filter definition pane of the Filter Editor.
When you run the report, a window that looks similar to the Filter Editor
displays. If the filter definition prompt is required, you must answer (resolve)
the prompt before the report runs.
To resolve a filter definition prompt:
Object Prompts
After completing this topic, you will be able to:
Create and use object prompts in a report.
Object Prompts
319
AddOpens the Select Objects window, which enables you to select the
objects for the list
an element has been selected, this button is replaced by
After
Modify, which opens the Select Objects window so you can modify
the previous selection.
5 Click Next.
6 On the Provide general information for the prompt page, in the Display
properties section, define the following settings:
Select the Minimum objects check box if you want to specify the
minimum amount of objects a user is allowed to select, then set that
number.
Select the Prompt answer required check box if you want to require
users to answer the prompt before running the report.
Object Prompts
321
12 In the Save As window, navigate to the location in which you want to save
the prompt.
13 Type a name, and click Save.
1 Create the object in which you want to use the object prompt. It may be a
report, a template, a metric, or another MicroStrategy object.
2 In the object editor, with the Object Browser, locate the object prompt and
drag it to the appropriate section of the object editor. For example, if your
object prompt presents a list of metrics, drag it to the columns or rows of
the template definition pane in the Report Editor. If your object prompt
presents a list of report filters objects, drag it to the Report Filter definition
pane in the Report Editor.
3 Save the object.
When you run the report, a prompt resolution window opens listing the objects
from which you can choose to answer the object prompt. If the object prompt is
required, you must answer (resolve) the prompt before the report runs.
To resolve an object prompt:
1 Create an object prompt that uses a predefined list of filters. Choose a wide
variety of filters based on many different aspects of the MicroStrategy
project. Give a title and description to the object prompt. Save and close it.
object prompt can contain only one object type. Therefore, you
Each
must create a separate object prompt for each object type.
2 Create another object prompt that uses a predefined list of attributes. Offer
a variety of attributes from every hierarchy. Give this object prompt a title
and description. Save and close it.
3 Create a third object prompt that uses a search object to find every metric
object. This assumes that you want to prompt on every metric available in
the project. Otherwise, you could use a predefined list of metrics. Give this
object prompt a title and description. Save and close it.
4 Create a new report. Add the first object prompt to the filter definition pane
in the Report Editor. Add the second and third object prompts to the
template.
5 Run the report and notice how the combination of prompts act like a report
building wizard.
Object Prompts
323
Value Prompts
After completing this topic, you will be able to:
Create and use value prompts.
Value prompts are typically used as part of a filter definition, but they may also
be used as part of a metric formula. You can prompt on a date, a numeric value,
a text string, a big decimal value, or a long value.
long value prompt is not enabled by default. To enable the long
The
value prompt, in Developer, from the Tools menu, select My
The following is an example of a text value prompt that prompts users to type
select a date:
Text Value Prompt
Value Prompts
325
Select the Maximum value check box if you want to set the highest
value allowed for the prompt answer, then set that number.
Select the Prompt answer required check box if you want to require
users to answer the prompt before running the report.
If you click on the drop-down list, a calendar displays, from which you
can select a specific date.
To set a dynamic date, that is, a date or time range that meets specific
offset conditions, click Date Editor.
Date prompts can be used in any place where you would normally specify a
date, such as in a filter that qualifies on an attribute of a date data type.
Numeric prompts can be used in any place where you would normally
specify a number, such as in a metric qualification.
Text prompts can be used in any place where you would normally specify a
text string, such as in an attribute form qualification.
Big decimal prompts can be used in any place where you need to qualify on
a high precision value (up to 38 digits), such as an attribute qualification on
the ID attribute form.
1 Create the object in which you want to use the value prompt. (It may be a
report filter or a metric.)
2 In the object editor, with the Object Browser, locate the value prompt, and
drag it to the appropriate section of the object editor. For example, if you
are using a date prompt in a date qualification filter, drag the date prompt
beside the Value box in the Attribute Qualification window.
3 Save the object.
When you run the report, a prompt resolution window opens. If the value
prompt is required, you must answer (resolve) the prompt before the report
runs.
To resolve a value prompt:
Value Prompts
327
List all <attribute>Creates a prompt that lists all the elements of the
selected attribute. At run time, the user selects which elements to
include.
can either type in the name of the filter or click the browse
You
button.
The Prompt Generation Editor is shown below:
4 Click OK.
When you click the Re-prompt report button, the prompt selection window
opens. You can then make a new selection of prompt answers, which will be
applied when the report re-executes.
329
StaticYou will no longer be prompted when you run the report in the
future. The prompt answers you selected are saved to the report definition
and used every time you run the report in the future.
PromptedYou will continue to be prompted every time you run the report
in the future. You can choose whether to be prompted for just the filter
definition prompts, just the template prompts, or both.
331
Single: Only one personal answer can be saved. When the prompt is used
again (on this report or a different one), the personal answer is displayed. A
user can keep the personal answer, or add or delete selections. The user can
save changes, but only one personal answer can be saved for the prompt.
For example, you run a report with the Year attribute and Revenue metric
on the template and an attribute element prompt on the Year attribute. The
user has selected the Remember this answer check box and answered the
prompt with year 2011 and 2012. When the user runs the report again, 2011
and 2012 prompt answers will be displayed as the default prompt answers,
as shown below:
Single Element Prompt Display
Multiple: Multiple user answers can be saved enabling different answers for
the same prompt. When the prompt is used again (on this report or a
different one), the personal answers are available, and the user can select
one of them or answer the prompt manually. The image below shows
multiple saved answers:
Multiple Element Prompt Window
333
You can edit your previous prompt answers by clicking Edit Answers.
4 Click Finish.
335
Searches enable you to search for a specific object or a collection of objects that
meet certain criteria. You can restrict the search results by name, ID, and
location, the date range during which objects were created or last modified,
object type, and object owner. The more criteria you specify, the smaller the
number of objects that will meet those criteria and be returned.
By default, you can use the Search for Objects window to restrict search results
by one or more of the following criteria:
Object type
Object owner
Object ID
Search By Components
You can search for objects containing particular objects or objects contained by
particular objects by enabling two additional tabs using the Search Options
window.
To activate the Contains and Contained By tabs:
1 In the Search for Objects Editor, on the Tools menu, select Options.
2 In the Search Options window, select the Show Contains and
Contained By tabs check box.
3 Click OK to close the Search options window.
can search for objects that are contained by particular objects,
You
rather than creating an independent search.
To view components of an object using the search by components shortcut:
337
Saving Searches
You can save searches just like any other MicroStrategy object to use them
again later or incorporate them into prompt objects.
of the prompts described in the previous topic can use the results
Many
of a search to generate a list of potential prompt answers.
To save a search:
Search-based Prompts
You may recall from the previous topic that the Prompt Generation Wizard has
the option to reference a search object in defining certain types of prompts.
Using searches in prompts enables you to limit a possibly overwhelming set of
potential prompt answers. It also allows you to make the set of potential
prompt answers more dynamic, since the set of potential prompt answers is the
list of objects returned by the search object, rather than a static list.
For example, suppose you want to create a report which template includes an
object prompt that allows users to select from a list of metrics which name
contains the word Revenue. You first create a search that returns a list of
metrics which name contains the word Revenue. You then incorporate the
search object into an object prompt, which you then place on the report
template. Every time the report runs, the search object executes to return the
latest list of metrics with the word Revenue, which is then presented to the
user in the prompt answer window. This way, the user always selects from the
latest list of revenues.
339
Lesson Summary
In this lesson you learned:
You can make different prompt selections each time you run the report.
You create the following types of prompts with the Prompt Generation
Wizardfilter definition prompt, object prompt, value prompt, and level
prompt.
Filter definition prompts are used within report filters to specify conditions
that data must meet to be included in report results.
Object prompts enable you to create very versatile reports. With an object
prompt you can qualify on a specified list of MicroStrategy objects or any
MicroStrategy object that is returned by a search object.
Value prompts are typically used as part of a filter definition, but they may
also be used as part of a metric formula. You can prompt on a date, a
numeric value, a text string, a big decimal value, or a long value.
You can also create prompts on the fly within the Report Editor.
When you save a prompted report after answering prompts and running
the report, you are presented with additional save options. You can save the
report as a prompted or static report.
You can save the prompt answers and reuse them when you run the same
report again.
You can restrict the search results by name, ID, and location, the date range
during which objects were created or last modified, object type, and object
owner.
Exercises: Prompts and Searches
Create Filter Definition Prompts
Overview
Create the following three prompts and use them in the report filter of a report
that has Item and Revenue on its template.
Prompt on the Quarter attribute element listUsers see the entire list of
elements, and 2012 Q4 should be the default answer. Answering the
prompt is required.
Books
You can use the detailed instructions that follow if you want help.
341
Detailed Instructions
Create the My Prompts Exercises folder
18 In the Open window, in the Time folder, select the Quarter attribute.
19 Click OK.
20 On the Select the attribute to be used in the prompt page, click Next.
21 On the Reduce the number of elements available to the user at runtime
page, keep the List all elements (no restriction) option selected.
22 Click Next.
23 On the Provide general information for the prompt page, click Next.
24 On the Select default prompt answer(s) page, click Add.
25 In the Select Objects window, in the Available objects list, select 2012 Q4.
26 Use the > button to add it to the Selected objects window.
27 Click OK to close the Select Objects window.
28 On the Select default prompt answer(s) page, click Finish.
29 Save the prompt in the My Prompts Exercises folder as Choose from all
elements of Quarter.
Create a prompt on the Revenue metric
343
50 Drag the Revenue metric into the columns of the template definition pane.
51 In the Report Editor, click Run Report.
For the first prompt, in the left window, double-click the Category
attribute to expand it. Drag Books to the right window and click Next.
For the second prompt, notice that the default answer, 2012 Q4, is
already selected. In the left window, select 2012 Q3 and click the >
button to add it to the right window. Click Next.
For the third and final prompt, in the set qualification pane, in the
Parameters section, change the Operator to Greater than and in the
Value box, type 20000.
Click OK.
53 Compare your results to the expected results in the Overview section at the
beginning of this exercise.
Save the report with a prompted filter
345
The metric prompt should enable you to choose either the Average Revenue
metric or the Units Sold metric.
The attribute prompt should enable you to select any attribute returned by
the Search for all objects of type Attribute search. (This search object is
already built for you and can be found in the Public Object\Searches
folder.)
This original report should use an empty report filter (no filter criteria) and
be named Prompts-Original.
When you run the report, select Units Sold, Category, and Year, so the report
results look like the following:
You will then save the report as prompted with the name Prompts-Template
Prompted. Run the report again, and save the report by selecting the static save
option. You will name the static version of the report Prompts-Static.
Answer: When you run the report Prompts-Original it will prompt you and will
not contain any previously-selected metrics or attributes. When you run
Prompts-Template, you will still be prompted, however, the metric and
attributes you saved will already be selected when the prompt opens. When
you run the Prompts-Static, you will not be prompted. The report will open up
with the metrics and attributes you previously selected.
Answer: Prompts-Static.
What does this tell you about the different save options?
_______________________________________
_______________________________________
_______________________________________
Answer: You can either save a report to run a new prompt every time, without
any previously selected report objects. Another option is to set a prompted
report so that the previously selected objects are provided as default answers.
The third option is to save the report as a static report which will not prompt
the user and instead will run using the previously selected objects.
You can use the detailed instructions that follow if you want help.
347
Detailed Instructions
Create a prompt for sales metrics
11 In the Save As window, save the prompt as Choose from a list of metrics.
Create a prompt for attributes
17 In the Open window, select the Search for all objects of type Attribute
search object.
18 Click OK.
19 In the Prompt Generation Wizard, click Finish.
20 Save the prompt in the My Prompts Exercises folder as Choose from a list
of attributes.
Create a report using the object prompts
349
27 Drag the Choose from a list of attributes prompt to the rows of the
template definition pane.
default, the sequence in which you add prompts to a report
Bydetermines
the order in which the prompts display when the user
runs the report. However, you can change this order by selecting
Prompt Ordering from the Data menu. In the Prompt Ordering
window, use the arrow keys to re-order the prompt objects in the
report.
the this prompt and the next prompt, notice that the answers
For
you selected the last time now display as the default answers.
47 Click Next.
48 Click Finish.
Save and run the report with the static save option
351
Creating this prompted report is a little different than the previous reports
because the prompt is not created as an independent object. Instead, you will
create the prompt from within the Report Filter definition pane.
When you create the report filter, you will see the following screen:
Note that there is a difference between the value prompt (created by clicking
Simple Prompt):
Using the Simple Prompt button, you can create a value prompt that allows the
user to only enter a date value for the hire date. Using the Prompt button, you
can create an attribute filter definition prompt that enables the user to select
the operator and enter a date value for the hire date.
You can use the detailed instructions that follow if you want help.
Detailed Instructions:
1 In Developer, on the File menu, point to New and select Report.
2 In the New Grid window, keep Blank Report selected and click OK.
3 In the Report Editor, in the Object Browser, double-click the Geography
hierarchy
4 Drag the Employee and the Hire Date attributes to the rows of the
template definition pane.
353
5 In the Object Browser, drag the Hire Date attribute to the Report Filter
definition pane.
6 In the Attribute Qualification window, from the Qualify On drop-down list,
select ID.
7 In the Operator drop-down list, select Less than.
8 Click Simple Prompt:
14 In the Date and Time Editor, keep the Static date option selected and enter
1/20/2012 as the date value.
355
A
MICROSTRATEGY TUTORIAL
Appendix Description
This appendix provides information on the MicroStrategy Tutorial project,
including the data model and physical warehouse schema.
357
MicroStrategy Tutorial
6 To return to the default view, on the View menu, select Auto arrange.
7 To save the layout view of the hierarchy, on the File menu, select Save
layout. The next time you open the Hierarchy Viewer, it displays the saved
view.
The MicroStrategy Tutorial data model consists of the following hierarchies:
Geography
MicroStrategy Tutorial
Customers
Time
Products
Geography Hierarchy
359
MicroStrategy Tutorial
Customers Hierarchy
MicroStrategy Tutorial
Time Hierarchy
Products Hierarchy
361
MicroStrategy Tutorial
MicroStrategy Tutorial
363
MicroStrategy Tutorial
5 To change display preferences for the physical view, on the Options menu,
select any of the following options:
Show joinsEnables you to select whether to connect the tables to
represent the joins between the warehouse tables
Use circular joinsEnables you to select whether to use circular joins
Show column data typesEnables you to select whether to show the
data type and size for each column
Show table prefixesEnables you to select whether to display the table
prefix as part of the table name
6 To switch back to the logical view, on the View menu, select Logical view.
7 To view the entire schema in the window, on the View menu, select Fit in
window.
can rearrange the tables by dragging them. Rearranging the tables
You
does not affect the relationships or joins, but it enables you to view the
tables in a way that is meaningful to you.
8 To return to the default view, on the View menu, select Auto arrange.
9 To save the layout view of the tables, on the File menu, select Save layout.
The next time you open the Table Viewer, it displays the saved view.
10 To copy the layout view, on the File menu, select Copy as Metafile (.wmf).
MicroStrategy Tutorial
Geography
Customers
Time
Products
Fact tables
365
MicroStrategy Tutorial
Geography Schema
MicroStrategy Tutorial
Customers Schema
367
MicroStrategy Tutorial
Time Schema
MicroStrategy Tutorial
Products Schema
369
MicroStrategy Tutorial
Index
INDEX
A
administration
Database Instance Manager 46
Schedule Manager 46
User Manager 46
advanced sort 116
attribute 66
attribute elements 30
attributes 29
C
cache 282
change journaling 75
consolidation 66
cross-tab 65
Cube Analysis, Derived Elements, Report
Objects, View Filter, Derived
Metric 281
custom group 67
D
data pivoting 106
371
Index
E
editors
Filter Editor 215
Metric Editor 252
Report Editor 63
Search Editor 336
ETL process 35
exporting 127, 139
F
Fact Editor 244
facts 31
filter 61
Filter Editor
layout 215
filters
attribute qualification filters 218
creating 216
embedded filters 225
filter definition prompts 310, 340
Filter Editor 215
filter qualifiers 225
set operators 226, 231, 285
folder list 48
folders
Data Explorer 47
History 46
My Personal Objects 46
Public Objects 46
Schema Objects 47
Function Wizard 254
G
grand totals 109
graphs
categories and series 180
372
H
history list subscription 130
L
lesson objectives
Filters 210
Introduction to MicroStrategy
Developer 38
Metrics 242
Prompts and Searches 304
Report Manipulations 94, 158, 280
Reports 60
M
menus
Administration 51
Edit 51
File 51
Go 51
Help 51
Schema 51
Tools 51
View 51
Window 51
metadata database 26, 35
metric 67
removing columns 75
Metric Editor 252
layout 252
metrics 32, 34, 245
components 255
compound 250
compound metrics 250, 264
creating 256
creation 252
formatting 258, 259
formula 256
Metric Editor 252
nested 249
saving 257
simple 248
simple metrics 248, 288
subtotals and 259, 264
types 248
MicroStrategy
Architect 40
MicroStrategy Administrator 39
MicroStrategy Agent 39
MicroStrategy Architect 39, 40
MicroStrategy Developer
components 39
toolbar 52
MicroStrategy Intelligence Server
benefits 44
MicroStrategy reporting terminology 28
mobile device subscription 134
N
notes 136, 141
O
Object prompts 319
object viewer 48, 390
objects
creation 52, 54
save 54
saving 54, 72
schema, objects
application, objects
configuration 54
373
Index
P
page-by 103
creating page-by fields 104
printing 125, 139
Project Source, project 42
project sources
logging in 45
projects
accessing 46
default structure 46
prompt
object 67
prompts 305
creating 306
filter definition 306, 310
filter definition prompts 310, 340
level 307
local, local prompts 328
object 307, 319
object prompt 307, 320, 340
required answers 308
save and reuse answers 309, 331
saving reports with 330, 340
search-based 339
types of 306
value prompt 307, 325, 340
web options 308
Q
quick sort 115
Index
R
removing metric column 75
report design
change journaling 75
removing metric column 75
report details properties 75
filter details - contents 77
filter details - other 77
general 76
template details 78
report details properties 75
Report Editor 63, 288
layout 63
report filter 67
report manipulation
adding notes 136, 141
save and reuse prompt answers 331
Report Objects 282
report views
Design View 74, 79
Graph View 74, 79
Grid View 74, 79
SQL View 74, 79
reporting terminology, MicroStrategy 28
reports 29, 61
adding attributes 68
adding metrics 69
create 64, 68
create, reports
view, reports
save 63
creating 68
details properties 75
display views 74, 79
exporting 127, 139
printing 125, 139
prompts and 330, 340
Report Editor 63
374
run 74
running 74
save 72
saving 72
reports, template 61
re-prompting 329
S
save and reuse prompt answers 331
Schedule Manager 46
search
by object ID 338
Search Editor 336
searches 336
prompts and 339
saving 338
Search Editor 336
set operators 226, 231, 285
shortcut bar 49
shortcut metrics 290
smart metrics 262
sorting 115
advanced sort 115
quick sort 115
source systems 35
subtotal 108
subtotals
displaying 108
grand totals 109
T
tabular 65
template 65
Template Editor 65
templates
adding attributes 68
adding metrics 69
2013 MicroStrategy Inc.
Index
cross-tab 65
defining 65
tabular 65
Template Editor 65
threshold 165, 186
toolbar buttons
Display Outline Results 122
Drill 98
Print Preview 125
Run Report 74
View Pages 104
U
update cache subscription 132
User Manager 46
V
value prompts, prompts
value 324
view filter 285
375
Index
376