<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SAS MDX Security Filter and unbalanced hierarchies in SAS Web Report Studio</title>
    <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/SAS-MDX-Security-Filter-and-unbalanced-hierarchies/m-p/35284#M605</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are looking at a feasible security concept for unbalanced hierarchies. The MDX below fails to be applicable when a level is missing because in that case data would be retrieved from one or more levels higher than the user has clearance for.&lt;/P&gt;&lt;P&gt;Descendants(&lt;/P&gt;&lt;P&gt;Ancestor(&lt;/P&gt;&lt;P&gt;Head(&lt;/P&gt;&lt;P&gt;Filter(&lt;/P&gt;&lt;P&gt;[DIM_SALES].AllMembers,[DIM_SALES].CurrentMember.Level.Name = 'SELLER_ID' and [DIM_SALES].CurrentMember.Name = 'SUB::SAS.Userid')&lt;/P&gt;&lt;P&gt;).Item(0&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;,3)&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;3=&amp;nbsp; this MDX script applies to user in role “General Agent” so it means if the users, at bottom level SELLER_ID, is a general agent than go 3 levels up&amp;nbsp; sales_team, main agency, general agency. If , for some reason a main agency is missing it would go up to the level region_USA which is not so great because the user is in role “General Agent” and not “regional agent”. At the end the user would see too much data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does someone have an idea how that could be solved? I have doubts that this will work with MDX at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Jul 2011 08:17:06 GMT</pubDate>
    <dc:creator>metalray</dc:creator>
    <dc:date>2011-07-22T08:17:06Z</dc:date>
    <item>
      <title>SAS MDX Security Filter and unbalanced hierarchies</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/SAS-MDX-Security-Filter-and-unbalanced-hierarchies/m-p/35284#M605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are looking at a feasible security concept for unbalanced hierarchies. The MDX below fails to be applicable when a level is missing because in that case data would be retrieved from one or more levels higher than the user has clearance for.&lt;/P&gt;&lt;P&gt;Descendants(&lt;/P&gt;&lt;P&gt;Ancestor(&lt;/P&gt;&lt;P&gt;Head(&lt;/P&gt;&lt;P&gt;Filter(&lt;/P&gt;&lt;P&gt;[DIM_SALES].AllMembers,[DIM_SALES].CurrentMember.Level.Name = 'SELLER_ID' and [DIM_SALES].CurrentMember.Name = 'SUB::SAS.Userid')&lt;/P&gt;&lt;P&gt;).Item(0&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;,3)&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;3=&amp;nbsp; this MDX script applies to user in role “General Agent” so it means if the users, at bottom level SELLER_ID, is a general agent than go 3 levels up&amp;nbsp; sales_team, main agency, general agency. If , for some reason a main agency is missing it would go up to the level region_USA which is not so great because the user is in role “General Agent” and not “regional agent”. At the end the user would see too much data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does someone have an idea how that could be solved? I have doubts that this will work with MDX at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jul 2011 08:17:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/SAS-MDX-Security-Filter-and-unbalanced-hierarchies/m-p/35284#M605</guid>
      <dc:creator>metalray</dc:creator>
      <dc:date>2011-07-22T08:17:06Z</dc:date>
    </item>
  </channel>
</rss>

