Hi all,
We are experiencing an erractic behaviour in TM1 right now.
We have TM1 9.5 deployed through Citrix and Excel 2007 is used. We have some cubes that have both numeric and string elements in the dimensions that form those cubes. For example, the developer who designed the cube had set some PL account elements to "S", and some of the measure elements are of "S" type too.
Problem:
If we enter text into the String measure elements in cube view, everything is fine. If we slice the view to Excel and enter the text into DBRW, the whole sheet recalculates but the entry is not stored.
Also, the sliced view does not show the text that is currently stored in the cube. Note that this behaviour occurs intermittently i.e. not consistent.
It appears NOT to be a TM1 version or Excel version issue as we tested it on another PC with TM1 9.4 and Excel 2003.
Possible cause:
I think the reason behind this behaviour is due to the presence of both S and N elements in more than one dimension in the cube. Perhaps TM1 gets confuse wen more than one of the elements that made up the location of the cell is "S" type and thus affecting the behaviour of the entire worksheet.
but why does it not affect the cube view? Can someone shed some lights on this? thanks!
harry
Erractic Behaviour in DBRW when entering strings
-
- Regular Participant
- Posts: 226
- Joined: Thu Apr 02, 2009 2:51 pm
- OLAP Product: IBM Planning Analytics
- Version: Latest version
- Excel Version: 2003 to 2019
Erractic Behaviour in DBRW when entering strings
Planning Analytics latest version, including Cloud
-
- Site Admin
- Posts: 6667
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Erractic Behaviour in DBRW when entering strings
TM1's not the only one; I am as well considering that you should have S elements in only one dimension in a cube:harrytm1 wrote:I think the reason behind this behaviour is due to the presence of both S and N elements in more than one dimension in the cube. Perhaps TM1 gets confuse wen more than one of the elements that made up the location of the cell is "S" type and thus affecting the behaviour of the entire worksheet.
(Page 20, version 9.5 Developer's Guide.)To include a string in a cell in a cube, the element from the last dimension defining the cell must be a string element. TM1 treats string elements that occur in any dimension other than the last one as numeric elements.
I haven't seen the behaviour that you're describing, but to avoid ambiguity (and the possibility of unpredictable behaviour) I'd suggest rebuilding your cube ensuring that you have your S elements only in the last dimension.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- Posts: 7
- Joined: Wed Aug 26, 2009 8:19 am
- OLAP Product: IBM Cognos TM1
- Version: 10.2.2
- Excel Version: 2013
Re: Erractic Behaviour in DBRW when entering strings
Hi!
You can try change DBRW function to DBR in Excel form.
We do it and it's works.
yng
You can try change DBRW function to DBR in Excel form.
We do it and it's works.
yng