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

KB440195: After creating an attribute unable to update schema with error message: "The object shown in the following hierarchy no longer exists in schema" in MicroStrategy 10.10


Stanislav Gordiienko

Senior Product Manager • MicroStrategy


This knowledge base article describes possible cause for triggered error message "The object shown in the following hierarchy no longer exists in schema" when updating schema in 2 or 3 tier project source after creating attribute which contains metric in at least one of its expressions.

SYMPTOMS:
When updating schema in 2 or 3 tier, users receive an error message from Strategy Developer as seen in the screenshot below: 

ka04W000001EtFsQAK_0EM44000000A4cS.jpeg


Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: [DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in schema: -Link-Attribute:(unexpected) Table GUID: 2E50B92F44167F6B4A7C258D59613A98
Message from GetErrorInfo : Login failure. Error(s) occurred while loading schema: 1.

STEPS TO REPRODUCE:
1. Using Attribute Editor, create a new attribute

ka04W000001EtFsQAK_0EM44000000A4cc.jpeg

2. Create an expression which would contain a metric in its syntax. For example, in Strategy Tutorial select column MONTH_ID from LU_MONTH. To include a metric into the syntax, we are using this sample case statement:


Case(([MONTH_ID] < Revenue), "Y", "N")

ka04W000001EtFsQAK_0EM44000000A4cr.jpeg

3. Validate the syntax and and verify column or metric name if multiple objects with the same name have been found and make sure that syntax has been validated.
4. Click OK to save expression and OK to save attribute form. Save the attribute and close attribute editor.
5. Update the schema in Strategy Developer to observe the error message from SYMPTOM section.
CAUSE:
This is a known limitation of Strategy Developer. The error message happens because the attribute expression contains a metric.  Having metrics inside an attribute definition is not valid.
ACTION:
Remove such references to metrics from the attribute expression.  Later releases of Developer may remove the ability to add metrics inside the attribute editor to prevent such issues.
WORKAROUND:
Although using metric in attribute definition is invalid, there are certain instances/requirements when aggregated metric values under particular filtering or level conditions may need to be used as an attribute in the report. Using Derived Elements should allow you to meet such requirements. To read more about Derived Elements in Strategy use the following URL
https://www2.microstrategy.com/producthelp/10.7/BasicReporting/WebHelp/Lang_1033/Content/BasicReporting/Derived_elements.htm
This issue has been logged as KB ID: KB440195


Comment

0 comments

Details

Knowledge Article

Published:

March 21, 2018

Last Updated:

March 21, 2021