<?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: Row-Level-Reduction on multiple fields in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Section-Access-Row-Level-Reduction-on-multiple-fields/m-p/2532145#M108084</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/318816"&gt;@SauGuad&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, it is possible. There are two major things to keep in mind:&lt;/P&gt;&lt;P&gt;1 - Keep in mind Section Access reduces rows by a single column only, that means, if you need to reduce by multiple columns, you'll have to combine these columns into one.&lt;/P&gt;&lt;P&gt;2 - For each user, you must list every single combination of values that this user must has access too.&lt;BR /&gt;So, if your USER1 access to Team 1 to 1o and Queue 1 to 11, you have to do something like this:&lt;BR /&gt;USER1, TEAM1|QUEUE1&lt;BR /&gt;USER1, TEAM1|QUEUE2&lt;BR /&gt;USER1, TEAM1|QUEUE3&lt;BR /&gt;USER1, TEAM1|QUEUE..&lt;BR /&gt;USER1, TEAM1|QUEUE11&lt;BR /&gt;USER1, TEAM2|QUEUE1&lt;BR /&gt;USER1, TEAM2|QUEUE2&lt;BR /&gt;USER1, TEAM2|QUEUE3&lt;BR /&gt;USER1, TEAM2|QUEUE..&lt;BR /&gt;USER1, TEAM2|QUEUE11&lt;BR /&gt;...&lt;/P&gt;&lt;P&gt;USER1, TEAM10|QUEUE1&lt;BR /&gt;USER1, TEAM10|QUEUE2&lt;BR /&gt;USER1, TEAM10|QUEUE3&lt;BR /&gt;USER1, TEAM10|QUEUE..&lt;BR /&gt;USER1, TEAM10|QUEUE11&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A common practice is to create a BridgeTable to link the Fact table and Section Access table. You'll have to combine all possible values and associate those to the Fact and User tables. This great article will probably answer all your questions:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Design/Basics-for-complex-authorization/ba-p/1465872" target="_blank"&gt;Basics for complex authorization - Qlik Community - 1465872&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Mark Costa&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Sep 2025 17:55:21 GMT</pubDate>
    <dc:creator>marksouzacosta</dc:creator>
    <dc:date>2025-09-30T17:55:21Z</dc:date>
    <item>
      <title>Section Access: Row-Level-Reduction on multiple fields</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-Row-Level-Reduction-on-multiple-fields/m-p/2531636#M108024</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to implement &lt;STRONG&gt;section access with row-level reduction&amp;nbsp;&lt;/STRONG&gt;based on multiple fields.&lt;/P&gt;&lt;P&gt;We have to maintain&amp;nbsp;&lt;STRONG&gt;600+ users. We have&lt;/STRONG&gt;&amp;nbsp;a &lt;STRONG&gt;team assignment list in SharePoint&lt;/STRONG&gt;&amp;nbsp;(name, email, user-id, employee-id, role, team etc.)&lt;/P&gt;&lt;P&gt;The main&amp;nbsp;&lt;STRONG&gt;fact table&amp;nbsp;&lt;/STRONG&gt;is &lt;STRONG&gt;call data&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;The &lt;STRONG&gt;data reduction&lt;/STRONG&gt; should be based on &lt;STRONG&gt;two fields&lt;/STRONG&gt;: call_queue and team. For example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;User1&lt;/STRONG&gt;: Role = Manager from Team 1 → can see data&amp;nbsp;&lt;STRONG&gt;Team 1–Team 10&lt;/STRONG&gt; and &lt;STRONG&gt;Queue 1–Queue 11&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;User2&lt;/STRONG&gt;: Role = Team Coordinator from Team 2 → can see &lt;STRONG&gt;Team 2 only&lt;/STRONG&gt; and &lt;STRONG&gt;Queue 1–Queue 11&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I want to know if it is possible to &lt;STRONG&gt;dynamically create data reduction&lt;/STRONG&gt; based on the SharePoint list.&lt;BR /&gt;At the moment each row in the SharePoint list corresponds to &lt;STRONG&gt;one employee and one team (no call queue).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Depending on the user’s role, they may have access to &lt;STRONG&gt;several teams and queues.&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;Also, the call_queue field is part of the &lt;STRONG&gt;Call fact table&lt;/STRONG&gt; and is &lt;STRONG&gt;not in the team assignment SharePoint list&lt;/STRONG&gt;.&lt;BR /&gt;&lt;BR /&gt;Is there any good example using sharepoint list for dynamic row-level-security on multiple fields?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Sep 2025 16:09:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-Row-Level-Reduction-on-multiple-fields/m-p/2531636#M108024</guid>
      <dc:creator>SauGuad</dc:creator>
      <dc:date>2025-09-23T16:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access: Row-Level-Reduction on multiple fields</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-Row-Level-Reduction-on-multiple-fields/m-p/2532145#M108084</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/318816"&gt;@SauGuad&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, it is possible. There are two major things to keep in mind:&lt;/P&gt;&lt;P&gt;1 - Keep in mind Section Access reduces rows by a single column only, that means, if you need to reduce by multiple columns, you'll have to combine these columns into one.&lt;/P&gt;&lt;P&gt;2 - For each user, you must list every single combination of values that this user must has access too.&lt;BR /&gt;So, if your USER1 access to Team 1 to 1o and Queue 1 to 11, you have to do something like this:&lt;BR /&gt;USER1, TEAM1|QUEUE1&lt;BR /&gt;USER1, TEAM1|QUEUE2&lt;BR /&gt;USER1, TEAM1|QUEUE3&lt;BR /&gt;USER1, TEAM1|QUEUE..&lt;BR /&gt;USER1, TEAM1|QUEUE11&lt;BR /&gt;USER1, TEAM2|QUEUE1&lt;BR /&gt;USER1, TEAM2|QUEUE2&lt;BR /&gt;USER1, TEAM2|QUEUE3&lt;BR /&gt;USER1, TEAM2|QUEUE..&lt;BR /&gt;USER1, TEAM2|QUEUE11&lt;BR /&gt;...&lt;/P&gt;&lt;P&gt;USER1, TEAM10|QUEUE1&lt;BR /&gt;USER1, TEAM10|QUEUE2&lt;BR /&gt;USER1, TEAM10|QUEUE3&lt;BR /&gt;USER1, TEAM10|QUEUE..&lt;BR /&gt;USER1, TEAM10|QUEUE11&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A common practice is to create a BridgeTable to link the Fact table and Section Access table. You'll have to combine all possible values and associate those to the Fact and User tables. This great article will probably answer all your questions:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Design/Basics-for-complex-authorization/ba-p/1465872" target="_blank"&gt;Basics for complex authorization - Qlik Community - 1465872&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Mark Costa&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 17:55:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-Row-Level-Reduction-on-multiple-fields/m-p/2532145#M108084</guid>
      <dc:creator>marksouzacosta</dc:creator>
      <dc:date>2025-09-30T17:55:21Z</dc:date>
    </item>
  </channel>
</rss>

