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
  3. KB44414: List of Dynamic Sourcing errors and their explanation in MicroStrategy

KB44414: List of Dynamic Sourcing errors and their explanation in MicroStrategy


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article lists dynamic sourcing errors alongside explanations.

Below is a list of error messages and their explanation found when using Dynamic Sourcing:

 

Error Message  

Explanation of Error

 CMI_NO_ERROR  

 No error occurred

 CMI_REPORT_IS_XDA  

 The report type is XDA. XDA reports are not supported for the purposes of dynamic sourcing

 CMI_REPORT_LIMIT_ON_CUBE_FOUND  

Cube cannot be reused as there is a report limit on it. Report limits are not supported on the cube side

 CMI_CG_OR_CONSOLIDATION  

 There is a custom group or a consolidation on the template. Custom groups and consolidation are not supported for the purposes of dynamic sourcing.

 CMI_ALL_METRICS_REMOVED_FROM_CUBE  

The cube originally had some metrics, but due to various reasons all of them were considered unusable for the purpose of dynamic sourcing. This cube cannot be used for any reports that have metrics and it cannot be used for any reports that do not have metrics either because the original metrics on the cube acted as a filter and might have filtered out some of the rows that are needed for the report. So this cube cannot be used for any report for the purposes of dynamic sourcing, and it’s not added to the cube index

 CMI_VLDB_DOWNWARD_OJ_PROBLEM  

This cube cannot be used for the purposes of dynamic sourcing, because neither is the downward outer join VLDB setting enabled, nor is the “Allow dynamic caching even if outer join properties are not set” project setting enabled. 

 CMI_VLDB_INCOMPLETE_LOOKUP_PROBLEM  

This cube cannot be used for the purposes of dynamic sourcing, because neither is the "Preserve All Lookup Elements" VLDB setting enabled (3rd option needed), nor is the “Allow Dynamic Sourcing even if outer join properties are not set” project setting enabled 

 CMI_VLDB_OUTER_TO_LOOKUP_PROBLEM  

This cube cannot be used for the purposes of dynamic sourcing, because neither is the "Preserve All Final Pass Results Elements" VLDB setting enabled (2nd option needed), nor is the “Allow Dynamic Sourcing even if outer join properties are not set” project setting enabled. 

 CMI_UNEXPECTED_REPORT_TYPE  

Report type is not supported. The type may be a datamart, XDA or Element browsing report, for example. 

 CMI_CUBES_FOR_AD_HOC_DISABLED_MASTERSWITCH  

Dynamic sourcing is disabled for the current project. 

 CMI_CUBES_FOR_AD_HOC_DISABLED_FOR_REPORT  

Dynamic sourcing is disabled for the current report.

 CMI_CSI_OR_ELEMENT_BROWSING  

Report is already a cube subset report or is used for element browsing. Neither of those requests are supported with dynamic sourcing. 

 CMI_INCOMPLETE_HIERARCHY_DANGEROUS_ATTRIBUTE  

The report or cube contains a attribute that has been set with a VLDB setting that could result in NULLs in lookup or fact tables. 

 CMI_METRIC_NOT_OJ  

This cube cannot be used for the purposes of dynamic sourcing, because there is a metric that is not outer join type and the “Allow Dynamic Sourcing even if outer join properties are not set” project setting is not enabled. 

 CMI_METRIC_WITH_TRANSFORMATION  

Transformation on metric is not supported for dynamic sourcing 

 CMI_METRIC_NOT_LEAF_OR_BRANCH  

Metric is neither a leaf or branch metric (unexpected type). 

 CMI_METRIC_WITH_CONDITIONALITY_IN_CUBE  

Conditional metrics are not supported on the cube side for dynamic sourcing 

 CMI_DIMMETRIC_BRANCH_IN_CUBE  

DimMetricBranches are not supported on cube side 

 CMI_UNSUPPORTED_METRIC_TYPE  

An unexpected metric type was found 

 CMI_NONAGGREGATION_IN_METRIC  

Nonaggregation in a metric is not supported 

 CMI_METRIC_AND_TEMPLATE_LVL_NOT_MATCHING_IN_CUBE  

Level metrics are not supported in cube 

 CMI_FACT_ENTRY_LVL_ERROR  

There is a problem with the fact entry level. Fact extensions, degradations including implicit ones(with cross-joins) are not supported

 CMI_METRIC_FITLER_KEY_NOT_IN_TEMPLATE  

