I am attempting to use custom dimension security to filter a parent-child dimension hierarchy based on the position of the logged on user by setting the allowed members MDX (running SP3). Example: If B is the login user, filtered members include B and C (user can look down the hierarchy, but not up)

A
B
C

The problem is with the top level, as A is visible. My thought was to dynamically set the Top Level based on the Level of the login user. However, the following MDX generates an error: "The top visible level must have unique names."

StrToMember("[Hierarchy].&[" + UserName + "]").Level"

The Member Names Unique property is set to True for the Hierarchy dimension, so I'm not sure what is expected/allowed for Top Level expressions.

Thanks.

Hello ,

Thanks for posting to MSDN Managed Newsgroup. We appreciate your patience.

Custom MDX can be used for defining top, bottom and visual levels - but
you, as per my research, will need to install a QFE for that.
Also, it is possible, that UI won't let you to do it, so you will need to
code it directly in DSO.

To get the appropriate QFE you will need to contact Microsoft Product
Support Services at 1-(800)936-5800 or by choosing one of the options
listed at http://support.microsoft.com/default...d=sz;en-us;top. If
this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf (AT) online (DOT) microsoft.com with the following
information,

* Include "Followup: ISSUE ID 19810119 " in the email Subject.
*Location of the post
* First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address

Thanks,

Vikrant Dalwale

Microsoft SQL Server Support Professional


Microsoft highly recommends to all of our customers that they visit the
http://www.microsoft.com/protect site and perform the three straightforward
steps listed to improve your computer’s security."
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
the allowed members MDX (running SP3). Example: If B is the login user,
filtered members include B and C (user can look down the hierarchy, but not
up)

A
B
C

The problem is with the top level, as A is visible. My thought was to
dynamically set the Top Level based on the Level of the login user.
However, the following MDX generates an error: "The top visible level must
have unique names."

StrToMember("[Hierarchy].&[" + UserName + "]").Level"

The Member Names Unique property is set to True for the Hierarchy
dimension, so I'm not sure what is expected/allowed for Top Level
expressions.

Thanks.

Thanks for your response. Is this QFE the same mentioned in the Dynamic
Dimension Security Web Cast related to using UDFs
(http://support.microsoft.com/default.aspx?kbid=828343)?


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Thanks for your response. Is this QFE the same mentioned in the Dynamic
Dimension Security Web Cast related to using UDFs
(http://support.microsoft.com/default.aspx?kbid=828343)?


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Hello Jason,

I think it's a different QFE. For the best interest, Its recommended to
contact Microsoft PSS or have us contact you
directly if you could provide us with your contact information as dicussed
in my previous post.

Thanks for posting to MSDN Managed Newsgroups,

Vikrant Dalwale

Microsoft SQL Server Support Professional


Microsoft highly recommends to all of our customers that they visit the
http://www.microsoft.com/protect site and perform the three straightforward
steps listed to improve your computer’s security."
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------