I need to hide a level for the time being. For explanation, you can set the
visible property to False for the [Store Country] level of Store dimension
of Foodmart 2000.

If you execute the following MDX query using AllMembers, you can see
[Store].[All Stores].[Test] as the unique name of a calculated member,
[Test].

WITH MEMBER Store.[All Stores].[Test] AS '1'
MEMBER Measures.StoreUniqueName AS 'Store.CurrentMember.UniqueName'
SELECT
{Measures.StoreUniqueName} on columns,
{[Store].AllMembers} on rows
FROM Sales

But, If you use the caculated member directly as following, you get binding
error.

WITH MEMBER Store.[All Stores].[Test] AS '1'
MEMBER Measures.StoreUniqueName AS 'Store.CurrentMember.UniqueName'
SELECT
{Measures.StoreUniqueName} on columns,
{[Store].[All Stores].[Test], [Store].AllMembers} on rows
FROM Sales

I'm not sure this behavior is reasonable or bug. But this is very important
issue for me and wish good response from Microsoft.

Thank you

Ohjoo Kwon

Hi Ohjoo,

Currently I am performing initial research on this problem and will update
you soon. Thanks for your patience.

Sincerely,

Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------

Hi Ohjoo,

This issue is still being research. I will provide you with an update once
I have new finding.

Thanks for your patience.

Sincerely,

Hong Tan
Microsoft OLAP Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Ohjoo,

I am still trying to find out a definitely answer on whether the behavior
that you were seeing is by design or bug. Based on my testing, I can tell
you that the calc member was created on the hidden level. I was able to
verify using the following MDX stmt.

WITH MEMBER Store.[All Stores].[Test] AS '1'
MEMBER Measures.LevelName AS 'Store.CurrentMember.Level.Name'
SELECT
{ Measures.LevelName} on columns,
{Store.Allmembers} on rows
FROM Sales

I can see the calc member "Test" was created at the [Store].[Country]
level, which is hidden, and this is why you were getting the name binding
error.

I am wondering what are you trying to accomplish here by?

Thanks

Hong Tan
Microsoft OLAP Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

In the same situation, I need to execute MDX query as following.

WITH MEMBER Store.[All Stores].[Test] AS '[Store].[All Stores].[WA] +
[Store].[All Stores].[CA]'
SELECT
{ Measures.[Unit Sales]} on columns,
{Time.Year.members} on rows
FROM Sales
WHERE (Store.[All Stores].[Test])

Thanks,
Ohjoo


"Hong Tan (MS)" <hongt (AT) online (DOT) microsoft.com> wrote

Hi Ohjoo,

Can you do this instead?

WITH MEMBER Store.[Test] AS '[Store].[All Stores].[WA] +
[Store].[All Stores].[CA]'
SELECT
{ Measures.[Unit Sales]} on columns,
{Time.Year.members} on rows
FROM Sales
WHERE (Store.[Test])

Thanks

Hong Tan
Microsoft OLAP Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Yes, I can use your example manually.

The problem is that my example is the case of a query automatically
generated by client tool such as ProClarity. For example, ProClarity
automatically generates calculated member using Aggregate() when selecting
multiple members on slice dimension.

Of course, it could be the tool's problem. But I'm not sure the tool can get
the information about visible setting. If not, they cannot solve this issue.

Thanks,
Ohjoo




"Hong Tan (MS)" <hongt (AT) online (DOT) microsoft.com> wrote

Hi Ohjoo,

I have talked to the development about this issue, the news that I got back
was this behavior is by design and expected.

Thanks

Hong Tan
Microsoft OLAP Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.