KB9201: "SQLEngine got an Exception from DFC: [DFCSCHEMA] Logic Exception: Partition mapping table can not be used as lookup table" error message appears and the report fails for MicroStrategy Developer users.

Salesforce Solutions Architect • Strategy

"SQLEngine got an Exception from DFC: [DFCSCHEMA] Logic Exception: Partition mapping table can not be used as lookup table" error message appears and the report fails for MicroStrategy Developer users.

SYMPTOM
Users executing a Strategy Developer report may find that it fails with the following error message:


SQLEngine got an Exception from DFC: Logic Exception: Partition mapping table can not be used as lookup table.

CAUSE
When checking the attributes on the report, users notice that one attribute is using a Partition Mapping Table (PMT) as its lookup table. For this example, the "Year" attribute is using the PMT_Year table as a lookup table:

ACTION
In Strategy 9.x, it is possible to create a Logical Table based off a SQL statement to use as a lookup table for the elements in the Partition Mapping Table. The screenshot below describes how the lookup table can be created.

When the new attribute based off the logical table is placed on a report the SQL generated uses the logical table as the lookup.


Select distinct a11.MONTH_ID MONTH_ID from (select distinct MONTH_ID from PMT_INVENTORY) a11

For more information about partitioning, refer to the following Strategy Knowledge Base documents:

KB5465: What is the difference between warehouse and metadata partition mapping in Strategy Desktop 8.x ?
KB5529: How to set up a project using partitioned fact tables in Strategy Architect 8.x and 9.x

Comment

0 comments

Details

Knowledge Article

Published:

April 14, 2017

Last Updated:

April 14, 2017