Before proceeding with the design of indicators, filters, prompts, and see how to develop templates for our reports, we will see a bit more in detail issues that have to do with the attributes of the dimensions (which we saw were set in the previous entry in the blog ), and that will be useful in developing the project.
Hierarchies allow us to browse and attributes. In Microstrategy, we have two types of hierarchies:
• System hierarchy: The hierarchy of the system, including the defined relationships between the attributes of the project.This hierarchy is not necessary to define, but the tool automatically generates Desktop to create the project (which was built using the Architect).
This is the default hierarchy, and contains all the attributes of the project, part of the schema definition. After creating the project, is the only hierarchy that exists. The system hierarchy is not edited, but is updated each time you add or remove child or parent attributes using the attributes editor or architect, or add new attributes to the project.
The hierarchy of the system is useful for determining the relationships between all objects in the project (you can navigate through it to see the values of attributes and how they relate to each other).The attributes defined in the hierarchy of the system does not need are defined in a user hierarchy. The attributes of the hierarchy of systems not using in user hierarchies are still available for use in reports, filters, or consolidations.
• User hierarchy: user hierarchies are groups of attributes and relations between them, coupled in a manner that is meaningful in the context of analysis.Not necessarily have to follow the logical data model. Moreover, unlike the hierarchy of system allows us to define limitations to the number of displayed values, the values set filters to view or define an entry point, which will be the attribute which will position us to use the hierarchy (for example, navigating or performing filtering.)
For example, we create a hierarchy that includes attributes Year, Quarter, Month and Day. When we surf the attributes with the Data Explorer, double-click on the year, we appear quarterly, then monthly and so on.
In our project we will create all necessary hierarchies to allow navigation through the different attributes of the dimensions.
User hierarchies are available when we will navigate the data in the reports and documents of Microstrategy, and we will provide the functionality Drill Up and Drill Down among the attributes that define within it.They are therefore an indispensable element in shaping the system, they are the starting point to take full advantage of dimensional navigation. For example, if in the above example we are viewing the attribute Quarter, we can sail up (drill up) by the hierarchy until, or browse down (drill down) to the month, or switch to another and change the navigation jeranquia .
They are the only kind of hierarchy can be defined by the user and may create all the hierarchies that may be required within a project.We will have to think of all the hierarchies required to cover all needs within the business model and outline the company's data warehouse.
Are schema objects that can be defined using attributes. Used to run time series analysis and period to date, current period against the previous period or periods changing analysis.The transformations we define the attributes (for example, in the image, we are using a date, which we subtract 14 days). This will set a variable value that depends on the value of the attribute to which it is related, and then use to create the indicators.
For example, we have a number called Net Income (estimated from net income of fact), we show current net sales in the period we are analyzing.If we create an indicator called Net Income for 14 days (and we associate the transformation defined in the image) when using the indicator in an earnings report will show 14 days earlier. Transformations are a very powerful and allow us to easily perform the analysis of time series.
All objects seen so far, attributes, events, user hierarchies and the changes are part of the schema objects, and are the starting point for the construction and development of our Business Intellingence system. Let's see what elements we can build with them:
Before proceeding, I recommend you view the video produced by speaking Microstrategy design of indicators, filters and selections.
Indicators are MicroStrategy objects representing business measures and key performance indicators.From a practical standpoint, the indicators are the calculations on data stored in the database and the results are shown in a report. They are similar to formulas in a spreadsheet program. It would not be an exaggeration to say that the core of virtually all reports are indicators.Most of the decisions made about the other objects to be included in a report depend on the indicators used in the report.
In particular, the indicators define the analytical calculations are performed with the data stored in the data source. An indicator is composed of facts and data source of mathematical operations to be performed on those facts to, thus, to carry out a meaningful analysis of business results.
In the indicators can be defined several things, but the key element is the formula that determines its value. A metric formula can consist of facts from the data source (as in the example above), business attributes of the source data or other indicators have already been created.The following examples of indicators show different features of these formulas:
The formulas can contain mathematical functions and has a wide range Microstrategy of them to allow for multiple types of calculations:
Besides the formula, we can indicate on the properties of the indicator:
In the Tutorial project that offers Microstrategy can see examples of how to define indicators for all possible types, from functions to manipulate dates, strings or numbers, statistical functions, financial, OLAP and data extraction functions for DataMining.
The filters allow us to restrict the values to different elements of our system.For example, we set a filter on the attribute year and select a particular value (eg 2009), and to run a report with this filter, only recover the values of that year. We could also have defined the filter dynamically, so that when you run the report, we aparecezca a list of years and choose the one that we will discuss (it will prompt filter).
You can also define filters on the indicators, for example, to limit values that we do not appear to be less than a value or the like.
A prompt is a question that makes the user running a report.Any report may contain prompts. This information allows us to give dynamism to the reports and to run the same report with different performance criteria. Prompts can be mandatory (that is essential to indicate a value) or optional.
Prompts are used to select the filter conditions at the time of report execution.It can dynamically determine an attribute, an attribute element selection, metrics and other objects that may be included in a report. Prompts can be used along with other selections static filters, and can add a report as many as needed.
We have the following types of prompts:
Templates are objects that serve as a basis for building the reports. Define the layout that will have the report. The templates specify the jointdata to which the report must retrieve the data source and also determine the structure in which information is displayed in the report's findings.
When you create a template, place the different objects in Microstrategy, with which we can use the following attributes, metrics, filters and prompts (in addition to custom groups and bindings).
Basically, we have two types of layout:
The templates will be the basis for building reports.
We passed over the main components that form the basis of Microstrategy BI system.Elements are much more complex than we have seen, with many options and features that will give us many possibilities in order to cover our requirements.
I recommend a close reading of the documentation provided by MicroStrategy to know each of the elements:
Seen everything we can highlight:
With that seen at least a few basics to start working with Microstrategy 9, define the basic elements and then use (such as user hierarchies, indicators, filters and prompts) and to further deepen the other components of the tool .