All member relationships are returned when you set the AttributeRelationship Visible property of an attribute to true or to false in SQL Server 2005 Analysis Services (915855)

MORE INFORMATION

Steps to reproduce the problem

1. Start Business Intelligence Development Studio.
2. On the File menu, click Open, and then click Analysis Services Database.
3. In the Connect to Database dialog box, click Connect to Existing Database.
4. In the Server box, type the name of the server.
5. In the Database list, click Adventure Works DW, and then click OK.
6. In Solution Explorer, expand Dimensions, and then double-click Customer.
7. In the Hierarchies and Levels pane, under Customer Geography, expand City, and then click the State-Province attribute relationship.
8. In the Properties window, under State-Province AttributeRelationship, click Visible, and then click False.
9. To process the database, click Process on the Database menu.
10. Start SQL Server Management Studio.
11. In Object Explorer, expand Databases, right-click Analysis Services Tutorial, click New Query, and then click XMLA.
12. In the XML for Analysis (XMLA) query window, run the following XMLA query.

    <Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
    <RequestType>MDSCHEMA_MEMBERS</RequestType>
    <Restrictions>
    <RestrictionList>
    <CATALOG_NAME>Adventure Works DW</CATALOG_NAME>
    <CUBE_NAME>Adventure Works</CUBE_NAME>
    <MEMBER_UNIQUE_NAME>[Customer].[Customer Geography].[City].&amp;[Alexandria]&amp;[NSW]</MEMBER_UNIQUE_NAME>
    </RestrictionList>
    </Restrictions>
    <Properties>
    <PropertyList>
    <Catalog>Adventure Works DW</Catalog>
    <Format>Tabular</Format>
    </PropertyList>
    </Properties>
    </Discover>
    

    You receive the following results.

    <row>
    <CATALOG_NAME>Adventure Works DW Standard Edition</CATALOG_NAME>
    <CUBE_NAME>Adventure Works</CUBE_NAME>
    <DIMENSION_UNIQUE_NAME>[Customer]</DIMENSION_UNIQUE_NAME>
    <HIERARCHY_UNIQUE_NAME>[Customer].[Customer Geography]</HIERARCHY_UNIQUE_NAME>
    <LEVEL_UNIQUE_NAME>[Customer].[Customer Geography].[City]</LEVEL_UNIQUE_NAME>
    <LEVEL_NUMBER>3</LEVEL_NUMBER>
    <MEMBER_ORDINAL>80</MEMBER_ORDINAL>
    <MEMBER_NAME>Alexandria</MEMBER_NAME>
    <MEMBER_UNIQUE_NAME>[Customer].[Customer Geography].[City].&amp;[Alexandria]&amp;[NSW]</MEMBER_UNIQUE_NAME>
    <MEMBER_TYPE>1</MEMBER_TYPE>
    <MEMBER_CAPTION>Alexandria</MEMBER_CAPTION>
    <CHILDREN_CARDINALITY>1</CHILDREN_CARDINALITY>
    <PARENT_LEVEL>2</PARENT_LEVEL>
    <PARENT_UNIQUE_NAME>[Customer].[Customer Geography].[State-Province].&amp;[NSW]&amp;[AU]</PARENT_UNIQUE_NAME>
    <PARENT_COUNT>1</PARENT_COUNT>
    <IS_PLACEHOLDERMEMBER>false</IS_PLACEHOLDERMEMBER>
    <IS_DATAMEMBER>false</IS_DATAMEMBER>
    <State-Province>New South Wales</State-Province>
    </row>
    

    Note You expect to receive the following results.

    <row>
    <CATALOG_NAME>Adventure Works DW Standard Edition</CATALOG_NAME>
    <CUBE_NAME>Adventure Works</CUBE_NAME>
    <DIMENSION_UNIQUE_NAME>[Customer]</DIMENSION_UNIQUE_NAME>
    <HIERARCHY_UNIQUE_NAME>[Customer].[Customer Geography]</HIERARCHY_UNIQUE_NAME>
    <LEVEL_UNIQUE_NAME>[Customer].[Customer Geography].[City]</LEVEL_UNIQUE_NAME>
    <LEVEL_NUMBER>3</LEVEL_NUMBER>
    <MEMBER_ORDINAL>80</MEMBER_ORDINAL>
    <MEMBER_NAME>Alexandria</MEMBER_NAME>
    <MEMBER_UNIQUE_NAME>[Customer].[Customer Geography].[City].&amp;[Alexandria]&amp;[NSW]</MEMBER_UNIQUE_NAME>
    <MEMBER_TYPE>1</MEMBER_TYPE>
    <MEMBER_CAPTION>Alexandria</MEMBER_CAPTION>
    <CHILDREN_CARDINALITY>1</CHILDREN_CARDINALITY>
    <PARENT_LEVEL>2</PARENT_LEVEL>
    <PARENT_UNIQUE_NAME>[Customer].[Customer Geography].[State-Province].&amp;[NSW]&amp;[AU]</PARENT_UNIQUE_NAME>
    <PARENT_COUNT>1</PARENT_COUNT>
    <IS_PLACEHOLDERMEMBER>false</IS_PLACEHOLDERMEMBER>
    <IS_DATAMEMBER>false</IS_DATAMEMBER>
    </row>