An attribute form from the metric filter key is not on the template. Related to CMI_FILTER_KEY_ATTRIBUTE_UNAVAILABLE 

 CMI_METRIC_GROUP_BY_KEY_NOT_IN_TEMPLATE  

An attribute from the metric group by is missing from the report template.

 CMI_AGG_METRIC_BRANCH_WITH_ZERO_CHECKING  

Aggregate metric branch has been found with zero checking on

 CMI_METRIC_NOT_SAFE  

The metric or one of its constituent metrics is marked as unsafe for dynamic sourcing through the 'Metric Validation' VLDB property.

 CMI_OLD_OLAP_FUNCTION_IN_METRIC  

Old OLAP function behavior is not supported. To fix the issue enable the 9.0 and later option for 'OLAP function support' VLDB property for the project. 

 CMI_BAD_OR_IN_FILTER  

An OR node in a filter has children that are based on different attribute forms and is not supported 

 CMI_ANDNOT_OR_ORNOT_IN_FILTER  

ANDNOT and ORNOT operators in filters are not supported for dynamic sourcing 

 CMI_UNSUPPORTED_FILTER_NODE  

Unsupported filter node (e.g. Metric Qualification) 

 CMI_UNSUPPORTED_FUNCTION_IN_FILTER  

Unsupported function in filter 

 CMI_UNSUPPORTED_EXPR_TYPE_IN_FILTER  

Unsupported expression type in filter

 CMI_FILTER_UNIT_ROOT_NODE_NOT_SUPPORTED  

Report as a filter is not supported for dynamic sourcing 

 CMI_FILTER_PRED_NODE_NOT_SUPPORTED  

Metric qualification is not supported for dynamic sourcing 

 CMI_FILTER_TABLE_NODE_NOT_SUPPORTED  

Subqueries are not supported. Usually this is relationship qualification 

 CMI_FILTER_METRIC_NODE_NOT_SUPPORTED  

Metric qualification is not supported 

 CMI_FILTER_METRIC_EXPR_NODE_NOT_SUPPORTED  

Metric qualification is not supported

 CMI_FILTER_RELATIONSHIP_NODE_NOT_SUPPORTED  

Relationship qualifications are not supported 

 CMI_FILTER_FACT_NODE_NOT_SUPPORTED  

Filtering on facts is not supported 

 CMI_PERFORM_OR_FAILED  

Error occurred when trying to merge two attribute form qualification based on the same attribute form. 

 CMI_DB_ONLY_FUNCTION_IN_FILTER  

Passthrough functions (e.g. ApplySimple) are not supported 

 CMI_INVALID_BETWEEN_IN_FILTER  

The first argument to between should be less than or equal to the second argument. 

 CMI_STRING_COMPARISON_NOT_ALLOWED  

String comparison was disabled with the VLDB setting on the attribute 

 CMI_INCOMPATIBLE_DATA_TYPES_IN_FILTER  

Incompatible datatypes for the same attribute form in the filter were found.

 CMI_FILTERS_CANNOT_ENSURE_ALL_DATA_NEEDED_IS_IN_CUBE  

The cube cannot be hit, because we cannot guarantee that the cube filter did not filter out some data that is to be needed for the report. 

 CMI_ZERO_METRICS_NEEDED  

If report has no metrics on the template, then the only cube that can mach must have no metrics as well. 

 CMI_SECURITY_FILTER_KEY_ATTRIBUTE_UNAVAILABLE  

Attribute from the security filter key is missing in the cube 

 CMI_SECURITY_FILTER_LEVEL_ATTRIBUTE_UNAVAILABLE  

Attribute from the security filter level (top or bottom)  is missing in the cube 

 CMI_DIFFERENT_DB_ROLES  

DB Roles for the report and the cube do not match 

 CMI_FULL_OUTER_JOIN_NOT_SUPPORTED  

Full outer join has been disabled with VLDB setting. Some databases don’t support full outer join. This creates problem sometimes and if this is the case the engine will not use the cube. 

 CMI_GROUP_BY_ATTRIBUTE_UNAVAILABLE  

An attribute from the group by key of the report metric attribute is not available on the cube 

 CMI_FILTER_KEY_ATTRIBUTE_UNAVAILABLE  

An attribute from the filter key of the report metric attribute is not available on the cube 

 CMI_FILTERING_KEY_ATTRIBUTE_UNAVAILABLE  

An attribute from the filtering key of the report metric attribute is not available on the cube 

 CMI_REPORT_TEMPLATE_ATTRIBUTE_FORM_MISSING_FROM_CUBE_TEMPLATE  

