TM1 Forum

Hi All,

This is weird.
I can enter the values in the cube and it works fine - the cube accepts the manually input values,
but
when I slice to Excel or manually build the same I receive *KEY_ERR from the DBRW instead of the values,
if I try to type over this, I receive "T1) Write Access Denied" and the value changes to #N/A ????
If I generate an Active Form I get a blank form with only the top column headers, no data in the rows - TM1RPTROW doesn't generate the rows.

Notes:
1. I can change values in the cube
2. I am trying to change all N-level values which are not effected by Rules
3. All this worked fine prior to upgrading from TM1 9.4.1 to TM1 9.5.1...
4. This only effects new slices - all Excel reports/templates built prior to upgrading work fine, however, parts of those existing templates also have the same error

Any ideas would be much appreciated.
Are any of you aware of anything in Excel that could be causing this behaviour.

Cheers

Admin Note: Moved, yet again. Will people PLEASE read the How To Make A Bug Post topic before posting in that forum.

Hi All again,

Just discovered that when I turn off an alias on one of the dimensions the slice works.
This alias is unique and only applies to that dimension's elements.

Still weird.

Cheers

kbana wrote:Hi All again,

Just discovered that when I turn off an alias on one of the dimensions the slice works.
This alias is unique and only applies to that dimension's elements.

Still weird.

Cheers

It's known to be an issue if the alias changes between reboots of the server. Not always, just sometimes. I've encountered it over a range of versions and because it's impossible to reproduce reliably (and therefore raise a service request for) it wouldn't surprise me if it's still showing its head in 9.5.

great thanks...

still weird as these aliases have not changed for over a year now. And the server has not been restarted, it just suddenly stopped working. The upgrade took place over a month ago.

The alias is for an element called SandBox4 (alias to Scenario4) in the Version Dimension. My gutt feel is that the use of element names "SandBox#" could be conflicting with 9.5's onwards Sandbox capability and thus causing this issue.