Erractic Behaviour in DBRW when entering strings
Posted: Wed Apr 14, 2010 2:51 am
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
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