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

KB7536: Error: ’A group of facts that need extensions do not have a common part in their group entry levels. Error in Process Method of Component: SQL Engine Server, Error code -2147212800’ when running reports after upgrade in MicroStrategy Desktop 9.4.1


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article describes an error when running reports after upgrade in MicroStrategy Desktop 9.4.1

SYMPTOM:
After users migrate reports and dependent objects from one project to another, some of those reports fail to run in Strategy Desktop 9.4.1  and newer. The following error message is displayed:
'A group of facts that need extensions do not have a common part in their group entry levels. Error in Process Method of Component: SQL Engine Server, Project x, Job yyyyy, Error code -2147212800.'
 
These reports functioned properly in the source project and continue to run without error in the source project.
 
CAUSE:
Some attributes in the target project have attribute forms that have different source tables selected to those in the source project. This can occur even if the attribute is also migrated from the source project to the target project.
 
Performing an 'update schema' does not resolve this issue, nor does running ScanMD.
 
ACTION:
Some of the attributes involved in the reports that fail may require modification.

  1. Go to the attribute forms in the target project in Strategy Desktop.
  2. Select the tables that should be checked.
  3. Verify which tables should be selected by comparing the attribute form definition in the source and target projects.

Example Attribute form with all tables selected in source project:

ka02R000000kYVaQAM_0EM440000002G99.jpeg

Example Attribute form with only some tables selected from the target project:

ka02R000000kYVaQAM_0EM440000002G9U.jpeg

Once all tables have been selected in the target project for each attribute form affected, go to the Logical table editor and recalculate the table keys. This is the button to the left of the 'Help' button in the logical table editor. Do this for all the tables that were added to these attribute forms as possible source tables.
 
Once this is done, the reports should run successfully.
 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017