TM1 Forum

Hi All,

When we create a pick list for cube it will be generated as a contol cube.
We can remove }cube_name.cub from Data Directory to delete that.

Is there any other way for deleting control object?

Regards,
Deepak Jain

deepakjain2020 wrote: Is there any other way for deleting control object?

You can delete control cubes through TI. I've done that in the past when an element security cube was incorrectly created. It doesn't require a reboot the way that that deleting from the data directory does.

But of course... proceed with extreme caution.

Hi Alan,

So using the function

CubeDestroy(}cube_name) will delete only specific cube, right?

Alan Kirk wrote:

deepakjain2020 wrote: Is there any other way for deleting control object?

But of course... proceed with extreme caution.

What are other things we need to take care off as part of caution?

Regards,
Deepak Jain

deepakjain2020 wrote: So using the function

CubeDestroy(}cube_name) will delete only specific cube, right?

One would certainly hope so, for it would be the mother of all bugs if it didn't.

deepakjain2020 wrote:

Alan Kirk wrote:

deepakjain2020 wrote: Is there any other way for deleting control object?

But of course... proceed with extreme caution.

What are other things we need to take care off as part of caution?

Mostly:
(a) That the cube name that you type as an argument to CubeDestroy() is the intended one;
(b) That it's a control cube that you genuinely intend to destroy;
(c) That you fully understand what the control cube is doing, why it needs to be destroyed, and what the consequences of that destruction will be.

Fail in any of these three, and the deletion of any system object can cause your entire day to take on a rather bleak aspect complete with hair pulling, wailing and the gnashing of teeth.

Thanks Alan

One more question, Why the delete option is disabled for control objects any idea?
Is it because those are the auto-generated?

Regards,
Deepak Jain

deepakjain2020 wrote: One more question, Why the delete option is disabled for control objects any idea?
Is it because those are the auto-generated?

At a guess it's just a safety precaution and a discouragement to do it. If they could be deleted by the GUI it would be too easy for a novice admin to delete a system object thinking that it served no purpose, only to find out that they were wrong about that. (Say, blowing away an attribute cube and not realising that a previous admin was using one of the attributes in some rules.) On the other hand if you go to the effort of deleting a system object through TI or through removing the object from the data directory, it's generally going to have been given a bit of thought. I think it's really more intended to be a warning than a barrier.