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

KB440482: "No data returned" is displayed when filtering data in a web visualization (VI)


Community Admin

• Strategy


This KB article describes how some user may experience an Error when filtering data in a web visualization (VI), when adding two particular attributes from a cube and unchecking the "ALL" option from the filter, error "No data returned" is displayed when there is data available.

SYMPTOM
Some user may experience an Error when filtering data in a web visualization (VI), when adding two particular attributes from a cube and unchecking the "ALL" option from the filter, error "No data returned" is displayed when there is data available.
STEPS TO REPRODUCE
1) Create a visualization with these 2 attributes. 
2) Add a filter for the Customer Acquisition Store attribute. 
3) Strategy will show 2 possible values for this attribute: All and DIRECT (both are selected). 
4) Unchecked the 'All' option. 
5) MSTR shows the error: 
"No data returned for this view. This might be because the applied filter excludes all data" 
But if we uncheck the "ALL" option as we have data for "DIRECT" (customer Acquisition store) this row should be show on the VI, but instead is showing an error message. 
CAUSE
The location_id columns on which the attribute ID form for "Customer Acquisition Store" is based on is defined as Integer column (see attached screenshot). We require our users to go in their projects and change that for right CSI to get generated. 
We are currently not changing/updating the Column data type in the metadata for project schema, customer has to make sure that the datatype is right.
ACTION
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release.
  40482 KB440482


Comment

0 comments

Details

Knowledge Article

Published:

March 30, 2018

Last Updated:

December 31, 2018