3.1.4.28 GetCubeMetaData

  • Article

The GetCubeMetaData operation takes in an Analysis Services RepositoryLocation complex type object (section 2.2.4.161) and returns the associated Cube complex type object (section 2.2.4.78).

The following is the WSDL port type specification of the GetCubeMetaData WSDL operation.

 <wsdl:operation name="GetCubeMetaData" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input message="tns:GetCubeMetaDataSoapIn"/>
   <wsdl:output message="tns:GetCubeMetaDataSoapOut"/>
 </wsdl:operation>

The protocol client sends a GetCubeMetaDataSoapIn request message (section 3.1.4.28.1.1), and the server (2) responds with a GetCubeMetaDataSoapOut message (section 3.1.4.28.1.2) as follows:

  • The server (2) retrieves the data source from the RepositoryLocation.

  • The server (2) validates whether it is a trusted location, along with the user's access permissions. If it is from an un-trusted location, it is added to the list (1) of untrusted data sources.

  • The server (2) retrieves the Cube definition represented by the data source, and generates a generic Cube object with dimensions as defined in the Dimension complex type object (section 2.2.4.90) with only hierarchies and levels from the specified Analysis Services cube definition.

Exceptions:

Error code

Description

UnableToLoadFCODao

See Full List of Possible Error Codes (section 2.2.2.1.2).

DataSourceCubeNotFound

See Full List of Possible Error Codes (section 2.2.2.1.2).

DatabaseConnectionNotOpen

See Common List of Error Codes (section 2.2.2.1.3).

DataSourceHostNotFound

See Common List of Error Codes (section 2.2.2.1.3).

DataSourceConnectionUnsupported

See Common List of Error Codes (section 2.2.2.1.3).

NotTrustedLocation

See Common List of Error Codes (section 2.2.2.1.3).

DataSourceDatabaseNotFound

See Common List of Error Codes (section 2.2.2.1.3).

In case of any other failure, the error code MUST be one of the values specified in section 2.2.2.1.2. A detailed specification of how exceptions are reported by the server (2) is in section 2.2.2.1.