TM1 Forum

If so, and if you would be happy to maintain a separate dimension with only the leaf items in it, then you could create a cube weight to calculate the contribution of each leaf to the top. It would have the dimensions hierarchy and leaves and the following rule [] = N: IF( !hierarchy @= !leaves, 1, ...

Is the problem that each leaf item must contribute only once to the top level, regardless of there being potentially multiple parentage paths between it and the top?

I suppose this is a text cell (S on the last dimension) that you are using. If you set a picklist of non-numeric items on a numeric cell you will get this error message. Perhaps one for John Hammond's list.

Why not set the element weights on the time dimension so that for normal consolidated periods only the last child period counts? If you need to use the time dimension in another cube that has normal aggregation then create and maintain two time dimensions, one for each method. You might also need on...

Try this.

Created a calculated measure showing 1 for the rows you want to include and 0 otherwise. Then do an extract on only that measure. Skip 0s but include rule calculated values. Then use CellGetN to get the revenue and volume numbers directly out of the cube for those rows.

In this ideally when the user looks at the cube the % should be based on the elements selected and the value for the total months. Thanks. If this is the case why not just divide by the figure for total months, leaving the elements on the other hierarchical dimensions unspecified? ['Amount %','Actu...

It look from what you say Bhaskar as though the running of the report is causing the ABCserver service to stop. Can you confirm if this is the case, and if so are you certain?

If it is the case have then what happens if you open the cube in one of the normal TM1 UIs?

If you are using SubsetCreateByMDX you will need to make sure that the dimension has at least one element that satisfies the MDX condition. If the MDX returns an empty set then the call fails. If you are only creating subsets for the values of the attribute that appear in the current members then yo...

How about ...

Change the current month source to contain <EDIT>the string</EDIT> then change the test to be Would that work?

If you could reply attaching the process (file with .PRO extension) that builds this dimension and the datasource from which it get the members it will be easier to see what the problem is. I am presuming by the way that this is a continuation of the "Filters in TM1" thread.

Cheers,
Duncan.

Further to what lotsaram said about how they appear in the subset editor, they actually seem to be implemented as string type elements so that if you write a rule on an }ElementAttributes_* cube all the definitions need to be of the form S:. This also has the effect that there is no consolidation of...

This code works for me in 9.5 and I am pretty sure it did in 9.4 as well. # Type may be AS, AN or AA for string, numeric or alias attribute_type = DTYPE('}ElementAttributes_' | dimension_name, attribute_name); I notice that you talk of an }Element_Attributes with an underscore between Element and At...

Thanks Steve. It occurred to me last night that this doesn't handle negative numbers at the leaf level. To do this you would need to take the absolute value and keep track of how many minus signs there were. Something like this :- ['isnegative'] = N:IF(0>['data'],1,0); ['iszero'] = N:IF(0=['data'],1...

Sorry if this is reviving an old post. I came across it in a search for something else and have an alternative answer to the original post. If you create a new measure (called e.g. "logarithm") and calculate it using the "LN" function ['logarithm'] = N:LN(['data']); then at the c...