TM1 Forum

I am having an issue with the Dimension Editor and Deleting an Element. I ran accross an element that made its way into a dimension with invalid characters (See Attached Document). When I try to delete it the element appears to be deleted, but it is really still there. I have tried it through my account and through the regular admin account with no luck. I have even tried editing the Dim file with very poor results (the server stopped booting). I am sure this is a bug that needs to be handled, but how can I delete the element while I wait on support?

TM1 functions fine with this element, but EV does not know how to handle it. It is only this element that is affected, I can delete others.

It is in the signature, but 9.4 MR1 FP1 on 64 bit Windows 2003.

Hello,

I would try the following:

0. create a backup of your model
1. export the FcstEmployee dimension into a cma file
2. create a dimension worksheet FcstEmployee from Perspectives
3. copy the content of the cma file in it expect for your bad element name
4. save the dimension from Perspectives

Regards,

Peter

PS: are you sure that you deleted the element from the dimension? I mean try a right click on the element and choose delete element from dimension instead of using the Delete button of the keyboard.

Thanks. I always forget about the dimension worksheets, all our dimensions are made through sql so I never use them. That will work out great since I was trying desperately to avoid a TI process. The effort to get the TI promoted up through the ranks was not worth the effort, the xdi method will work out great.

Why not just write a very simple TI with one line on the prolog?

DimensionElementDelete(DimName, ElName);

- A much simpler workaround than exporting the whole dimension ...

Edit: Sorry George posted this after seeing Peter's post but not really reading your response. Why would "promoting" a TI be so difficult. Do it on dev then promote the dimension? (Also what is the point of strict rules about object promotion if it is apparently OK to workaround with an xdi? Surely this circumvents the whole point of promotion policies and a xdi should be subject to the same rules??)