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

KB317193: "None of the table keys in PseudoTable" error occurs when running a report with a non-aggregatable metric in MicroStrategy


Community Admin

• Strategy


This article notes a scenario where a pseudotable error is thrown with non-aggregatable metrics

SYMPTOM
In Strategy 10.x, when running a report that has a non-aggregatable metric, users may notice that in certain cases the following error message is seen:
 


Error: SQLEngine got an Exception from DFC: [DFCENGINE] Engine Logic: Non-Aggregation Metric dimensionality error. 
None of the table keys in PseudoTable [LHS = table1, RHS = table2]'s LHS table are children of Non-aggregation dimensionality: Attribute1 
Error in Process method of Component: SQLEngineServer, Project Strategy Tutorial, Job 1472, Error Code= -2147212800.

 
STEPS TO REPRODUCE
The following steps can be used to reproduce the error in the Strategy Tutorial project

  • Create a fact that is only sourced from a Quarter level fact table, in this case QTR_CATEGORY_SLS
ka04W000000OcA0QAK_0EM440000002C09.jpeg
  • Create a metric that uses the fact in step 1 and put the level dimensionality to be non-aggregatable at the level of the Month of Year attribute.  Set the grouping to be beginning (lookup)
ka04W000000OcA0QAK_0EM440000002C0G.jpeg
  • Create a report with the metric from step 2.  The error will occur when running the report.
ka04W000000OcA0QAK_0EM440000002C0B.jpeg

 
CAUSE
The error occurs because there is an indirect many-many relationship between the attribute in the level dimensionality and the attribute that is the level of the fact table, in this case Month of Year and Quarter respectively.  
The metric in the above example will calculate the revenue for the first Month of Year in the lookup table for Month of Year from the Quarter level fact table.  But there is no direct relationship between Quarter and Month of Year so there is no proper way to relate the elements of Quarter in the fact table with the beginning month of year from the lookup table.  Thus the metric calculation should not be expected to return meaningful data given the relationship between these 2 attributes, and the exception is thrown indicating that there is no direct join path through parent-child relationships from the fact table up to the non-aggregation dimensionality attribute.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 26, 2017

Last Updated:

May 26, 2017