<?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 Re: Section Access Removes Outer Join Effect  ? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454366#M169533</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appreciate suggestion. Yes that works - I have set that up already although I need to see year/month/day for 2 years so an extra 730 records approx. Was hoping that QV would have a more elegant solution. The reason I find it odd&amp;nbsp; that it is not part of the product is that Section Access is a big selling point and so too is the associative nature of&amp;nbsp; QV. Section access though immediately takes away the elegance of the associatve functionality imo.It changes a full outer join to a strict equi join. Selective Secton Access is what I need but your work around or an island table with a bunch of triggers are my only options for now it seems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks again for thoughts though - much appreciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Oct 2012 21:24:21 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-10-02T21:24:21Z</dc:date>
    <item>
      <title>Section Access Removes Outer Join Effect  ?</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454363#M169530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a dashbaord which has years and months as list boxes. I want to show several years and all months as availble selections like any onther dashboard. This works fine so far When I put in basic section access so a user only sees activity realting to himself, all months and years where no activity exist for that person are removed. So in the case of a month list box - a user with activity for just July for example, will have all other months removed form the list boxes - not grayed out but physiclaly removed making the list boxes look odd.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This on one hand seems logical as section access is designed to do this i.e. remove data unrelated to the user. In essence though I only want data from the Fact table removed via Section Access but it is applying it accross the model and reducting dimensions also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q. do I need to create an Island Calendar table to work around this - if so will this have an impact on performance - my current set analysis defintions are very fast currently on large data setes e.g. 20 million records. Perhaps there is a way to keep certain tables immune to section access at the script level ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q. Presumably this problem occurs for anyone using Section Access - is there a better way to solve the challenge ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Sep 2012 19:10:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454363#M169530</guid>
      <dc:creator />
      <dc:date>2012-09-28T19:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Removes Outer Join Effect  ?</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454364#M169531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;here is the question in a more simplified way - is it possible to add section access to just some tables but not all ? I want to see all years and months in my list boxes even though I have activity for a subset of that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for any possible thoughts on this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Oct 2012 19:09:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454364#M169531</guid>
      <dc:creator />
      <dc:date>2012-10-02T19:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Removes Outer Join Effect  ?</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454365#M169532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't believe section access will allow you to do that however you could add a dummy record to the end of the table that has just the year and a value in the key field that all users have access to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Oct 2012 20:01:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454365#M169532</guid>
      <dc:creator>Josh_Good</dc:creator>
      <dc:date>2012-10-02T20:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Removes Outer Join Effect  ?</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454366#M169533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appreciate suggestion. Yes that works - I have set that up already although I need to see year/month/day for 2 years so an extra 730 records approx. Was hoping that QV would have a more elegant solution. The reason I find it odd&amp;nbsp; that it is not part of the product is that Section Access is a big selling point and so too is the associative nature of&amp;nbsp; QV. Section access though immediately takes away the elegance of the associatve functionality imo.It changes a full outer join to a strict equi join. Selective Secton Access is what I need but your work around or an island table with a bunch of triggers are my only options for now it seems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks again for thoughts though - much appreciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Oct 2012 21:24:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454366#M169533</guid>
      <dc:creator />
      <dc:date>2012-10-02T21:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Removes Outer Join Effect  ?</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454367#M169534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Several years down the line, this persists. Is there a way to have section access in place and yet make the outer joins work (other than the extra records workaround, since that isn't an option at my end)? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;Benazir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jun 2018 12:06:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Removes-Outer-Join-Effect/m-p/454367#M169534</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-06-21T12:06:24Z</dc:date>
    </item>
  </channel>
</rss>

