<?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 Issue in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269157#M855862</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Add a single connection per user between you section access table and your data model, by reducing the two redundant columns USER1 and USER2 to a single one and creating a linking table (with the same user definitions) in your data model. You may have to redesign your data model to accomodate this security-by-using-a-single-key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an alternative, you can add dummy data to Table 2 that has an entry for missing users, but a NULL value in Data_T2. Then you can leave the Section Access table structure as is.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Feb 2017 12:46:47 GMT</pubDate>
    <dc:creator>Peter_Cammaert</dc:creator>
    <dc:date>2017-02-14T12:46:47Z</dc:date>
    <item>
      <title>Section Access Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269156#M855861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two data table as shown below along with section access details&lt;/P&gt;&lt;P&gt;Here&lt;/P&gt;&lt;UL style="list-style-type: disc;"&gt;&lt;LI&gt;in first table data for user A,B,C &amp;amp; D is available.&lt;/LI&gt;&lt;LI&gt;in second table data for user A,B &amp;amp; C is available. (D is missing)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="153054" alt="Capture.JPG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/153054_Capture.JPG" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Section Access is working fine&lt;/SPAN&gt; for user A, B &amp;amp; C.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;But user D is not able to access the file due to the data is not available for user D in table 2.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Hence user D is not able to access the data from any of other tables/analysis of the said file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way so that user D can access the data of other Tables where data of user is D.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Girish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269156#M855861</guid>
      <dc:creator>girish_talele</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269157#M855862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Add a single connection per user between you section access table and your data model, by reducing the two redundant columns USER1 and USER2 to a single one and creating a linking table (with the same user definitions) in your data model. You may have to redesign your data model to accomodate this security-by-using-a-single-key.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an alternative, you can add dummy data to Table 2 that has an entry for missing users, but a NULL value in Data_T2. Then you can leave the Section Access table structure as is.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2017 12:46:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269157#M855862</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2017-02-14T12:46:47Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269158#M855863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could create spoof users that are present in Table1 but not Table2 Data;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table1:&lt;/P&gt;&lt;P&gt;LOAD * INLINE [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; USER1, Data_T1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; A, 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; B, 200&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; C, 300&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; D, 400&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;P&gt;//=====================================================================================================================&lt;/P&gt;&lt;P&gt;Table2:&lt;/P&gt;&lt;P&gt;LOAD * INLINE [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; USER2, Data_T2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; A, 100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; B, 200&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; C, 300&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;P&gt;//=====================================================================================================================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/*&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*/&lt;/P&gt;&lt;P&gt;Concatenate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SpoofUsers:&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;USER1 as USER2,&lt;/P&gt;&lt;P&gt;'NoAccessToT2' as Data_T2&lt;/P&gt;&lt;P&gt;Resident Table1&lt;/P&gt;&lt;P&gt;Where not Exists(USER2,USER1);&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2017 13:34:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Section-Access-Issue/m-p/1269158#M855863</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-02-14T13:34:33Z</dc:date>
    </item>
  </channel>
</rss>

