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

KB438621: MicroStrategy Architect does not save an attribute created with only a DESC form


Community Admin

• Strategy


This knowledge base article describes a known limitation in MicroStrategy Architect 10.x and above when attempting to save an attribute with a Description form only.

SUMMARY:
This knowledge base article describes a known limitation in Strategy Developer 10.x and above when attempting to save an attribute with a Description form only.
SYMPTOM:
When creating an attribute in Strategy Architect using only a DESC form, after saving and closing the attribute, the changes are not saved and the attribute is not created afterward. However creating an attribute manually in Strategy Developer with only a DESC form, the attribute gets created and is recognized in Architect.  
STEPS TO REPRODUCE:
1. Create a new attribute in Architect
2. Change the attribute form category from ‘ID’ to ‘DESC’ 
3. Map the attribute to corresponding hierarchy
4. Save and close out of Architect and update schema
5. Search for the attribute in Developer doesn’t return the newly created attribute
6. Checking for newly created attribute in Architect does not exist.
 
 
CAUSE:
This is working as design. The ‘ID' form category is the default key form for an attribute, when creating an attribute in Architect with only the DESC form, there is no key form for the attribute. Without a key form the attribute is not being saved because it is not a proper attribute.  
ACTION               

  1. Change the form categories for the project to use the DESC form as the key form instead of ID, which will allow attribute to be created in Architect with just a DESC form.
  2. Create the attributes in Developer where the DESC is automatically made the key form when the DECS is the only attribute category form.
ka04W000000Obf5QAC_0EM44000000VlmV.png

 
  KB438621


Comment

0 comments

Details

Knowledge Article

Published:

September 13, 2017

Last Updated:

December 31, 2018