EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB237201: Derived metrics calculate differently when created from the Dataset Objects pane or the Grid pane in a Visual Insight dashboard in MicroStrategy Web


Community Admin

• Strategy


SYMPTOM:
When using a Grid visualization in Visual Insight in Strategy Web 9.4.1, derived metrics can be created by clicking on the down arrow next to the metric name in the Dataset Objects pane or Grid pane. More specifically, a “Percent to Total” metric can be created by clicking on the down arrow next to the metric name, and selecting “Percent to Total”.
The picture below shows how to create a “Percent to Total” metric in the Grid pane:

ka04W00000148n3QAA_0EM4400000025lO.jpeg

 
The picture below shows how to create a “Percent to Total” metric in the Dataset Objects pane:

ka04W00000148n3QAA_0EM4400000025lM.jpeg

 
As seen from the pictures above, there are two ways to create a “Percent to Total” metric on the “Profit” metric. However if both metrics are added to a grid, they provide different results, as shown below. 
 
Metric created from Grid Pane:

ka04W00000148n3QAA_0EM4400000025l4.jpeg

Notice how the value of the metric in the image above, adds up correctly to 100%.
 
Metric created from Dataset Objects pane:

ka04W00000148n3QAA_0EM4400000025lX.jpeg

Notice how the value of the metric in the image above, does not add up correctly to 100%, but gives a value of 700%.
 
STEPS TO REPRODUCE:

  • In Strategy Web 9.4.1, create a report with Customer Region, Customer State, and Profit.
  • Create a Dashboard in Visual Insight using the report and insert both attributes and metric into a grid visualization.
  • In the "Grid" pane, click on the down arrow next to the Profit metric and go to Percent to Total and then Customer Region, as shown below.
ka04W00000148n3QAA_0EM4400000025lV.jpeg
  • Insert this derived metric, Percent to Total, into the grid.
  • Click the down arrow that appears when hovering over the "Customer State" column in the grid and then over the "Customer Region" column, and go to "Show Totals" > Enable "Total", as shown below.
ka04W00000148n3QAA_0EM4400000025lZ.jpeg
  • The grand total for the derived metric, Percent to Total, should display 100% as expected.
  • Now, in the "Dataset Objects" pane, click on the down arrow next to the Profit metric and go to "Percent to Total" and then "Customer Region".
  • Delete the previous derived metric, and insert the new derived metric, Percent to Total, in the grid. The grand total for the second derived metric will add up all the subtotals and will therefore be 700%, which is incorrect.

CAUSE:
This is working as designed in Strategy Web 9.4.1. When creating a derived metric from the "Grid" pane, the metric automatically becomes a "smart metric" and does not add up all the subtotals, giving a correct overall percentage that adds up to 100%. When the metric is created from the "Dataset Objects" pane, the metric is not created as a "smart metric" by default, thus the result is the regular addition of all the values adding up to 700%. The problem arises from not being able to identify which location creates what kind of metric. A request has been logged to address this issue.
Note: Refer to tech note KB8472  for more information on smart metrics. 
ACTION:
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release.
WORKAROUND:
If a smart metric is required, create the derived metric from the "Grid" pane. If a normal metric is required, create it from the "Dataset Objects" pane.
 
The Strategy Internal Reference Number for the issue discussed in the technical note is 1014534.


Comment

0 comments

Details

Knowledge Article

Published:

April 12, 2017

Last Updated:

April 12, 2017