Hello,
I noticed that if i use the function SUBNM on Excel 2003 (after an export or asking TM1 for a Active Form) the subset sends me a
"TODO" Subset that i didnt made (which in spanish means ALL) and no data is displayed, even if i press any button like "display all". On the TM1Web is working well.
I am using 9.4 MR1 FP2, excel 2003, win XP
I am attaching an Image. I couldnt find something on the forum.
Thanks
Rodrigo
Wrong Subset Behavior on Excel 2003
- rodrigo
- Posts: 49
- Joined: Tue Jun 03, 2008 10:34 pm
- OLAP Product: TM1, Executive Viewer
- Version: 9.4 MR1 with FP3
- Excel Version: 2003
Wrong Subset Behavior on Excel 2003
- Attachments
-
- subsetproblem.doc
- (129.5 KiB) Downloaded 327 times
-
- Posts: 22
- Joined: Wed Jul 01, 2009 3:53 pm
- OLAP Product: TM1 and Cognos EP
- Version: 9.4
- Excel Version: 2003 and 2007
Re: Wrong Subset Behavior on Excel 2003
Try creating a new subset (with all of the elements you want) and referring that in your Excel formula and see if that works.
- rodrigo
- Posts: 49
- Joined: Tue Jun 03, 2008 10:34 pm
- OLAP Product: TM1, Executive Viewer
- Version: 9.4 MR1 with FP3
- Excel Version: 2003
Re: Wrong Subset Behavior on Excel 2003
It worked! thanks..
=SUBNM("sdata:year","Por defecto","2008")
But this makes me wonder that using only "" for subsets doesnt work in excel slicing on ESP language by now.
=SUBNM("sdata:year","Por defecto","2008")
But this makes me wonder that using only "" for subsets doesnt work in excel slicing on ESP language by now.
-
- Posts: 22
- Joined: Wed Jul 01, 2009 3:53 pm
- OLAP Product: TM1 and Cognos EP
- Version: 9.4
- Excel Version: 2003 and 2007
Re: Wrong Subset Behavior on Excel 2003
I generally stay away from using "" in subsets simply because its not reliable especially if you keep changing whats in different unnamed subsets
-
- Posts: 51
- Joined: Thu Jul 24, 2008 6:14 am
Re: Wrong Subset Behavior on Excel 2003
I think the problem is, that the TM1-Server is set up on English, whilst you client is Spanish. So your client assumes, that there is the system-generated, always available TODO subset - but the server has only the generic ALL subset. They just don't meet where expected ...