Report template attribute is not available in the cube template 

 CMI_NO_GOOD_CANDIDATE_METRICS_FOUND  

The engine did not find an appropriate metric in the cube for the current report metric 

 CMI_METRIC_CROSS_JOINED_NO_GROUP_BY  

Cross joins are not supported 

 CMI_FILTER_NOT_RESTRICTIVE_ENOUGH  

The metric cannot be used because the engine cannot guarantee that the filter of the  cube metric did not filter out some data that is to be needed for the report metric 

 CMI_DIM_METRIC_LEAF_EXPECTED  

Expected a dimensional metric type for the metric, found something else 

 CMI_AGG_METRIC_LEAF_EXPECTED  

Expected a leaf class type for a aggregatable metric, found something else

 CMI_NON_AGG_FUNCTION_FOUND  

Non aggregatable functions are not supported in dynamic sourcing 

 CMI_DIFFERENT_AGG_TABLE_HIT  

The cube metric and the report metric get their data from different tables in the warehouse 

 CMI_COUNT_DISTINCT_FOUND  

Count with distinct parameter set to true is not supported 

 CMI_NONAGGREGATABLE_METRIC  

Non Aggregatable metrics are not supported 

 CMI_FUNCTION_EXPECTED  

Something else was found where a function was expected 

 CMI_NULL_CHECKING_FOR_ANAL_ENGINE_MISMATCH  

The value for the NULL checking for the analytical engine is different in the report and the cube 

 CMI_CUBE_TEMPLATE_MISSING_FILTER_ATTRIBUTE_FORM  

All attributes forms used in the report filter must be available in the cube 

 CMI_FACT_ENTRY_LVL_GREATER_THAN_A_FILTER_LEVEL  

The fact entry level is incompatible with one or many filter levels. For example, the filter level contains an attribute that is not found/compatible in the fact entry level 

 CMI_DISTINCT_FOUND_ON_AGGREGATION_FUNCTION

The count distinct parameter is found on the aggregation function and the level of the cube is not exactly the same as the report metric level

CMI_JOINT_PARENT_OR_JOINT_CHILD_OR_MANY_TO_MANY_NOT_SUPPORTED

Joint parent and joint child relationships are not supported. If possible remove one of the children that have a joint parent or one of the parents that have a joint child. Many to Many reklationshios are not supported either, one of the attributes in a many to many relationship may need to be removed to make it eligible for Dynamic Sourcing.

 CMI_METRICS_WITH_NESTED_AGGREGATION_NOT_SUPPORTED  

Nested aggregation is not supported for dynamic sourcing.

 CMI_UNSUPPORTED_ELEMENT_IN_FILTER  

Some unsupported element has been used in a filter

 CMI_UNSATISFIABLE_CONDITION_IN_FILTER  

An unsatisfiable condition has been introduced in the filter 

 CMI_IF_NO_METRIC_REPORT_AND_CUBE_LOWEST_LVL_MUST_BE_THE_SAME  

 If the report contains no metrics, it can only hit cube that is exactly the same level as the report

 CMI_NON_HDA_USER_CANNOT_USE_HDA_CUBE  

The current user does not have the Use Heteregeneous Data Access (HDA) reports privilege, so it cannot use cubes that use the HDA feature. 

 CMI_DISTINGUISH_DUPLICATED_ROWS_MISMATCH_FOR_CUBE_AND_REPORT  

The current report cannot use the current cube, because the values for the "Distinguish Duplicated Rows for the Analytical Engine" setting do not match 

 CMI_VLDB_SETTING_MISMATCH_FOR_CUBE_AND_REPORT  

The current report cannot use the current cube, because the values for a VLDB setting that can change the report results do not match 

 CMI_METRIC_BREAK_BY_NOT_ON_CUBE_TEMPLATE

The break by of this metric is not on the cube template 

 CMI_DB_ONLY_FUNCTION_IN_METRIC_FORMULA

The report cannot use dynamic sourcing because there is a database only function in the metric formula 

 CMI_DIFFERENT_METRIC_FORMULA

The metric cannot be used because the metric formulas are different 

 CMI_FACT_NOT_SUPPORTED_AT_REQUIRED_CUBE_LEVEL

A fact is used in the report that has an entry level higher than the level of the recommended cube.

 CMI_USER_LOCALE_NOT_SUPPORTED_IN_CUBE

Cube is not available in the user locale.


Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2023

Last Updated:

January 31, 2024