<?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 Section Access field names: Upper case or not in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Section-Access-field-names-Upper-case-or-not/m-p/2504778#M103833</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;since ever, it is well known that field names in Section Access must be written in Upper Case.&lt;BR /&gt;This is well documented for all Qlik Sense editions (and Qlikview too)&lt;/P&gt;
&lt;P&gt;Nevertheless, sometimes Section Access is working even with Lowercase field names.&lt;/P&gt;
&lt;P&gt;This simple script is working in a test app. &lt;STRONG&gt;Field1&lt;/STRONG&gt; is limited to 'A' value.&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Section Access;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;LOAD&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'USER' AS ACCESS,&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'username@domain.com' as USER.EMAIL,&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'A' as &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Field1&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;AUTOGENERATE 1;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Section Application;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Table:&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;LOAD * INLINE [&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Field1&lt;/EM&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;A&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;B&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;C&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;So why bother with translating to upper case if it working anyway? Is there any deterministic rule to this behaviour?&lt;/DIV&gt;
&lt;DIV&gt;By the way, the same table with an INLINE instead of AUTOGENERATE will result in an upper case field name (FIELD1), therefore in the above situation, the field won't be filtered.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;Regards&lt;/DIV&gt;
&lt;DIV&gt;Paolo&lt;/DIV&gt;</description>
    <pubDate>Thu, 06 Feb 2025 10:27:49 GMT</pubDate>
    <dc:creator>paolo_cordini</dc:creator>
    <dc:date>2025-02-06T10:27:49Z</dc:date>
    <item>
      <title>Section Access field names: Upper case or not</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-field-names-Upper-case-or-not/m-p/2504778#M103833</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;since ever, it is well known that field names in Section Access must be written in Upper Case.&lt;BR /&gt;This is well documented for all Qlik Sense editions (and Qlikview too)&lt;/P&gt;
&lt;P&gt;Nevertheless, sometimes Section Access is working even with Lowercase field names.&lt;/P&gt;
&lt;P&gt;This simple script is working in a test app. &lt;STRONG&gt;Field1&lt;/STRONG&gt; is limited to 'A' value.&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Section Access;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;LOAD&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'USER' AS ACCESS,&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'username@domain.com' as USER.EMAIL,&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt; 'A' as &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Field1&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;AUTOGENERATE 1;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Section Application;&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Table:&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;LOAD * INLINE [&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;Field1&lt;/EM&gt;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;A&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;B&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;C&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;So why bother with translating to upper case if it working anyway? Is there any deterministic rule to this behaviour?&lt;/DIV&gt;
&lt;DIV&gt;By the way, the same table with an INLINE instead of AUTOGENERATE will result in an upper case field name (FIELD1), therefore in the above situation, the field won't be filtered.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;Regards&lt;/DIV&gt;
&lt;DIV&gt;Paolo&lt;/DIV&gt;</description>
      <pubDate>Thu, 06 Feb 2025 10:27:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-field-names-Upper-case-or-not/m-p/2504778#M103833</guid>
      <dc:creator>paolo_cordini</dc:creator>
      <dc:date>2025-02-06T10:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: Section Access field names: Upper case or not</title>
      <link>https://community.qlik.com/t5/App-Development/Section-Access-field-names-Upper-case-or-not/m-p/2504823#M103844</link>
      <description>&lt;P&gt;I haven't tested if it works as you say, but I'll assume you're correct. "&lt;SPAN&gt;So why bother with translating to upper case if it working anyway?" Well, I'd say you should bother because the section access syntax defines it. If it works now, it doesn't necessarily mean that it will still work in the next version.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2025 14:41:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Section-Access-field-names-Upper-case-or-not/m-p/2504823#M103844</guid>
      <dc:creator>henrikalmen</dc:creator>
      <dc:date>2025-02-06T14:41:54Z</dc:date>
    </item>
  </channel>
</rss>

