This case is also explained with an example based on the MicroStrategy Tutorial project.Ī. The smart metric and the component metric are from different datasets. For example, users can have a smart compound metric and a component metric of this compound smart metric on the grid in the document.
The same metric exists multiple times on the grid. If users do not want such blank columns to be displayed, set the source dataset so that such ambiguity does not arise. Since the engine cannot just randomly pick one of the two available datasets, it chooses not to display any data for this metric. In the above example, the metric ‘Profit’ does not exist in the source dataset ‘DS3’ and exists in more than dataset which are in the document i.e., it exists in both ‘DS1’ and ‘DS2’. In the executed document, no data is displayed for the metric ‘Profit’ as shown below. Set the source of this grid to be the dataset ‘DS3’.ģ. Create a document based on the above datasets and create a grid object on the document with the following objects: ‘Year’, ‘Quarter’, ‘Profit’. Dataset DS3 with the attribute ‘Quarter’ and metric ‘Cost’.Ģ. Dataset DS2 with the attribute ‘Year’ and metrics ‘Profit’, ‘Revenue’.Ĭ. Dataset DS1 with the attribute ‘Year’ and metric ‘Profit’.ī. This case is explained with an example based on the MicroStrategy Tutorial project.Ī. Only one dataset does not contain this metric and this dataset is set as the source of the grid. Note: When the MicroStrategy Analytical Engine cannot resolve the correct datatset as explained in the cases below, the data displayed for these will correspond to the value chosen for the missing object display under Project Configuration > Report definition > Null values > Missing Object Display. Examples based on the MicroStrategy Tutorial project have been provided to explain this information. The MicroStrategy Analytical Engine displays no data for metrics in ambiguous cases or when there is a conflict. Ambiguous cases can arise in cases where multiple datasets contain the same objects. Users can set the set the source of the grid to a particular dataset or choose no dataset (in which case, the MicroStrategy engine will determine the best suited dataset). The default value is set to: “Objects in document grids must come from the grid’s source dataset only”. Click “Configure” under the Analytical engine VLDB.Right mouse click (RMC) on the project name.For example, if Dataset #1 contains Category and Revenue and Dataset #2 contains Category and Profit, a grid can be created which contains Category, Revenue, and Profit.Īdministrators can control the use of multiple datasets in a single grid, graph, or widget through the Analytical Engine VLDB properties window at the project level. Users now have the ability to add attributes and/or metrics from multiple datasets to a single grid, graph, or widget. Multiple Datasets in a Single Grid/Graph/Widget Object in MicroStrategy Web 9.4 Starting with MicroStrategy Analytics Enterprise 9.4.1, Report Services documents can contain grids with objects coming from more than one dataset.
0 kommentar(er)
