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

KB44838: "Follow the instructions marked below by a red flag" error shows but there is no red flag when running an MDX cube report in MicroStrategy Web


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article notes a situation where an invalid error is thrown in web when trying to answer prompts off of an MDX cube

SYMPTOM:
"Follow the instructions marked below by a red flag" error shows but there is no red flag when running an MDX cube report in Strategy Web, as shown below:

ka02R000000kXNIQA2_0EM440000002Cds.jpeg

 
Follow the instructions marked below by a red flag.
 
STEPS TO REPRODUCE:
Follow the steps below to reproduce the issue:
 
NOTE:
The issue does not happen when the report is running in Strategy Developer.

  • In Strategy Developer, create a Database Instance to connect to the MDX server.
  • Go to Menu -> Schema -> MDX Cube Catalog, and import a cube from the MDX source.
  • Select the imported cube, and go to Cube Mapping tab.
  • Right mouse click on the attribute -> Map
  • Select an existing attribute in the project, and map the attribute forms, as shown below:
ka02R000000kXNIQA2_0EM440000002Cdi.jpeg
  • Save and close the MDX Cube Catalog.
  • Update Schema.
  • Create an MDX cube report, and select the imported cube.
  • Add a prompt based on the mapped attribute, as shown below:
ka02R000000kXNIQA2_0EM440000002Cdk.jpeg
  • Save and close the report.
  • Run the report in Strategy Web. Select any element, and the issue happens after clicking on Run Report.

 
 
CAUSE:
This is a known issue with Strategy Web 10.x.
 
ACTION:
Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release. 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2017

Last Updated:

June 15, 2017