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

KB12159: “[DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in the schema: -Relation-TableObject is not found in DFCSchema during DFC conversion” error is generated when attempting to update the schema


Community Admin

• Strategy


“[DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in the schema: -Relation-TableObject is not found in DFCSchema during DFC conversion” error is generated when attempting to update the schema

When attempting to update the schema, users receive the following error message:

ka04W000000OahvQAC_0EM440000002Fhy.jpeg

 


Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: Population Exception: The object shown in the following hierarchy no longer exists in the schema: -Relation-TableObject is not found in DFCSchema during DFC conversion. ( 1 ).

 
ScanMD will provide the following error:

Error Type 12: Error : Attribute {Attribute Name} BaseForm {#} is not supported by its lookup table {Table Name}. No recommended action: Fix not implemented yet. Please check {Attribute Name}'s definition in Strategy Desktop.

 
CAUSE:
 
Either there is no primary lookup table defined for the specified attribute form, or the defined primary lookup table does not have a structure that allows it to be the primary lookup for the defined form expression.
 
ACTION:
 
Define a valid primary lookup table for the attribute form through the attribute form editor. After fixing the definition, the user should be able to update schema.
 
NOTE: It may be necessary to restart the Strategy Intelligence Server before updating the schema in 3-tier.
 
KB 000019177


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

September 28, 2018