It seems to me that length(MDX expression for Allowed/Default Member) is
limited to 32k !?
Is this true?
Is there any workaround?
Thanks,
Igor Mekterovic

Yes - this is almost for sure true. The workaround is to store your actual
string somewhere (in external data source etc - you cannot use member
property, because it will have similar limitation), and then StrToSet it for
AllowedSet or StrToMember for DefaultMember, although I am very curious why
would you need more then 32K for DefaultMember (I can understand why you
would need it for AllowedSet).

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
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.
==================================================

True - DefaultMember is not a must - I've been setting it the same as a
AllowedMember.
But AllowedMember is a must: with this limitation I can set about 800-900
allowed members in a dim. which is not so huge.
Could you elaborate a bit more your idea with external data source, I'm not
quite sure what ext.data source to use?
Thanks,
Igor
"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

For example - you store the string in file/database/LDAP etc, and then write
an UDF called GetMyAllowedSet() which knows how to fetch it. Then the
definition of the allowed set becomes

StrToSet(GetMyAllowedSet())

Note, that if you go that route, you will need to get post SP3 hotfixe which
enables use of UDFs in the dimension security.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
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.
==================================================
"Igor Mekterovic" <igor.mekterovic (AT) fer (DOT) hr> wrote