In AS2000, I used to include the member key as member property. This member
property was while passing IDs to reports via actions.
But in 2005, member properties dictate rollup paths - will having the member
key as member property cause any problems in AS2005?
How best can I pass the member keys to other applicatons via action?

Thank you!


--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...-olap/200511/1

This isn't true. Member properties/related attributes don't dictate rollup
paths. Data rolls up by granularities regardless of attribute relationships.

Actually, member's key is intrinsic member property, so you don't need to
define special one - and you can still use it in the actions if you wish.
P.S. In AS2005 you can even take any part of the composite key by using
Key0, Key1 etc syntax.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =