-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Business Intelligence with MicroStrategy Cookbook
By :

Most of the time, we filter attributes based on values, be it an element or a list of elements, always belonging to the same attribute (Year = 2007; Product in list….). There are cases when we want to look at two separate attributes to see if they match or not. The classic example being the order date and the ship date (order date = ship date), to control if our warehouse is preparing the orders during the same day they are processed. That example is way too common, so we'll complicate the things a bit. Our Sales Manager wants to know which orders from the resellers were originated by employees outside the sales territory where they belong (???). In other words, who are those employees who sell in a sales territory where they should not.
The FactResellerSales
table has a column SalesTerritoryKey
, and the Employee
table also has SalesTerritoryKey
, so we will create two attributes: one Reseller SalesTerritory
and the other Employee...
Change the font size
Change margin width
Change background colour