What I would suggest is a MDX parameter for the SUBNM function, the way it is implemented as an optional parameter within the TM1RPTROW function.
That would be a very powerful possibility to circumvent dynamic subsets and would allow for easy user-/data-specific frontend interaction, too.
This would easily enable a bunch of nice features such as an user-specific pre-selection of elements having data(, if there is no dimension security in place).
Or is there any possibility to do that with picklists?
Optional MDX parameter for the SUBNM function
-
jpm_de
- Posts: 22
- Joined: Thu Jun 10, 2010 5:19 pm
- OLAP Product: TM1
- Version: 10.2.2 FP3
- Excel Version: 2010
Optional MDX parameter for the SUBNM function
Why TM1? Because ...with great dimensionality there must also come -- great responsibility!
(http://www.quotecounterquote.com/2012/0 ... great.html)
(http://www.quotecounterquote.com/2012/0 ... great.html)
-
lotsaram
- MVP
- Posts: 3698
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: MDXSetNm formula
This would be a great feature but it would be much more likely to be implemented as a new formula (and much more logically too.) The whole purpose of the SubNm formula is to call members of a subset so I can't see that this would be changed. Still a great idea though. Maybe MDXSetNm?
MDXSetNm("server:dimension","MDX",Index, [Alias])
MDXSetNm("server:dimension","MDX",Index, [Alias])