9.4 - renaming an element

[ccpr20]

Hello,

First time post here. We have TM1 9.4 and I am the admin. However, I am not technical. I am what IBM calls the "business owner." I am trying to rename an existing element. In this case the element is a GL account. For example, I want rename 10100 - Disbursement Account to 10100 - Lodging Disbursement Account. I go to the cube that holds the attributes for this element and rename it. Simple. Howerver, when I pull up this element in the cube viewer and slice to Excel, I get a KEY_ERR. I have the same problem when an orphan comes through. In this case, I have to name it and then place it in the hierarchy. If I place it in the hierarchy and then name it, I get a KEY_ERR.

Any suggestions? I am a novice admin. I really don't want to delete from the hierarchy and reload the entire dataset to follow my orphan naming process. The installer said this is a bug within the software.

Thanks,
Ben

[kpk]

Have you tried an Excel restart?

[Alan Kirk]

First time post here. We have TM1 9.4 and I am the admin. However, I am not technical. I am what IBM calls the "business owner." I am trying to rename an existing element. In this case the element is a GL account. For example, I want rename 10100 - Disbursement Account to 10100 - Lodging Disbursement Account. I go to the cube that holds the attributes for this element and rename it. Simple. Howerver, when I pull up this element in the cube viewer and slice to Excel, I get a KEY_ERR.

It's an issue that I've seen in quite a few versions of TM1 and unfortunately there's no predicting when it'll happen.

As per Peter's suggestion sometimes a restart of Excel will help... sometimes it won't. Consequently I usually keep alias changes to just before I do a scheduled reboot the server. After a server reboot the Key Errors won't appear.

I have the same problem when an orphan comes through. In this case, I have to name it and then place it in the hierarchy. If I place it in the hierarchy and then name it, I get a KEY_ERR.

Now that one I haven't seen, but I haven't used 9.4 in anger. Generally if you assign an alias for the first time, there are no problems with key errors in my experience. I'd try the suggestion of restarting Excel with that one, and ask other users to advise you if they still encounter problems. Also make sure that you're not assigning an alias at the time that the new element is added, otherwise it will be an alias change rather than an assignment... and as we know alias changes can potentially cause problems.

[ccpr20]

Thanks for the prompt responses. I did try to restart Excel but that did not work. I think I'll have to coordinate with IT after month-end close to do all my renames and have them reboot. If there are any other suggestions, I am open. I will report back what I find.

Again, I appreciate the help.

[kpk]

I go to the cube that holds the attributes for this element and rename it. Simple.

One question: did you use the attribute editor or opened a view from the }Attribute cube?
Try to edit it from the attribute editor to see whether any error message appears or not.

Regards,
Peter

[lotsaram]

Thanks for the prompt responses. I did try to restart Excel but that did not work. I think I'll have to coordinate with IT after month-end close to do all my renames and have them reboot. If there are any other suggestions, I am open. I will report back what I find.

Again, I appreciate the help.

It's not a restart of Excel that will help but a restart of the TM1 server.

In these instances where an alias attribute value has changed but the change in alias isn't showing up correctly forcing a recompile of the dimension itself can often solve the problem without resorting to restarting the server. The easiest way to force the dimension to recompile is to insert a dummy element, save the dimension then delete the dummy element and resave.

[Alan Kirk]

Thanks for the prompt responses. I did try to restart Excel but that did not work. I think I'll have to coordinate with IT after month-end close to do all my renames and have them reboot. If there are any other suggestions, I am open. I will report back what I find.

Again, I appreciate the help.

It's not a restart of Excel that will help but a restart of the TM1 server.

As a universal fix, yes. But I've seen instances (at least in the versions 7/8 series, haven't encountered it in a 9+ series but as I said I for one never do a rename during the day any more) where a worksheet will not recognise the new name... but is still Ok with the old one. Kick Excel over and it goes away. As with the key error itself, it's random and impossible to reproduce... but Peter's suggestion won't do any actual harm.

In these instances where an alias attribute value has changed but the change in alias isn't showing up correctly forcing a recompile of the dimension itself can often solve the problem without resorting to restarting the server. The easiest way to force the dimension to recompile is to insert a dummy element, save the dimension then delete the dummy element and resave.

Ah yes, I'd forgotten about the recompile the dim trick; good call.

[lotsaram]

Application.Run "M_Clear"
... should also achieve the same result as an Excel restart if it is a Perspectives caching issue as opposed to server issue.

[ccpr20]

Thank you for all of the posts!! Based on your suggestions, I got it to work through the recompiling route.

First, I renamed the element via the }ElementAttributes cube. Second, I inserted a dummy element in the same dimension and saved. I resliced to Excel and no KEY_ERR on the new alias.

Thanks so much.