I'm facing a chalenge in a new project that I can't find a solution (at least at the moment ).
The customer wants to be able to put same values either on the leaf item of a dimension or consolidation item of the same dimension (in this case it show break down the values - I would say like Cognos Planning does).
The problem in some tests I'm doing, this can't be done even on excel perspectives saying "Cell cube is not updatable".
Is there anyone that already faced this and could resolve it ?
That functionality in TM1 is called data spreading versus data input. The difference is in data spreading you can't just select the cell and type the number, you have to tell TM1 to spread via the context menu (accessed by right-clicking on the mouse).
I know that spreading is a possibility but doesn't seem very user frendly because at the moment they use a portal where they can just input data at any level. Although I don't know yet if I'm going to be put on the spot with this, I was trying to think on a "plan b" if they demanded a similar behavior in the tm1 model.
If you get users away from perspectives (which I tend to try for most people who are doing basic input as opposed to data analysts) then the web side of things can know inherently to spread.
Or create an input cube where all elements are nodal and a ti sorts out the spreading... not particularly user friendly unless well hidden in a sexy web interface where the user doesn't even know they are executing TIs
In perspective, One has to use p ahead of each input. E.G: P500 or P1500. '"P'" stands for proportional spread.
TM1 contributor is ideal interface in this scenario to input data where you can just write the input number or paste the number.
@jviegas: Did you find any difference in the performance while entering data at consolidation versus entering data at leaf level? It seems the entering data at consolidation level would take more time as it has to break down the numbers to leaf elements.
Placing data in the consolidation will take a bit long than to place data on leaf items because it make a weight distribution for all the decendents. Yet in this case I will need to do it because its a requirement for the app.
@jviegas: In that case make similar cube with only those elements where you want to enter data (consolidated element in other dim would become leaf element here). User can do in put in this cube and than with TI you can spread back data to the main cube. You can assign button to user to run that ti. It is faster, we had implemented same solution.
dharav wrote:@jviegas: In that case make similar cube with only those elements where you want to enter data (consolidated element in other dim would become leaf element here). User can do in put in this cube and than with TI you can spread back data to the main cube. You can assign button to user to run that ti. It is faster, we had implemented same solution.
Hi dharav,
Sorry the question (I actually never did this with a TI) if I "link" data from the leaf element in Cube1 to a consolidate element in Cube2 will TM1 spread the data or should I do a loop in the data tab of the TI process.
If the spread is automatically done I admit it would solve this and actually spare me some time at this stage
Going to keep this idea because I would say that in a week or two I will get the global requirements and maybe this will be a way to solve a possible problem in the spreading and the time taken to do it.