What is it that causes a perfectly normally functioning excel TM1 report to suddenly require ENTER after selecting a different element in a SUBNM formula (when it was not required previously)???
I've seen it many times before but I can't remember what causes it...
SUBNM requires enter after selection
-
- MVP
- Posts: 3703
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: SUBNM requires enter after selection
9.4.1 FP2 has a few bugs in how it handles incomplete SUBNM formulas. The issue you describe is usually preceded by a "VBA error 13: Type mismatch" in the tm1p.xla VBA module, this disables TM1 handling the double-click event that fires the subset editor until the code break is reset (usually be performing another action such as a fresh slice or possibly a recalculate would work as well).
-
- MVP
- Posts: 263
- Joined: Fri Jun 27, 2008 12:15 am
- OLAP Product: Cognos TM1, CX
- Version: 9.0 and up
- Excel Version: 2007 and up
Re: SUBNM requires enter after selection
Hi
Might want to give the good old 'Edit directly in cell' option a try.
Cheers
Might want to give the good old 'Edit directly in cell' option a try.
Cheers
-
- Posts: 62
- Joined: Wed Sep 02, 2009 11:33 am
- OLAP Product: TM1
- Version: PA 2.0.9.4
- Excel Version: 2016
- Location: Australia
Re: SUBNM requires enter after selection
HA - had a brain wave and I've cracked it!!!
It must be a bug (not sure if specific to this version - client version I'm on is 9.4 MR1). It is caused when you have a SUBNM formula in a merged cell. Unmerge the cells and SUBNM works normally again. It's a pain though cause frequently you need to merge cells in reports with SUBNM.
Does anyone know if this a bug logged with IBM or is it a "documented feature"?!
It must be a bug (not sure if specific to this version - client version I'm on is 9.4 MR1). It is caused when you have a SUBNM formula in a merged cell. Unmerge the cells and SUBNM works normally again. It's a pain though cause frequently you need to merge cells in reports with SUBNM.
Does anyone know if this a bug logged with IBM or is it a "documented feature"?!