TM1 Forum

It was actually same elements across dimensions and spaces in my dimension name causing the ConsolidateChildren not to work. Added the 'dimension name':'element' and that started working. I added C: and N: rules to accomplish what I was looking for. ['variance']=C:IF(ELLEV('Period',!Period)>0, [unit...

so basically how do i deal with both being consolidated at the same time? I want the period to perform a calculation and the product to just consolidate its childern. (ConsolidateChildern('Product') always returns a missing colon error) This is what i assume you mean: [measure]=if(ellev('Product',!P...

A general question here on how to control when a rule consolidates versus calculates across dimensions. Take for example you have a cube with the following two dimensions: product and period The product dimension has a couple levels: Total Products Product Group 1 Product 1 Product 2 ... The period ...

Outside of creating alternate rollups, is there any way to have a consolidation only reflect the elements that a user has access to? For example the user below would only have access to Golf and all of its ancestors and descendants: All Products = 100 -Camping = 26 --Tents = 18 --... = 8 -Golf = 74 ...

When you say headaches, do you mean from a performance standpoint or write capability or something else?

Thanks for the help everyone. I ended up taking a different approach. In my time dim I added an attribute for the last value: for consolidations it is the element value of the last child(grandchild), for elements it is its own value. In addition to this I added a second measure element ('Rollup'). H...

Same result. I am working with a simple single cube, with 4 dimensions and one measure. Maybe asking the question in a more generic way would help. What rule would be used to provide the last child of a consolidation for a specific dimension while maintaining the sum for other dimensions? Based off ...

Sorry, I wasn't implying there was anything wrong with the rule. It is clearly something in my cube but not sure where to start investigating. My response was more a question of if this scenario happened with that exact rule what could be the possible reasons for it? The Acct (1) and Acct (Y) are co...

Needs to be the same hierarchy. The end goal would be something like this: ###### Jan09 | Feb09 | Mar09 | Q1/09 | ... | Oct09 | Nov09 | Dec09 | Q4/09 | 2009 Acct (1) 15000 | 20000 | 10000 | 45000 | ... | 32000 | 12000 | 14000 | 58000 | 183000 ... Acct (Y) 10000 | 12000 | 15000 | 15000 | ... | 20000 ...

Thanks for the response. I like the idea of the attribute flag and have since added that to my account dim. The issue I face now is when I add the rule as specified the value for the 'Amount' always returns 0 (for elements and consolidations) where the flag is 'Y'. If I comment out the rule I get th...

I am trying to develop a rule where the consolidations at all levels of the date dimension displays the last childs value and not the rollup of the value. To complicate this further the consolidation only needs to behave this way when viewing a specific section of the accounts dimension. Here is my ...