TM1 Forum

Interesting idea but would raise the question of; If you know which of the elements is going to be calculated as part of the consolidated calculation then why use ConsolidatedMax at all? You could just say one is equal the other (or if there are no other measures just weight only that element.) It ...

Consider a measure where N-cells are being rule-calculated. Also assume that @ C-level I have one of the following functions: ConsolidatedMax, ConsolidatedMin, ConsolidatedAvg, ConsolidatedCount. To get the ConsolidatedAvg or ConsolidatedCount functions to calculate correctly, ALL the N-level cells ...

Assuming your cube has 4 dims dim1, dim2, dim3, dim4 and the measures dim has elements: Kgs, metres, GroupAverage And assuming you want to average on a consolidated element 'Total of dim3' on dim3, your rule would look like this. your Clevels rules should be fine, and your N level rule would go like...

The loading time for a cube usually depends more on the "write to cube" speed than the "read from source" speed. One quick way to identify the cause of the delay is to create a dummy cube with the same dimensions as the regular cube to which you load. The dummy cube shouldnt have...

I disagree on the concept of always taking one approach over the other. Yup. :) I was not suggesting the TI process approach as a 'one size fits all' or that I was stating gospel truth. I put the "my belief" disclaimer up front. In the specific example DJ gave, the requirement was a simpl...

My rule of thumb: any TI process that offers functionality that did not naturally exist in Architect in 9.5.x, should not be tried in Architect. There's a lot that PM can do that doesnt gel back well with Architect. One of those is the TI process created when you set up a link as TI than as a rule. ...

A. TM1 is a viable choice: It is not the PERFECT solution for storing property info: but it's definitely not the worst either. B. Identifying what goes into dim, what goes into attr, and what becomes a measure will be crucial. As Alan rightly points out, you will need to think about the reports the ...

The is theotical, and while possible this is a ot of effort when you can jst have a look, The worth lies in having to pull out this information from a server that has 300+ dimensions. DJ, The below TI code will TextOutput a list of Dimension, their measure elements and the specific picklist used in...

As Declan very kindly pointed out, you CAN do this purely using rules only by adding a cube which has the extra dim. From having tried both approaches, I am firmly of the belief that the effort involved in writing the rules and feeders, especially if you want to go from a source cube with Dims, 1, 2...

once a cell received a value in the past and was also correctly fed, TM1 keeps remembering that a value has been in that cell and thinks it is still in there, even though I have deleted the input for that cell and it is back to zero This stinks of UNDEFVALS... Alex: do you have undefvals; in your r...

Dev, the way rules in TM1 work is this... Going down a rule file, once a rule is found that applies to a cell (or area or slice), no other rule will apply to that same cell (area or slice). If your rules in cube 3 are like this: [] = N: DB ( Cube2, !dim1, !dim2, !dim3, !msr ); [] = N: DB ( Cube1, !d...

Tom's code snippet should do the trick. But I've always wondered about the need for creating a copy of a dim with exactly the same elements: i have the same dimension as the cube1 but with another name, but the exact same elements. I can understand there's a valid case for doing this if you have an ...

What is the TI process doing? cube loads? or dim modifications as well? It is tough to help without further details. Please remember that the word 'lakh' (meaning 'a hundred-thousand') is not in common usage outside of the Indian sub-continent. Your problem seems to be that with 4 times as much data...

Does any of the other dimensions in Cube ABC have an element called 'Agts'? The error about ambiguous element is telling you that it is not able to identify which agts element to feed from: ['agts']=>db('cubepqr',!dim1,'agts'); should be corrected as (if I'm understanding you right that you wanto us...

beek, Wim Gielis was suggesting that you re-do the structure of your measures dimension so that it looks somewhat like this D |- E |- A |- B |- C Assuming you give each child element a weight of 1, this structure takes care of the calculations without the requirement for feeding. If you have simple ...

Seems to me that static subsets should do the job?

Open subset editor, select the elements you want ( 1,2,4,6,8,10), remove other elements, and save the subset as A.
Rinse and repeat for subset B.

Why would you need "dynamic" subsets for this?

... but you can't protect someone from ... following their GPS off a cliff. Loved that one, Alan! :D I create my dims (and attributes) in TI processes (it helps me in migrating stuff between my DEV / QA and Prod environments). And I always immediately add a minimum of one element to the dim immedia...

Chittem,
What version of TM1 are you using?

In the source cube: Consider putting this feeder in and let me know if it works: The dim order might not match (since I dont know the dim order in your target cube ,or its name) ['BU Qty'] => DB ( 'TGT_Cube' , 'Actual', !Brands, !Components, !Providers, 'FY' | SUBST(!TimeMonth11Months , 6, 4), 'FY' ...

The rule in the T(arget) cube is something like ['Measure1'] = DB('S', 'DI_' |ATTRS('DimTime', !DimTime, 'Year'), 'Measure2')*DB('VAT', ATTRS('DimTime', !DimTime, 'Year'),'value'); Meanwile, you can try feeding to the consolidated element: If DI_2012, feeds to 2012 (the consolidated element), it fe...