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

KB276000: Error: (Unexpected case inside switch statement of CDSSBaseElementProxy::gCreateFromElementID) when attribute form ID contains ampersand characters in MicroStrategy Web 10.1 grid selectors


Community Admin

• Strategy


This article describes a known issue when an attribute form ID contains an ampersand character in a grid selector.

SUMMARY:
This article describes a known issue when an attribute form ID contains an ampersand character in a grid selector.
 
SYMPTOM:
When running a document in Strategy Web 10.1 Express mode, the below error is displayed.


Error:  (Unexpected case inside switch statement of CDSSBaseElementProxy::gCreateFromElementID)

 
STEPS TO REPRODUCE:
1. Create a new attribute in Strategy Developer using the Tutorial project
2. Use Source Table: LU_SUBCATEG
3. Use SUBCAT_DESC in expression
4. Mapping method left as Automatic
5. Create a grid with only the newly created Subcateg attribute
6. Create a document in Strategy Web using the grid created previously as a dataset
7. Include a panel stack on the document below the grid, add the new attribute to the panel stack
8. Use the attribute in the grid as a selector targeting the attribute in the panel stack
9. Run the document and select "Art & Architecture"
10. Error below is shown:  

(Unexpected case inside switch statement of CDSSBaseElementProxy::gCreateFromElementID)

 
CAUSE:
This is an identified defect with Strategy Web 10.1.
 
ACTION:
This defect has been fixed in Strategy 10.2. Upgrade to take advantage of the fix.
 
WORKAROUND:
This issue only happens when running the document in Express mode.  Run the document in a different view mode to avoid the issue.


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017