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

KB43273: Error: “Engine Logic: Cannot get the column reference of a join attribute from the associated table” is seen when running report in MicroStrategy


Community Admin

• Strategy


This article describes an issue where an error can be received with an invalidly mapped compound ID attribute.

SYMPTOM:
When running a report in Strategy, users may observe the error shown below: 

ka04W000000OdcwQAC_0EM440000002Cgj.png

 


Error: SQLEngine got an Exception from DFC: Engine Logic: Cannot get the column reference of a join attribute from the associated table.

 
CAUSE:
This error indicates there is a data modeling inconsistency which happens when an attribute relationship is defined through a table which doesn't support all components of a of an attributes compound ID forms.
In this case, an attribute contains a compound ID attribute form in which not all the source tables contain both the ID components. When these tables are used as relationship table for his attribute, the Strategy SQL Engine attempts to join relationship table with fact tables and lookup tables, and finds that the relationship table does not contain all the required columns. This results in the error: “Engine Logic:Cannot get the column reference of a join attribute from the associated table”. Strategy requires compound ID form attributes to have all source tables for all of the ID forms in the ID form group. Due to how the editor works it is not possible to force this restriction upon creation. However it is invalid to have a compound ID form attribute mapped to any table that does not contain all parts of the attributes ID.
 
ACTION:
An attribute relationship table should always be defined through a table that is mapped as the source table of all components of the attribute's ID attribute forms.


Comment

0 comments

Details

Knowledge Article

Published:

April 10, 2017

Last Updated:

April 10, 2017