|
Summary Mission
|
Summary mission is a query, with or without aggregates.
Only the list of
dimensions is compulsory to compose. You can also define several aggregates. In
this case, the data will be grouped by dimensions. If there are no aggregates it
will be a simple query without grouping.
If you group data, you can analyze any row more thoroughly by
creating
submissions.
After retrieving data you can:
move columns within the detail table (left-click a column title and drag it to the left or right);
change any column width (drag a column border to the left or right);
sort the data (double click on the title of the column, you want to sort the data by);
search for rows by substring or certain first symbols (just select the required column and start typing a substring or first symbols of the required word). The program will search for matches on your typing each symbol;
summarize numeric columns;
Only summary missions can be used in reports. Nevertheless, you can create a summary submission for any type of parent mission. In practice, if you need to use the details of a detailed mission's item in a report, you may just create a summary submission for this item.
Simple queries without aggregations
If you need to create a simple table query without grouping, create a summary mission that has a one-table data model. Do not specify an aggregate. You can specify just a filter condition. The program will not group rows in query result.
You can unite several summary missions. Full compatibility of names, types and column order is not necessary. It is possible to unite retrieval results even from incompatible data sources.
The Union bar
on the right side of the
mission structure (or
cube update) dialog window is
used to create unions. It consists of two arrow-buttons for up and down switching
between UNION clauses and buttons with UNION clause numbers used to view a
concrete clause. To create a new UNION section click
in the bar.
If current UNION element is the last, the program will create a clear page for a new element. Before that, like when creating a new mission, it will require a data model template or a data source specified.
If a UNION section is fully compatible with the first section, it will be executed the most fast, because the program will transfer the query with UNION sections to the server. The following conditions are required for sections full compatibility:
equal column quantity;
equal column name;
equal column type;
equal column order.
If there is no full compatibility the program will first retrieve data on the client side and add to the first section result then.
Data source compatibility in different UNION sections is not as important, as the query and main mission data source compatibility. The ability of Dataodyssey Express to unite sections of different structure and from heterogeneous data sources is rather unusual and can be very useful in some situations.