STEPS ON HOW TO DELETE A PRIVATE SUBSET IN TM1

[segunfunwaoluwa]

Hi everybody,
I would appreciate it if anyone could show me the steps to use in deleting a 'private subset' in tm1.I have gone through the TM1 online documents and all it shows are the functions to call but not the steps on how to go about doing the delete.Pointers anyone?
Thanks
Segun

[Steve Rowe]

It can't be done as an admin, only as the user concerned through the front end, or by directly in file system which will break any assocaited views.
Cheers

[segunfunwaoluwa]

Thanks Steve for the reply,could you please elaborate the steps the user needs to follow to do the delete?
Thanks.
Segun

[lotsaram]

Thanks Steve for the reply,could you please elaborate the steps the user needs to follow to do the delete?
Thanks.
Segun

Huh? How about "use the delete key".

[Wim Gielis]

Segun

Let the user navigate in the Server Explorer to the respective dimension and subset.
Select it and click Delete.

That's it.

Please do not use all capital letters in your topic title. Thanks.

[Alan Kirk]

The question is unclear. There's no indication of which part of the interface we're talking about but the reference to "functions to call" suggests that it may be TI.

TI cannot directly delete a private subset. It only deals in public ones. The only way to delete a private subset in TI is by using the AsciiDelete function to perform that task that Steve was alluding to; that is, deleting the .sub file that will be found in the DataDirectory\UserName\DimName}subs folder. The deletion will not be visible until the user logs out (if they're already logged in) and back in. As Steve mentioned, you also run the risk of corrupting any private views that the user may have created so this would not be an approach to take lightly.

[segunfunwaoluwa]

Thanks for the pointers guys.Checked it out myself by creating a private subset and then right clicked on that particular private subset and chose 'delete' and issue was resolved.Went ahead to convey the same steps mentioned to my user.Still awaiting a response but believe that the steps mentioned will resolve the issue.Thanks everyone.
Segun.