Skip navigation.
spilling the beans

MDX

Duplicate elements in rollups

admins
| | |

Large nested rollups can lead to elements being counted twice or more within a rollup.
The following process helps you to find, across all dimensions of your system, all rollups that contain elements consolidated more than once under the rollup.


Comments

developers
|

Comments allow you to explain, to yourself and/or to your users, what the query is trying to achieve, how it works, who wrote it or amended, etc.

Use "//" or "—" (without the double quotes) to end a line with a comment or to have the comment on its own line.


Syntax and Layout

developers
|

A query can be broken over multiple lines to make it more readable. For example:
{
FILTER(
     {TM1FILTERBYLEVEL( {TM1SUBSETALL( [Product] )}, 0)},
       Test2.([Rate Measures].[Rate]) = 19


a closer look at subsets

developers
| |

if you ever loaded a .sub file (subset) in an editor this is the format you would expect:

283,2 start
11,yyyymmddhhmmss creation date
274,"string" name of the alias to display


Creating Dynamic Subsets in Applix TM1 with MDX - A Primer

developers
| |

Lead author: Philip Bichard.
Additional Material: Martin Findon.

About This Document


Syndicate content