TM1 Forum

Again, what's on rows, what's on columns and what's on pages? If you have time on columns and incident on rows then from your earlier view results I would expect a view of 40500000 cells, which is very different from 8178. And also have you tried it with static subsets? Or have you created new dimen...

Ok, so now I understand. You want to loop through the elements of the dimension. itemIndex = 0; itemCount = DIMSIZ('dim'); while ( itemIndex < itemCount ); itemIndex = itemIndex + 1; itemName = DIMNM( 'dim', itemIndex ); ... the rest of your code that is using this item ... end; It may seem a bit od...

If I understand you correctly something like this should do it, normally in the "Prolog" sub-tab.

I think it would help if you said exactly what dimensions there are, and in the view that's failing if you said exactly what was on rows, columns and pages, and if you have anything other than time and incident on rows or columns to give an indication of the structure of those dimensions and what is...

A single TI will definitely single-thread, and furthermore if you kick off a number concurrently then any calculations that they do will be held in caches local to the TI threads, and only shared globally when each TI commits. This was also a characteristic of early MTQ which is why in some cases it...

When I was there I argued for a "rules cannot use aliases" config option to improve performance, but it fell on deaf ears. If your attribute cube has an alias in it I have a feeling that this recompilation used to happen whenever you wrote to any attribute, whether an alias or not. However...

If the attribute is an alias there will be performance implications as rules of cubes using that dimension will need to be recompiled.

SCAN finds the first string in the second, not the second string in the first.

HTH

There was a feature put in that SubsetCreateByMDX could take an additional argument of the dimension name to apply the subset definition to if the MDX didn't return any elements. It was put in about 2 to three years ago and I think it's in 10.1.? but definitely in 10.2. It hadn't been documented whe...

there should be no limit to the size of a number, large or small, only the precision TM1 uses IEEE754 double precision for its numbers (explained here http://en.wikipedia.org/wiki/Double-precision_floating-point_format ) and that format does have limits, if you can call them that. From that page .....

The evaluation of which dimension it is from is done at compile time - as you will see if you use an ambiguous name. There is no effect on runtime performance.

The DB function is useful, indeed necessary, within the same cube in the following scenarios Accessing string data - this can not be done with the ['item'...] syntax Accessing data where the location of the source cell depends on other data - the ['item'...] syntax only allows constant strings, wher...

I'm not sure that I would use ConsolidateChildren, as it doesn't play well with feeders. If you are doing a ConsolidateChildren over e.g. four large dimensions with multiple levels of hierarchy in each, then in order to get the top level it will be repeating the ConsolidateChildren call at each of t...

Also on closer inspection you haven't got enough closing brackets. My guess is that you haven't given a value for "if fails condition". I'm also guessing that this is because it should be 0. If that is the case try this :- ['_3552','GIP Value']=N:if(DB('}ElementAttributes_MET Cost Codes',...

I do however recollect being able to add a string element to the last dimension after doing the reorder - and everything worked fine as far as I recall.

Not that I'm advocating it mind. It's just that sometimes documentation fails to tell the full story. It might be worth experimenting.

Try

TM1 does not have the optimization that only evaluates the right of a logical expression if needs to. It is stack based and it evaluates both sides, putting their results on the stack, before it sees that they are being combined with an "&".

Is it this feature?

Easier than putting in loads of AsciiOutput statements, but quite a lot more verbose, is setting DEBUG logging for process functions.

I described how to do it here.

[Edit] and you can read the log while the process is running.