SSAS MDX Error: Two sets specified in the function have different dimensionality + Solution

when we run the below mdx query

WITH SET LastSample AS TAIL(NONEMPTY([Date].[Hierarchy].members *[Time].[Hierarchy].members,[Measures].[Overall LU SR]))
MEMBER [KPI Name] AS "Overall LU"
MEMBER [KPI Value] As KPIValue("Overall LU SR")
MEMBER [KPI Status] AS KPIStatus("Overall LU SR")
MEMBER ObjectName as "Overall LU SR"
MEMBER [Critical Threshold] as [KPI Thresholds].[Threshold1].&[Overall LU SR].member_value
MEMBER [Major Threshold] AS [KPI Thresholds].[Threshold2].&[Overall LU SR].member_value
MEMBER [Minor Threshold] AS 0
MEMBER latestDate as [Date].[Hierarchy].membervalue, format_string = 'mm/dd/YYYY'
MEMBER latestTime as [Time].[Hierarchy].member_caption
SELECT {latestDate,latestTime,ObjectName,[KPI Name], [KPI Value],[KPI Status],[Measures].[Critical Threshold],[Measures].[Major Threshold],[Measures].[Minor Threshold]} ON COLUMNS
,nonempty(LastSample) ON ROWS
FROM [DRA]

we got the below error
Executing the query ...
Query (11, 9) Two sets specified in the  function have different dimensionality.

Execution complete 
This error is misleading us ,  where are 2 Set s?   Then after many trail and error methods we identified there is problem with  MEMBER [KPI Name]  . The strange thing is  when we change the name of the member it is working fine  but it is not working with [KPI Name] but we need that name .
The final solution is we added Measures dimension to the name while selecting .

WITH SET LastSample AS TAIL(NONEMPTY([Date].[Hierarchy].members *[Time].[Hierarchy].members,[Measures].[Overall LU SR]))
MEMBER [KPI Name] AS "Overall LU"
MEMBER [KPI Value] As KPIValue("Overall LU SR")
MEMBER [KPI Status] AS KPIStatus("Overall LU SR")
MEMBER ObjectName as "Overall LU SR"
MEMBER [Critical Threshold] as  [KPI Thresholds].[Threshold1].&[Overall LU SR].member_value
MEMBER [Major Threshold] AS  [KPI Thresholds].[Threshold2].&[Overall LU SR].member_value
MEMBER [Minor Threshold] AS 0
MEMBER latestDate as [Date].[Hierarchy].membervalue, format_string = 'mm/dd/YYYY'
MEMBER latestTime as [Time].[Hierarchy].member_caption
SELECT  {latestDate,latestTime,ObjectName,[Measures].[KPI Name], [KPI Value],[KPI Status],[Measures].[Critical Threshold],[Measures].[Major Threshold],[Measures].[Minor Threshold]} ON COLUMNS
,nonempty(LastSample) ON ROWS
FROM [DRA]

Comments

Post a Comment

Popular posts from this blog

SSAS : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). + Solution

Problem : have installed Analysis service on my server machine through remote login from my service account. I am able to open Analysis services from there. When I open SSMS from the same service account on my local machine, I am not able to connect to that Analysis service. It is giving me error by saying : "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond 10.245.192.111:2382(System)." Solution : Based on my research, the issue was caused by the Browser Service account was changed to the domain account. In your scenario, you can try to connect to the Analysis Service using <Servername>:2383 instead of instance name. Or you can change the Browser Service account to "Local System".
Read more

SSIS Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces

Image
Problem : When we have Multiple Namespaces in the Xml Source which we need to load the Data from   as we shown below Then we will face a issue in generating XSD for that XML Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces. (Microsoft Visual Studio) Solution : First we need to avoid multiple namespaces to transform your source file to a format that doesn’t refer to the namespaces. SSIS has an XML task that can do the transformation. 1) Add the XML task to an SSIS   Control Flow and edit it. 2) Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem. 3) Set the SaveOperationResult property to True and expand the OperationResult branch. Set DestinationType to File Connection and the Destination to a new XML file ( ModifiedInput.XML). 4) Add the below script to a new file and save it with an xslt file extension (Input.XSLT) <
Read more