Key Errors when Description Alias is turned on

[LeeTaylor1979]

Hello All,

I am very pleased to see this forum up and running again.

Can anyone help with the following :

I have just created 3 new elements in a dim (via edit dimension structure)

I have been into the security side of things and given appropriate people write access.

I then added an attribute for example:

Element = O8
Attribute = O8 - LTGS

At first i thought it might be the - but I have lots of other elements with this symbol and they work fine.

If anyone can point me in the right direction it would be very much appreciated.

Regards


Lee Taylor

[bihints.com]

New attributes are not updated dynamically in Excel.

You either need to restart your excel or run the macro "m_clear" that will update the attribute tables in Excel.

[ASEVEREYNS]

Dear Lee,

This is a know bug in v9.1 SP3 (although I never managed to figure out the exact circumstances under which it appears). It is supossedly fixed in v9.1 SP3 U2.

Regards,
Anthony

[Steve Rowe]

Yeah this bug has been around for ages...

If you execute the DBRW against alias that are not correct yet you *KeyErrors
then you got into SE and correct the description,
you will continue to get KeyErrors even if the alias is already set up.

Restarting the client clears the issue (as does M_clear I suspect though I've not tried this.)

[Olivier]

Hi ,

It has happen to me quite a few times,(V9.1 SP2 Update 3)

All excel templates using attributes (Any Alias of Any Dimension) will start to retrieve KEY_ERRORS.
It s not limitated to one user in particular, and therefore killing the excel session and restart the client doesn't resolve.
The only option i found so far was to restart the TM1 server.( How confortable ...)

Good luck,

Olivier

[Martin Erlmoser]

there are 2(or more) problems
- the m_clear macro / excel restart thing - client issue
- server can't handle aliases in rules & excel anymore - server issue
the server bug should be fixed in 9.1 SP3 U2 HF2!

you can jump into cold water and update the tm1server or restart him everytime.
another workaround is a process which exports all elementattributes and recreates everything (but take care when somebody writes specialcaracters like a CR LF in the database .. you will "destroy" the asciioutput file when you don't filter these things out)

[Alan Kirk]

Hi ,

It has happen to me quite a few times,(V9.1 SP2 Update 3)

All excel templates using attributes (Any Alias of Any Dimension) will start to retrieve KEY_ERRORS.
It s not limitated to one user in particular, and therefore killing the excel session and restart the client doesn't resolve.
The only option i found so far was to restart the TM1 server.( How confortable ...)

If I recall correctly, in some versions it was found that adding a dummy element to the dimension, recompiling it, then deleting the dummy element will resolve this problem as well. Don't quote me on that, but it's worth a try the next time you encounter it.

[Olivier]

Hi All,

I just had an occasion to check this out.

You don't need to add a dummy element in the dimension you want to recompile.
Uploading the dimension seems to do the trick by itself.

It fix the dimension aliases, and dbrw formula behave as expected in front of Aliases of this re uploaded dim.

The problem becomes,
It is impacting "some dimensions" and i don't see any easy way to test all dims, all attributes, to see wich need to be reprocess.

I guess upgrading is the safest to get rid of this bug ,)