Blank row

[JKowalski]

Hello,

I would like to know that it is possible to make empy elements in dimenssion which you can fill in the future withou distroy the cube. Because if I have a 3 elements in dimension and I add next one my cube is change and the new element is other calculation or similar function then other. I want to have a 10 elements formatig exactly the same and fill them when I will need. Is possible to do something like that?

[David Usherwood]

I would like to know that it is possible to make empy elements in dimenssion which you can fill in the future withou distroy the cube.

No. Elements cannot be blank.

[tomok]

It sounds like you are confusing the terminology and saying "element" when you really mean "dimension". Adding a new element to an existing dimension in no way destroys or invalidates a cube. TM1 wouldn't be much of a product if it did. Adding a new "dimension" to a cube basically destroys it, you have to rebuild it (unless you are using performance modellor).

You can add placeholder dimensions to a cube but it's not best practice. I would never do it unless I was certain I needed another dimension and then, if that was the case, why not go ahead and add it now.

If you are really talking about "elements" then yes, you can add blank ones, they just have to actually have a name like "Blank_1", "Blank_2",... though I can't think of any good reason for doing so.

[Alan Kirk]

If you are really talking about "elements" then yes, you can add blank ones, they just have to actually have a name like "Blank_1", "Blank_2",... though I can't think of any good reason for doing so.

An HR budgeting model for one. "New Employee 1", "New Employee 2", etc when it's expected that there will be additional or replacement staff during the year, but details of the names, salaries, much less ID codes won't be known at the time of entry. Same applies to theoretical products if budgeting is being done by product. Same applies to production costings where multiple jobs are being budgeted for during the year but the specifics of the jobs aren't known at the time, and likely rather than definite job parameters are used in the budget. There can be any number of reasons for using "New" / "Blank" / "Job" elements, particularly in a budgeting situation.

Sometimes it works better if you provide the users with an action button to add such elements on demand so that users only add the elements as they're needed, sometimes it works better if you pre-prepare the elements and just let them use those. Part of that depends on the level of sophistication of the users.

[tomok]

If you are really talking about "elements" then yes, you can add blank ones, they just have to actually have a name like "Blank_1", "Blank_2",... though I can't think of any good reason for doing so.

An HR budgeting model for one. "New Employee 1", "New Employee 2", etc when it's expected that there will be additional or replacement staff during the year, but details of the names, salaries, much less ID codes won't be known at the time of entry. Same applies to theoretical products if budgeting is being done by product. Same applies to production costings where multiple jobs are being budgeted for during the year but the specifics of the jobs aren't known at the time, and likely rather than definite job parameters are used in the budget. There can be any number of reasons for using "New" / "Blank" / "Job" elements, particularly in a budgeting situation.

Sometimes it works better if you provide the users with an action button to add such elements on demand so that users only add the elements as they're needed, sometimes it works better if you pre-prepare the elements and just let them use those. Part of that depends on the level of sophistication of the users.

The scenario of which you speak is not a blank, at least as far as what I was talking about. I was talking about blanks just to fill in rows so that adding them in the future wouldn't "destroy" the cube.

[JKowalski]

I think about elemenent there wasn't mistake. Thanks for your replay. I should find other solution for my problem.

This time I have an another question involving creation apllication in TM1 Performance Modeler. When we define applicatio everything is clear despite control dimension. I found information that we need it when we want to use approval hierarchy to more than one application, but nobody write what we should use in control dimension. Do you know?

Addlitional, I would like to know that there is possible to create two approval hierarchy for one application?