KEY_ERR in data slice from 10.1

[Nessie]

Hi,

We have some slices etc which uses the alias of one particular dimension i.e. Project Code and Description instead of only the Project Code, for example, we select the alias to show '1234 Computer Room Replacement' instead of just '1234'. The numbers do not pull through (using DBRW) and show *KEY_ERR in the excel slice.

If I change '1234 Computer Room Replacement' to '1234' in excel and refresh then the numbers appear.

This slice was working fine in version 9.5 but we have just upgraded to 10.1 and now have this problem. Even if I recreate the view in TM1 and run a new slice the problem still occurs.

Is this a known bug? Is there a fix?

Thanks

[lotsaram]

As opposed to any specific issue with 10.1 I think your issue is a general one that has been around for quite a few versions where attributes can become "unattached" from the dimension. It is difficult to spot as the attribute values are still there and can be browsed in the }ElementAttributes cube and in subset editor it is still possible to toggle aliases on and off, and normal cube viewer with alias values on is unaffected However the symptoms are:
- in subset editor when the properties pane in on all the attribute values for the non-alias attributes will display a #ERROR! message not the attribute value
- if a DBR(W) formula in Excel or TM1Web tries to reference an alias value on an affected dimension where attributes are "not attached" will return KEY ERR (what you reported)

A server restart usually fixes the issue. But there is a quicker "local fix" in IBM parlance ("bug workaround" for the rest of us) where if you force a dimension recompile then the attributes will "re-attach". The easiest way to force a dimension recompile without changing the dimension is to add a dummy element and then delete it again. [We have had this issue so frequently on 9.5.1 and 9.5.2 we actually developed some housekeeping processes to run and loop through and recompile all key reporting dimensions whenever we noticed this or a user reported it.]

If you search the board you should find this has been discussed before and you might even find code snippets for the dimension recompiling.

[Nessie]

Thanks lotsaram. We did a server refresh and this fixed the issue.

Thanks
Nessie