Multidimensional Expressions (MDX) is a query language for online analytical processing (OLAP) using a database management system. Much like SQL, it is a query language for OLAP cubes.
I am trying to figure out how to compare two dimension values in a MDX query such that records where two dimension values are the same will be filtered out.
To test this, I have modified the HoleFoods cube in SAMPLES namespace to have a new dimension called RandomRegion
I want to create a MDX query where the [Outlet].[H1].[Region] value is not equal to the [RandomRegion].[H1].[RandomRegion] value.
A calculated measure is a powerful feature in DeepSee and can help to enrich your analyzes. In the case of complex or long running computations plugins can be useful. This article shows with a simple example how you can build and use a plugin in DeepSee.
I need to create a KPI similar to the DeepSee.Model.KPIs.DemoTrendLines kpi in Samples. This kpi supports a scorecard widget with a trend line. It shows patient counts by city with a trend line of the count of patients over a decade. What I want is to show the trend line based on the average allergy score ([Measures].[Avg Test Score]). A pivot table query that shows the data I would want to base the trend line on is:
I'm trying to calculate the percentage of the top level with the SUM function. But I don't understand the PARENT behavior. It does not work in any way!
Using cube CubeA and cube CubeB that contains calculated measure TotalClients. I would like to use TotalClient calculated measure from a compound cube CubeC (CubeA,CubeB).
In DeepSee, having a customer account cube. The cube includes a time dimension AccountCreationDate.
How do you create a calculated measure to get the total number of accounts from the beginning to a certain date in abscissa ?
I tried many things including this:
AGGREGATE(%TIMERANGE([AccountCreationDate].[H1].[MonthYear].&[190001],[AccountCreationDate].[H1].[MonthYear].CURRENTMEMBER) ,[Measures].[%Count])
But I don't get the right result because the date in abscissa creates a filter on the first date.
I have a dashboard which shows the growth of the months compared with the month from the last year.
The way I found to develop that, it was with a kpi. So, I overrode the %OnLoadKPI method with two mdx:
SELECT NON EMPTY [DataD].[H1].[MothYear].Members ON ROWS, [Measures].[CountVisits] ON COLUMNS FROM SubjectAtendimento %FILTER [DataD].[H1].[Year].&[2016]
SELECT NON EMPTY [DataD].[H1].[MonthYear].Members ON ROWS, [Measures].[CountVisits] ON COLUMNS FROM SubjectAtendimento %FILTER [DataD].[H1].[Year].&[2015]
The DeepSee Shell best Practices Series - Execute an MDX query in the DeepSee Shell with/without results cache
This cache is different from cache reset. Cache reset clears everything in the namespace but “cache off” only clears the cache in ^DeepSee.Cache.Results and ^DeepSee.Cache.Axis global node for the corresponding cube. The difference is quite smaller in the case as below, but in some cases it can be a big difference.
The DeepSee Shell Best Practices Series - Reset your DeepSee cache in the DeepSee Shell
This method is provided as a convenience for developers for use on development or test systems. You should not use this method on production systems as it will have immediate effect on the performance of end user operations.
Hi! I am working on a project and I am facing a weird problem. I have created an MDX using Analyzer. This MDX executes very fast. I am trying to automate its execution with %DeepSee.ResultSet and the query never returns:
Set tSC = oMDX.%PrepareMDX(tMDX)
Quit:$System.Status.IsError(tSC)
Set tSC = oMDX.%Execute()
Quit:$System.Status.IsError(tSC)
What could be causing %Execute() to take so long to run while Analyzer is responding fast?