SYMPTOM
A user wishes to create a new project to access an MDX Cube data source in Strategy Developer 9.4.1 and 10.x by performing the following steps:


CAUSE
This behavior is by design.
From the user's perspective, it may appear to be self-evident that the main warehouse for a project whose primary purpose is to connect to SAP BW, Microsoft Analysis Services, or Hyperion Essbase should be the MDX Cube database instance. From the perspective of the Strategy object model, however, this is not the case.
In a Strategy project, the 'Warehouse Database Instance' always refers to the ODBC database instance (for a SQL-based database) that will be used for SQL generation and execution of standard Strategy reports.
MDX Cube data sources fall in the domain of Extended Data Access, and are separate from the primary project warehouse. A project can have only one warehouse database instance, but it can have several MDX Cube database instances. Even in Project Configuration, is not possible to set an MDX cube database instance as the project's primary warehouse, so it would be inconsistent to allow that type of selection here.
The wording of the second stage in the Project Creation Assistant is precise: to 'Select tables from the Warehouse Catalog.' OLAP Cubes are not imported using the Warehouse Catalog, but rather by the OLAP Cube Catalog. So the user should not expect to see OLAP Cube database instances in this dialog, because there are no SQL tables to import from an OLAP Cube provider.
ACTION
The correct procedure to create a new project for MDX Cube access is as follows:


