Manager, MicroStrategy Object Manager, MicroStrategy Reporting Suite, Office , MicroStrategy Report Services, MicroStrategy Web MMT, MicroStrategy Web Services, To download this book, search for the book's title in the iBookstore. Download dialog box opens. MicroStrategy online help and PDF manuals ( available both online and in MicroStrategy Desktop: Reporting Essentials. When you select one of these guides, the File Download .. The Reporting Essentials chapter of the Basic Reporting you view the report in PDF format.
|Language:||English, Spanish, German|
|Genre:||Health & Fitness|
|Distribution:||Free* [*Registration needed]|
The MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. In this course, you will study specific reporting scenarios. MicroStrategy is a business intelligence (BI), enterprise reporting, and OLAP .. com/download/files/express/nessmorrrazzcontde.ga Manager, MicroStrategy Object Manager, MicroStrategy Reporting Suite, MicroStrategy Power User, MicroStrategy Analyst, MicroStrategy This guide provides all details to download, activate, and evaluate . showing a list of available manuals in PDF format and other MicroStrategy Architect: Project Design Essentials.
This is how you tell the database to link the two tables together. Well, this type of join is called an outer join. I could spend a lot more time on joins but we only have 5 minutes! For example, using the above query from the previous step, suppose we wanted to modify the query so it returned the zip code and total units sales for customers with the zip code A group by does just that, it groups records together so you can perform some type of total or aggregate function.
In this case the only records that will be totaled are ones with a zip code of as specified in the WHERE filter. Below is an example of query results. The query will now return total units sales for ALL zip codes. How would you accomplish this? Understanding this makes it easier to realize that queries can be joined just like tables.
To rename an attribute, right-click the attribute and select Rename. Click Add. Ensure that you do not have the first column Address selected because it will cause an error. Under Compound Attributes, you should now see your Distribution Center attribute. You can expand it to see its compound ID columns.
Specify attribute description columns according to the Attributes table. Note: Architect makes an educated guess for the description column based on the attributes ID column that you selected. You specify the description column for Distribution Center in a later step.
Specify attribute lookup tables according to the Attributes table. Note: Architect makes an educated guess for the lookup table based on the attribute ID and description columns that you selected. The Day attributes lookup table may need to be changed. You specify the lookup table for Distribution Center in a later step.
All Rights Reserved Page 16 of 38 9. Specify the children for each attribute according to the Attributes table by doing the following: From the Attributes list, select an attribute and click Add. In the Select Children Attributes window, select all attributes that you want to assign as immediate children and click OK.
In the Children of list, select the relationship type. Note: Architect makes an educated guess for the children based on the attribute ID columns that you selected.
After reviewing the list of attributes you are about to create, click Finish. The Project Creation Assistant returns with a green check mark next to the Create attributes step All Rights Reserved Page 17 of 38 5.
Expand the Practice Tutorial Project. Notice that the facts you created earlier were saved to this location. On the File menu, point to New, and select Fact.
All Rights Reserved Page 18 of 38 5. Click Validate to check the syntax. Under Mapping method, ensure Automatic is selected. In the Fact Editor, on the Definition tab, click New and define the two other fact expressions of Revenue. Click Save and Close. In the Save As window, name the fact Revenue. Click Save.
Following a similar procedure, use the table to create the Discount fact. Update the project schema. Full Name should display the last name and then the first name of a customer for example, Smith, Jones. The default report display form should be Full Name. The default browsing display forms should be Last Name and First Name. How to add attribute forms to an existing attribute: 1. Notice that the attributes you created earlier were saved to this location.
Double-click Customer. All Rights Reserved Page 19 of 38 4. On the Forms tab, click New. Using the following table, follow a similar procedure to create the remaining three attribute forms: Full Name, Address, and E-mail. After you created the remaining forms, in the Attribute Editor, click the Display tab.
All Rights Reserved Page 20 of 38 How to create an implicit attribute form expression for the Rush Order attribute: 1. On the File menu, point to New and select Attribute. Under Mapping method, ensure that Automatic is selected. In the form expression window, enter "Y" including the quotes. Under Mapping method, ensure Manual is selected. In the Attribute Editor, click the Children tab. All Rights Reserved Page 21 of 38 In the Attribute Editor, click Save and Close.
In the Save As window, name the attribute Rush Order. Customer Age Attribute Customer Age is a derived attribute. Use an ApplySimple statement to calculate a customers age based on their birth date. How to create a derived Customer Age Attribute: 1. In the Attribute Editor dialog box, click the Children tab.
In the Save As window, rename the attribute to Customer Age. All Rights Reserved Page 22 of 38 User Hierarchies Now that you have created the attributes and specified their parent-child relationships, you are ready to create user hierarchies. User hierarchies enable you to easily browse through attributes in Desktop. Create the following five user hierarchies according to their requirements: Time Hierarchy Include all time-related attributes as diagrammed in the logical data model.
Make all attributes entry points. Allow drilling on the hierarchy.
Customers Hierarchy Include all customer-related attributes as diagrammed in the logical data model. In addition, include the Customer Age and Rush Order attributes created in section 8 and 9. Make all attributes entry points, except Order. Lock the Order attribute. Geography Hierarchy Include all geography-related attributes as diagrammed in the logical data model. Promotions Hierarchy Include all promotion-related attributes as diagrammed in the logical data model. All Rights Reserved Page 23 of 38 Allow drilling on the hierarchy.
Products Hierarchy Include all product-related attributes as diagrammed in the logical data model, except Discontinued. How to create user hierarchies: 1.
On the File menu, point to New and select Hierarchy. In the Hierarchy Editor, notice that the attributes are arranged according to their parent-child relationships. Attributes with a green check mark are entry points. By default, any attribute without a parent is an entry point.
Right-click Quarter and select Set as Entry Point. Follow the same procedure for Month and Day. To remove an entry point, right-click an attribute and select Remove as Entry Point.
To lock an attribute, right-click the attribute, point to Element Display and select Locked. At the bottom of the Hierarchy Editor, leave the Use as a drill hierarchy check box selected. All Rights Reserved Page 24 of 38 9. When notified that this hierarchy has been defined as a drill hierarchy, click OK. In the Save As window, rename the hierarchy to Time Hierarchy. Remember to make all attributes entry points except Order.
Lock the Order attribute and allow drilling on the hierarchy. Remember to make all attributes entry points and allow drilling on the hierarchy.
It covers concepts from the MicroStrategy Desktop: Advanced Reporting course, but it is limited to those advanced reporting techniques that can be completed in a 2-tier project.
The actual MCD Certification contains additional reporting requirements. In addition, this practice project contains report development information that is not included in the actual MCD project. However, after some further investigation, there were other peak months in for certain subcategories. In addition, sales for Science and Technology peaked in March. This report will be used to illustrate how much sales during the peak months contributed to sales of the same items during the entire year.
Report Requirements: Display the revenue for each item in the three selected subcategories during their peak periods for example, Cameras in April , as well as sales of the same items for the entire year. For each item, show the percent contribution their peak sales contributed to their annual sales.
Display a totals row that shows a total for each metric by subcategory. Be sure the percent contribution metric displays Smart Totals. Change the formatting of these totals to make them stand out.
A two to three week delivery period is guaranteed to your customers, so any orders that are shipped three weeks, or 21 days, past the date the order was placed is considered delayed.
Report Requirements: Include all data in the data warehouse with no restriction to a particular time period. Display each customer city where items were shipped 21 days or more later than the day they were ordered. Display both the number of delayed orders from the customer cities as well as the total number of orders of those cities. Also, display the percent of delayed orders to total orders rounded to the nearest whole percent. Display customer cities grouped by their customer regions.
Include a row showing totals by Customer Region for each metric on the report. Also include a grand total for all metrics. Be sure the percent metric displays Smart Totals. Result Set Check: The report result returns a total of rows. Albany had a total of orders and 96 delayed orders. This forces the metric to count from the correct fact table. The child of Ship Date is Customer. The final report needs to place these customers into quartiles in each of their customer regions based on the total dollars that they spent.
Report Requirements: Display Customer Region, Customer Information including last name, first name, and address , total dollars spent by each customer, and the quartile each customer falls into for example, 1, 2, 3, or 4 with 1 being the 'best' customers. Sort the customers alphabetically by Customer Region, then by quartile within the region with the best customers appearing first , and finally by dollar sales within the quartile in descending order.
Include all customer regions, both foreign and domestic. Prompt the user to select the number of repeat purchases the customer must have made in order to be included in the report.
The user should be limited to selecting greater than or equal to a number between 15 and For the initial report, select The Northwest customer region has two customers: one in quartile 2 and another in quartile 4. The NTile parameters specify 4 tiles and break by Customer Region.
The report filter contains a set qualification based on Count of Orders, and embedded in the set qualification is a value prompt.
The attribute forms for displayed for Customer should be specified only on this report. All Rights Reserved Page 31 of 38 Document Development Because this project is limited to functionalty available within a 2-tier project, it does not include a Document Creation phase.