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

KB45172: Report result rows do not seem to be filtered according to the metric qualification definition when the metric qualified on contains values formatted to be percentages in MicroStrategy


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article notes a consideration for dealing with metric qualifications on percent metrics

SYMPTOM:
A user creates a report that uses a percentage metric like the one below. 'New Metric' is a compound metric (Cost / Revenue):

ka02R000000kcBOQAY_0EM440000002CbN.png

 
The user attempts to create a metric qualification filter (either a report filter or a view filter) on the percentage metric 'New Metric' where the metric value is greater than 75. When they do so, no result rows are returned:
 

ka02R000000kcBOQAY_0EM440000002CbU.png

 
 
No result rows are returned even when the number used in the 'New Metric' filter is very low:

ka02R000000kcBOQAY_0EM440000002CbL.png

 
CAUSE:
The Strategy SQL Engine applies metric qualification filters in the report SQL's WHERE clause according to the unformatted value of the metric being qualified on. The percentage formatting is only used for report display. In this case, the unformatted value of 85% is 0.85 (Cost/Revenue), so creating a filter that excludes rows with 'New Metric' values below 75 (or 0.86) will return no data.
 
ACTION:
The value used in a metric qualication must be entered in a way that corresponds to the unformatted metric values. Therefore, if the user wants to the report to return all rows with a 'New Metric' value above 75%, they should enter the following:

ka02R000000kcBOQAY_0EM440000002CbM.png

 
 


Comment

0 comments

Details

Knowledge Article

Published:

May 23, 2017

Last Updated:

May 23, 2017