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

KB47289: Even after changing the VLDB property "Display Null on Top" to place null values at the bottom, the null values are still present at the top in MicroStrategy Developer 9.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Even after changing the VLDB property 'Display Null on Top' to place null values at the bottom, the null values are still present at the top.

SYMPTOM:
Even after changing the VLDB property 'Display Null on Top' to place null values at the bottom, the null values are still present at the top.
 
STEPS TO REPRODUCE:
1. Create a report with an arbitrary attribute and metrics, some of which contains null values.
2. Change the VLDB property ‘Display Null on Top’ to display null values at the bottom of the report

ka02R000000kc6BQAQ_0EM440000002CLP.jpeg

 
3. Sort by the Revenue metric in ascending order.

ka02R000000kc6BQAQ_0EM440000002CLL.jpeg

 
 
4. The report displays that the null values are present at the top instead of at the bottom.

ka02R000000kc6BQAQ_0EM440000002CLZ.jpeg

 
CAUSE:
One possible cause for this issue is that the Report Data Options property ‘Set the value to be used in place of empty values when the report data is sorted’ is enabled and the value of 0 is placed as a parameter. Hence, the null values are treated as 0 when sorting in ascending order, which causes them to be placed at the top.

ka02R000000kc6BQAQ_0EM440000002CLa.jpeg

 
ACTION:
Disable the option ‘Set the value to be used in place of empty values when the report data is sorted’, so the report will return the expected outcome as follows:

ka02R000000kc6BQAQ_0EM440000002CLM.jpeg

Comment

0 comments

Details

Knowledge Article

Published:

May 27, 2017

Last Updated:

May 27, 2017