<?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 table rows limit in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Section-access-table-rows-limit/m-p/2436689#M97051</link>
    <description>&lt;P&gt;I could imagine that a valide testing would be possible even with such large section access table by checking a few users from the start/mid/end of the access-table which should exclude that any of them are ignored (completely excluding or having full access) even if the script doesn't return any error.&lt;/P&gt;
&lt;P&gt;Beside of this I'm not sure that such granular section access is sensible at all - because who could really define it with such details? I think it would be helpful to apply the access to higher groupings of the related fields - maybe by an extra load-layer which mapped it to the link-table, for example replacing the period-listing of YYYYMM just to a 0/1 flag.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Apr 2024 10:47:59 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2024-04-02T10:47:59Z</dc:date>
    <item>
      <title>Section access table rows limit</title>
      <link>https://community.qlik.com/t5/App-Development/Section-access-table-rows-limit/m-p/2436633#M97048</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;I'm working on Qlik Sense May 2023 Patch1 version&lt;BR /&gt;In previous version (can't remember which) there was a limitation for section access table to hold 1 million records maximum&lt;BR /&gt;Now&lt;BR /&gt;I got in my schema a huge link-table which is connected to several fact tables&lt;BR /&gt;in this table I'm creating a field named SECURITY_KEY&amp;nbsp;&lt;BR /&gt;ex:&lt;BR /&gt;Project, Resource, Month_Year, SECURITY_KEY&lt;BR /&gt;P1, R1, 202401, AUTONUMBER(Project &amp;amp; Resource)&lt;BR /&gt;P1, R1, 202402&lt;BR /&gt;P1, R1, 202403&lt;BR /&gt;...&lt;/P&gt;
&lt;P&gt;in this case above the seucrity_key values will be let's say 23,23,23&lt;BR /&gt;so in the section access table suppose a user can see data related to P1, and R1, then there will be one record for this user&lt;BR /&gt;ex:&lt;/P&gt;
&lt;P&gt;ACCESS, USERID, SECURITY_KEY&lt;BR /&gt;USER, domain\user1, 23&lt;BR /&gt;&lt;BR /&gt;now there is a requirement that says that users can see data related to P1, and R1 by period&lt;BR /&gt;suppose user1 can see data for P1 and R1 for all months, then in the section access he will have 3 records which is the distinct combinations of all possible security keys in the link table&lt;BR /&gt;&lt;BR /&gt;my question here the section access table will grow immensely in size (no of rows)&lt;BR /&gt;would section access still function? because in previous versions of Qlik sense there was a limitation of 1 million records for the section access table.&lt;BR /&gt;&lt;BR /&gt;you may tell me test it to see, but the thing is that I cannot check so many cases&lt;BR /&gt;Kindly advise&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2024 08:41:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-access-table-rows-limit/m-p/2436633#M97048</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2024-04-02T08:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: Section access table rows limit</title>
      <link>https://community.qlik.com/t5/App-Development/Section-access-table-rows-limit/m-p/2436689#M97051</link>
      <description>&lt;P&gt;I could imagine that a valide testing would be possible even with such large section access table by checking a few users from the start/mid/end of the access-table which should exclude that any of them are ignored (completely excluding or having full access) even if the script doesn't return any error.&lt;/P&gt;
&lt;P&gt;Beside of this I'm not sure that such granular section access is sensible at all - because who could really define it with such details? I think it would be helpful to apply the access to higher groupings of the related fields - maybe by an extra load-layer which mapped it to the link-table, for example replacing the period-listing of YYYYMM just to a 0/1 flag.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2024 10:47:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-access-table-rows-limit/m-p/2436689#M97051</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-04-02T10:47:59Z</dc:date>
    </item>
  </channel>
</rss>

