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

KB9184: Running Sums are calculated differently after a metric qualification is applied to a MicroStrategy Developer report.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This document describes an issue in which Running Sums are calculated differently after a metric qualification is applied to a MicroStrategy Developer report

SYMPTOM:
When users execute a report containing a running metric, such as RunningSum(Contribution), and a filter (metric qualification) on the metric, such as RunningSum(Contribution) > 0.5, only 50% of the data is returned by the running metric:

ka02R000000kY2SQAU_0EM440000002G05.jpeg

 
CAUSE:
This issue occurs because the calculation of the metric 'RunningSum(Contribution)' is made at execution time. After filtering, a new calculation is performed and new values are displayed with the original attribute.
The application is working as designed. Note the results in the following screen shot obtained by removing the filter RunningSum(Contribution) > 0.5 and re-executing the report:

ka02R000000kY2SQAU_0EM440000002G07.jpeg

Applying the filter to the report will allow only the first three records to remain since 63.22% > 0.5. The new calculation is performed and a new value will be displayed with the original attribute, i.e. RunningSum(Contribution) displaying data from 27.26% onwards.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017