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

KB9337: "Report returned no data" error message appears on a MicroStrategy Developer report with two or more metrics and one of the metrics contains no data.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Users receive a "Report returned no data" error message in MicroStrategy Developer when the report contains two or more metrics and one of the metrics contains no data.

Users receive a "Report returned no data" error message in Strategy Developer when the report contains two or more metrics and one of the metrics contains no data.
The following example uses the Strategy Tutorial project to illustrate this issue.
 
SYMPTOM:
Consider that a user has a report with one metric for 'Revenue' and the other for the same definition with a transformation for the previous year. This report has a filter to month = March 2001.
 
Notice that there are values for both metrics, as illustrated below:
 

ka02R000000kbpJQAQ_0EM440000002G1j.jpeg

 
However, the report does not return any values when the filter definition is changed to month = March 2000 even though the previous report shows that there are values present for March 2000. When this report is executed, the following error message appears:
 

ka02R000000kbpJQAQ_0EM440000002G1h.jpeg

 
Report returned no data
CAUSE:
This issue occurs because the metric outer join is not properly set.
 
ACTION:
To resolve this issue, change the metric join type at the Report Data Option to "Outer", as shown below:
 

ka02R000000kbpJQAQ_0EM440000002G1c.jpeg

 
The report now displays the proper values:
 

ka02R000000kbpJQAQ_0EM440000002G1g.jpeg

 


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017