<?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 View All in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Section-Access-View-All/m-p/1807513#M65731</link>
    <description>&lt;P&gt;Apparently I found the answer, per documentation &amp;gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;If a wildcard (*) is used as a field value in the data reduction column, it is interpreted as allowing the user to access &lt;STRONG&gt;records associated with all selected reduction fields in the security table."&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since FIELD3 isn't in the security table it won't show up. I guess it makes sense but adds a layer of additional complexity for creating new section access fields.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 May 2021 21:27:40 GMT</pubDate>
    <dc:creator>derrydavis</dc:creator>
    <dc:date>2021-05-12T21:27:40Z</dc:date>
    <item>
      <title>Section Access View All</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-View-All/m-p/1807511#M65730</link>
      <description>&lt;P&gt;Ran into a problem with section access and the '*' access. Using the section access script of&lt;/P&gt;&lt;P&gt;LOAD * INLINE [&lt;/P&gt;&lt;P&gt;ACCESS, USERID, GROUP, FIELD, OMIT&lt;/P&gt;&lt;P&gt;USER, *, GROUP1, FIELD1&lt;/P&gt;&lt;P&gt;USER, *, GROUP2, FIELD2&lt;/P&gt;&lt;P&gt;USER, *, GROUP3, *&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;etc. I've found that GROUP3 can see FIELD1 and FIELD2 but if there is a FIELD3 it does not load and no one can see it.&lt;/P&gt;&lt;P&gt;Is this normal behavior and a group has to be defined for every value of 'FIELD'? That doesn't seem right to me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: I've tried using the STAR is * command and it doesn't make a difference.&lt;/P&gt;&lt;P&gt;EDIT2: we are using a domain and adding the domain name as a prefix actually breaks things and the data won't load.&amp;nbsp;&lt;/P&gt;&lt;P&gt;example: DIR\GROUP1 no longer gives access to FIELD1&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2021 21:19:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-View-All/m-p/1807511#M65730</guid>
      <dc:creator>derrydavis</dc:creator>
      <dc:date>2021-05-12T21:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access View All</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-View-All/m-p/1807513#M65731</link>
      <description>&lt;P&gt;Apparently I found the answer, per documentation &amp;gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;If a wildcard (*) is used as a field value in the data reduction column, it is interpreted as allowing the user to access &lt;STRONG&gt;records associated with all selected reduction fields in the security table."&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since FIELD3 isn't in the security table it won't show up. I guess it makes sense but adds a layer of additional complexity for creating new section access fields.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2021 21:27:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-View-All/m-p/1807513#M65731</guid>
      <dc:creator>derrydavis</dc:creator>
      <dc:date>2021-05-12T21:27:40Z</dc:date>
    </item>
  </channel>
</rss>

