KB32541: What features are not supported when using Dynamic Sourcing in MicroStrategy?

Dynamic Sourcing is the technology that allows ad-hoc report, standard reports and OLAP reports to access shared Intelligent Cubes in an automatic way.
 
The benefits from using Dynamic Sourcing are:

• Better performance for all kinds of reports.
  
• Easy to set up, to enable Dynamic Sourcing we just need to turn on a switch and tune some settings.
  

However, there are some features that will not support the use of Dynamic Sourcing because we cannot guarantee that the information retrieved from the cube will be the same as the one from the database server or because the feature is not supported yet in Intelligent Cubes or in Dynamic Sourcing.
 
The following are the features that are not supported as of current Strategy versions:
 
Features in Intelligent Cubes that are not supported for Dynamic Sourcing:

• The following set qualifications in the Intelligent Cube filter:
  
• Metric qualifications
  
• Relationship qualifications
  
• OR, AND NOT, OR NOT logical operator in the report filter.
  
• Use of Pass-through functions such as ApplySimple in metrics.
  
• Report as filter used in the Intelligent Cube filter.
  
• Report limit.
  

Besides the above features that disable the whole Intelligent Cube to be used in Dynamic Sourcing, the following features, disable only the metric that contain such feature. That is, it could be the case that other metrics do not posses such features and then they could be used by Dynamic Sourcing:

• Metrics that use facts with fact degradation or fact extension.
  
• Conditional metrics
  
• Compound metrics not defined as smart.
  

Report features or objects that are not supported for Dynamic Sourcing:
 

• Consolidations
  
• Custom Group
  
• Query Builder or Free Form SQL reports cannot be used.
  
• MDX reports using SAP BI, Microsoft Analysis Services or Hyperion Essbase.
  
• The following set qualifications in the report filter:
  
• Relationship qualifications that do not include a filter in their definition, or that use a different Relate By option than Use System Default.
  
• Metric qualification.
  
• OR, AND NOT, OR NOT logical operators in the report filter.
  
• Metrics that use pass through functions like ApplySimple.
  
• Metrics that use facts with fact extension or degradation.
  
• Data marts
  
• Report as filter used in the report filter.
  
• Using any of the following VLDB properties: