<?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 NTDOMAINSID in section access not working in November 2020 in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/NTDOMAINSID-in-section-access-not-working-in-November-2020/m-p/1767370#M17057</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;I've just upgraded to Qliksense November 2020 from June 2020.&amp;nbsp; In June 2020 there were bugs in the section access and I've picked up additional problems in this release.&amp;nbsp; We currently run code similar to the below for our section access where we include the NTDOMAINSID (i've just starred out the actual SID).&lt;/P&gt;&lt;P&gt;We binary load from a number of Qlikview apps which use this sort of section access.&amp;nbsp; After upgrading these binary loads all fail with a "General Script Error."&amp;nbsp; I've double-checked the NTDOMAINSID we've used and it's correct.&amp;nbsp; As soon as I remove it from the section access, binary load succeeds.&lt;/P&gt;&lt;P&gt;Is this a known issue?&amp;nbsp; Is there any workaround?&amp;nbsp; I'm guessing it hasn't been picked up as not all clients use the NTDOMAINSID?&lt;/P&gt;&lt;P&gt;star is *;&lt;BR /&gt;section access;&lt;BR /&gt;// Load Customer users and passwords&lt;BR /&gt;SECURITY:&lt;BR /&gt;Load //NT AUTHENTICATION&lt;BR /&gt;IF(LEFT([TYPE],1) = 'A','USER','ADMIN') AS ACCESS,&lt;BR /&gt;upper([USERID]) AS NTNAME,&lt;BR /&gt;'S-1-5-21-*****-***-***' AS NTDOMAINSID,&lt;BR /&gt;'*' AS USERID,&lt;BR /&gt;'*' AS PASSWORD&lt;BR /&gt;FROM [$(vSecurity_Path)] (biff, embedded labels, table is [$(vUserSheet)$]);&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;section application;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;star is ;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Dec 2020 15:23:52 GMT</pubDate>
    <dc:creator>nsm1234567</dc:creator>
    <dc:date>2020-12-09T15:23:52Z</dc:date>
    <item>
      <title>NTDOMAINSID in section access not working in November 2020</title>
      <link>https://community.qlik.com/t5/Management-Governance/NTDOMAINSID-in-section-access-not-working-in-November-2020/m-p/1767370#M17057</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;I've just upgraded to Qliksense November 2020 from June 2020.&amp;nbsp; In June 2020 there were bugs in the section access and I've picked up additional problems in this release.&amp;nbsp; We currently run code similar to the below for our section access where we include the NTDOMAINSID (i've just starred out the actual SID).&lt;/P&gt;&lt;P&gt;We binary load from a number of Qlikview apps which use this sort of section access.&amp;nbsp; After upgrading these binary loads all fail with a "General Script Error."&amp;nbsp; I've double-checked the NTDOMAINSID we've used and it's correct.&amp;nbsp; As soon as I remove it from the section access, binary load succeeds.&lt;/P&gt;&lt;P&gt;Is this a known issue?&amp;nbsp; Is there any workaround?&amp;nbsp; I'm guessing it hasn't been picked up as not all clients use the NTDOMAINSID?&lt;/P&gt;&lt;P&gt;star is *;&lt;BR /&gt;section access;&lt;BR /&gt;// Load Customer users and passwords&lt;BR /&gt;SECURITY:&lt;BR /&gt;Load //NT AUTHENTICATION&lt;BR /&gt;IF(LEFT([TYPE],1) = 'A','USER','ADMIN') AS ACCESS,&lt;BR /&gt;upper([USERID]) AS NTNAME,&lt;BR /&gt;'S-1-5-21-*****-***-***' AS NTDOMAINSID,&lt;BR /&gt;'*' AS USERID,&lt;BR /&gt;'*' AS PASSWORD&lt;BR /&gt;FROM [$(vSecurity_Path)] (biff, embedded labels, table is [$(vUserSheet)$]);&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;section application;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;star is ;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2020 15:23:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/NTDOMAINSID-in-section-access-not-working-in-November-2020/m-p/1767370#M17057</guid>
      <dc:creator>nsm1234567</dc:creator>
      <dc:date>2020-12-09T15:23:52Z</dc:date>
    </item>
  </channel>
</rss>

