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
  3. Topics

KB14037: Named sets defined in MDX Cubes in Microsoft Analysis Services do not appear in MicroStrategy Architect after importing the cube

Community Admin

• Strategy

This article notes a limitation of MDX sources in MicroStrategy

SYMPTOM
A user has defined MDX cubes in Microsoft Analysis Services. Within the cube, named sets are defined to group hierarchy members into reusable units. An example of a named set is shown below:
 

ka04W000000ObcrQAC_0EM440000002FTy.gif

 
This cube is imported into Strategy Architect using the MDX Cube Catalog. After importing the cube, the user examines the 'Cube Mapping' tab to verify how the cube objects were converted into Strategy objects. The named sets are not visible.
 
CAUSE
When Strategy imports a cube from an MDX (multidimensional expression) data source, the following mappings take place:
 


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric


 Dimension (may also be called Hierarchy)HierarchyHierarchy Level (mapped to a cube column)AttributeMember propertyAttribute formMember of Measures dimensionMetricCalculated member inMetric

 
Named sets do not correspond exactly to the categories of hierarchy, attribute, or attribute form and cannot be imported into the Strategy metadata.
 
ACTION
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release. 
 
WORKAROUND
 
Consult the following Strategy Knowledgebase article for a method to filter on named sets using custom MDX metrics.
 
KB30361: How to use a custom MDX expression to refer to predefined named sets in Microsoft SQL Server Analysis Services cubes in Strategy Engine
 
 

Comment

0 comments

Details

Knowledge Article

Published:

May 25, 2017

Last Updated:

May 25, 2017