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

KB30585: "[DFCSCHEMA] Population Exception: The object shown .. in the schema: -Dimension/Hierarchy-Attribute:Object is not found in DFCSchema during DFC conversion" error returned while updating schema in MicroStrategy.


Community Admin

• Strategy


Cannot delete 'LU_Gender' because other objects depend on it. Do you want to search the dependent objects?
 
User gets this error while updating schema after moving some hierarchies and attributes from another project:
 

ka04W000000OdUEQA0_0EM440000002ERg.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: -Dimension/Hierarchy-Attribute:Object is not found in DFCSchema during DFC conversion Error(s) occurred while loading schema: 0.

CAUSE:
The error is an indication of metadata inconsistency. It is difficult to identify how the metadata has become inconsistent. Making changes to a schema object while a large number of users are logged into the project simultaneously may be a factor. Also, moving objects across several Strategy environments before reaching their final destination may be another factor.
If running ScanMD against the metadata, there will be errors in the `Schema Collections Verification` test. The error entries will be of type:

Form/Table/Column is not found in Schema`s Forms/Tables/Columns collection.

 


 

ACTION:
 
Run the latest version of ScanMD against the project.  For more information about ScanMD, refer to the following Strategy Knowledge Base document:
KB35809: Using ScanMD to fix known logical metadata inconsistencies in the Strategy 9.x Product Suite
Alternatively, if users know what were the objects moved to the metadata that originated the issue, they can erase those objects and try moving them again.
 
Metadata Modification WARNING:
Manually editing values in the Strategy Metadata incorrectly may cause serious, project-wide problems that may make your project unusable. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users are strongly encouraged to backup Metadata prior to any alteration.
  


Comment

0 comments

Details

Knowledge Article

Published:

April 12, 2017

Last Updated:

April 12, 2017