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

KB275279: Some metrics and subtotals show different results after upgrading from MicroStrategy 9.x to MicroStrategy Secure Enterprise 10.x


Community Admin

• Strategy


 
SYMPTOM
After upgrading from Strategy 9.3 to 10.x, some metrics and subtotals show different results as shown below: 
Strategy 9.3.1 
 

ka04W000000OafbQAC_0EM440000002C1f.jpeg

 
Strategy 10.1 

ka04W000000OafbQAC_0EM440000002C1d.jpeg

 
 
In the SQL view Analytical Engine calculation steps, the evaluation order is different between 9.3 and 10.1.
CAUSE
This is working as designed in Strategy Secure Enterprise 10.x. The default evaluation order has been modified in 10.x. In 10.x, the default option is as shown below: 9.x order: Calculate derived elements/consolidation before derived metric/smart compound metric, "total" subtotal as smart and other subtotals as non-smart
 

ka04W000000OafbQAC_0EM440000002C1h.jpeg

 
In 9.x, the default evaluation order is as shown below: 6.x order: Calculate derived metric/smart compound metric before derived elements/consolidation and all subtotals as smart

ka04W000000OafbQAC_0EM440000002C1T.jpeg

 
ACTION
 
If users prefer to see the results seen in 9.3.x, change the evaluation order to the first option:  6.x order: Calculate derived metric/smart compound metric before derived elements/consolidation and all subtotals as smart
To apply this at the project level, the VLDB property can be changed at the project level from project configuration > project definition > advanced > project VLDB settings 'Configure' 
 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE22961.
 
 
 
 
 
KB275279


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

December 31, 2018