<?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: Binary load with Section Access in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617549#M445532</link>
    <description>&lt;P&gt;As I wrote in my first reply: should not be an error message, but security behavior should be controlled by the coming app section access rule.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Aug 2019 10:49:06 GMT</pubDate>
    <dc:creator>tresB</dc:creator>
    <dc:date>2019-08-28T10:49:06Z</dc:date>
    <item>
      <title>Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617528#M445523</link>
      <description>&lt;P&gt;&lt;FONT face="Times New Roman, serif"&gt;&lt;FONT size="3"&gt;&lt;FONT color="#3d3d3d"&gt;&lt;FONT face="Helvetica, serif"&gt;&lt;FONT size="2"&gt;In two qvw files, if it is loaded with binary load, will section access applied on other affect the next qvw? Will the section access be carried forward? Suppose this allows binary load, which option needs to be selected to follow this approach?&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 02:37:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617528#M445523</guid>
      <dc:creator>sujit_nath</dc:creator>
      <dc:date>2024-11-16T02:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617537#M445527</link>
      <description>&lt;P&gt;Section access that comes with binary loaded file would &lt;STRONG&gt;override&lt;/STRONG&gt; the destination file's section access (if any). To avoid this security goof up, you should always check &lt;STRONG&gt;'Prohibit Binary Load'&lt;/STRONG&gt; (Document Properties-&amp;gt;Opening tab) where you have section access in the qvw file.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 10:31:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617537#M445527</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2019-08-28T10:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617543#M445528</link>
      <description>&lt;P&gt;Hi Tresesco, Thanks for your reply! I am in a doubt that the 2nd qvw that's binary loaded from 1st will inherit the Section access from it's parent? I am trying to do so, but gives an error not sure if this is possible, or I'm making a mistake.&lt;/P&gt;&lt;P&gt;Please let me know what is the expected behaviour in this scenario.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 10:41:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617543#M445528</guid>
      <dc:creator>sujit_nath</dc:creator>
      <dc:date>2019-08-28T10:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617545#M445529</link>
      <description>&lt;P&gt;What error message are you getting?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 10:44:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617545#M445529</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2019-08-28T10:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617547#M445530</link>
      <description>&lt;P&gt;I don't have the scenario handy now. Would share it tonight. However, could you mention what to expect in this case.&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 10:46:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617547#M445530</guid>
      <dc:creator>sujit_nath</dc:creator>
      <dc:date>2019-08-28T10:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617549#M445532</link>
      <description>&lt;P&gt;As I wrote in my first reply: should not be an error message, but security behavior should be controlled by the coming app section access rule.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 10:49:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617549#M445532</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2019-08-28T10:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617560#M445533</link>
      <description>&lt;P&gt;While the application values (those not in the section access table) may concatenate or create synthetic keys, the last table with section access to be loaded will remain and override the previous ones.&lt;/P&gt;
&lt;P&gt;Say I'm DOMAIN\USER1 and I have a File1.qvw with section access with the following line&lt;/P&gt;
&lt;P&gt;USER, DOMAIN\USER1, SPAIN&lt;/P&gt;
&lt;P&gt;Then I have File2.qvw that binary loads File1.qvw and section access with&amp;nbsp;&lt;/P&gt;
&lt;P&gt;USER, DOMAIN\USER1, FRANCE&lt;/P&gt;
&lt;P&gt;When I open File2.qvw, I will only see FRANCE, the section access table in File2 overrode the previous one.&lt;/P&gt;
&lt;P&gt;If you want to have both values, keep the section access code in a QVS file that you load via $(Include=). You can play with the name of the file and string functions to load different files in that include.&lt;/P&gt;
&lt;P&gt;For example, I have a section access DEVELOPMENT.qvs which allows all developers to open the app and see fake data, not real, production data and PRODUCTION.qvs with all users including developers. I could choose which table I want to load based on which server the app is hosted.&lt;/P&gt;
&lt;P&gt;Similarly, I could load both section access tables as normal tables, so they concatenate, then load that table with all values into a section access table via RESIDENT.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 11:05:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1617560#M445533</guid>
      <dc:creator>Miguel_Angel_Baeyens</dc:creator>
      <dc:date>2019-08-28T11:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618420#M445593</link>
      <description>&lt;P&gt;It says can not access the file file1.qvw &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2019 16:07:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618420#M445593</guid>
      <dc:creator>sujit_nath</dc:creator>
      <dc:date>2019-08-29T16:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618615#M445601</link>
      <description>&lt;P&gt;That probably means that as per the section access in file2 user login doesn't have right to access data of file1.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2019 06:20:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618615#M445601</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2019-08-30T06:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618646#M445602</link>
      <description>&lt;P&gt;Such difference between app1 and app2 could occur if the option of "strict exclusion" in the section access settings (document properties in tab open) is set differently, for example if it disabled in app1 and enabled in app2:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-8562" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;Section Access: Strict Exclusion&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Another point are the set active directory access rights which might be set differently in any way.&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2019 07:25:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1618646#M445602</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2019-08-30T07:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1620711#M445774</link>
      <description>&lt;P&gt;Sujit, my understanding of how things worked was that if you had Section Access in the binary, that definitely came through into the new document doing the binary load of the original and that any Section Access in the new app was concatenated to the binary loaded Section Access.&amp;nbsp; I went to the one source I thought might have some clarification on this:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Unfortunately, HIC did not mention anything regarding binary load.&amp;nbsp; Same strike out on the Help for Section Access as well:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2019/Subsystems/QMC/Content/QV_QMC/QMC_Users_SectionAccessManagement.htm" target="_blank"&gt;https://help.qlik.com/en-US/qlikview/April2019/Subsystems/QMC/Content/QV_QMC/QMC_Users_SectionAccessManagement.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Success on the following though:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2019/Subsystems/Client/Content/QV_QlikView/Scripting/ScriptRegularStatements/Binary.htm" target="_blank"&gt;https://help.qlik.com/en-US/qlikview/April2019/Subsystems/Client/Content/QV_QlikView/Scripting/ScriptRegularStatements/Binary.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;There it does state Section Access is pulled in...&amp;nbsp; It does not confirm exactly what happens if you also have a Section Access load in the new app...&lt;/P&gt;
&lt;P&gt;I am going to reach out to one of the guys I know will likely know for sure to see if they can have a look at this post and leave a comment.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2019 18:35:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1620711#M445774</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2019-09-05T18:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: Binary load with Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1620713#M445775</link>
      <description>&lt;P&gt;Thanks Brett for this explanation.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2019 18:48:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Binary-load-with-Section-Access/m-p/1620713#M445775</guid>
      <dc:creator>sujit_nath</dc:creator>
      <dc:date>2019-09-05T18:48:17Z</dc:date>
    </item>
  </channel>
</rss>

