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

KB38470: Attribute alias is not used in a Report Services document in a view filter, threshold editor and a derived element editor in MicroStrategy Developer and Web


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article describes an issue where attribute aliases that are created in a Report Services document are not reflected on in the editors. In some places such as: Advanced Sort, Subtotals, Custom Banding, Formatting, the attribute alias is used correctly, but in other places such as: View Filter, Thresholds, Attribute Display (forms), Derived Elements, Drill Map, the attribute alias is not used. Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled MicroStrategy release.

SYMPTOM:
In both Strategy Developer and Web, attribute aliases that are created in a Report Services document are not reflected on certain features in the editors.  
 
STEPS TO REPRODUCE:
Follow the steps below to reproduce the issue in Strategy Tutorial project:

  • Create a document from a report with an attribute.
  • Change the attribute alias for the attribute.  For this example, the alias is "x".
  • Notice the object alias is correctly shown on the grid.
ka02R000000kVozQAE_0EM440000002DSG.png
  • Open a view filter editor/threshold editor/derived element editor and notice the actual object name instead of the alias is used:
ka02R000000kVozQAE_0EM440000002DSF.png

 
CAUSE:
This is a known issue in Strategy Developer and Web
 
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. 


Comment

0 comments

Details

Knowledge Article

Published:

May 23, 2017

Last Updated:

May 23, 2017