CUBE-AREA or MDX-SET
The CUBE-AREA or MDX-SET terminal in the MaxL language represents an Essbase cube area, region, or other data set specification, developed in MDX as a symmetric, syntactically-valid set.
The area specification must be static; for example, it cannot contain Dynamic Calc members or MDX runtime functions such as Filter, TopSum, or BottomSum. Enclose strings containing spaces or special characters in square brackets ([]). Check the MaxL statement examples for other quoting requirements, which may differ depending on what you are doing.
Type
string (see MaxL Syntax Notes)
Examples
The following is an MDX set of siblings.
'{[Jan 2000], [Feb 2000], [Mar 2000]}'The following is an MDX crossjoined set.
'{([Qtr1], [New York]), ([Qtr1], [California]),
([Qtr2], [New York]), ([Qtr2], [California])}'The following MDX set is also a tuple.
'{(Jun, FY2011, Actual)}'The following MaxL statement clears data from a region of ASOsamp.Basic. The region to clear is expressed using MDX.
alter database ASOsamp.Basic clear data in region '{(Coupon, [Prev Year], South)}' physical;The following MaxL statement creates a trigger that logs information based on a condition. The CUBE-AREA region to track (after the where clause) and the CONDITION to test for (after the when clause) are expressed using MDX.
create or replace on update trigger Sample.Basic.NYCola where (Jan, Sales, Actual, [100-10], [New York]) when [New York] > 20 then spool EastColas_Fail end;