<?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 Scrambling and Section Access in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457005#M170632</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a dashboard with confidential information that only certain users can see, but I cannot use OMIT in section access because I still want the field in the chart visible, but scrambled. What I want is so that for User Group 1, the field "Name" is not scrambled, while for User Group 2, the field "Name" is scrambled. I can do it in the load script using HASH128(Name), but is there a way for that to only happen with certain users? Please let me know if you can help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Jun 2013 15:55:38 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-06-10T15:55:38Z</dc:date>
    <item>
      <title>Scrambling and Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457005#M170632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a dashboard with confidential information that only certain users can see, but I cannot use OMIT in section access because I still want the field in the chart visible, but scrambled. What I want is so that for User Group 1, the field "Name" is not scrambled, while for User Group 2, the field "Name" is scrambled. I can do it in the load script using HASH128(Name), but is there a way for that to only happen with certain users? Please let me know if you can help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2013 15:55:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457005#M170632</guid>
      <dc:creator />
      <dc:date>2013-06-10T15:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: Scrambling and Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457006#M170633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See attached example. The users are Admin, User1 and User2 with the same passwords as the names. User1 gets to see the Product field, User2 gets to see the ScrambledProduct field. The chart dynamically shows the proper field based on section access and mapping in the FieldUser table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2013 16:21:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457006#M170633</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2013-06-10T16:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Scrambling and Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457007#M170634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why not just create two fields, so USER1 can see the "unscrambled" data and USER2 can only see the scrabbled data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Section Access;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD * INLINE [&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ACCESS,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;USERID, OMIT &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; USER,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;USER1,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;SENSATIVE_DATA &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; USER,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;USER2,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;SENSATIVE_DATA_HASH123&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ADMIN,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ADMIN, &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Section Application;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD * &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;,RowNo() AS id&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;,Hash128(SENSATIVE_DATA) AS SENSATIVE_DATA_HASH123;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD * Inline [SENSATIVE_DATA&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;A&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;B&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;C&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2013 16:25:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457007#M170634</guid>
      <dc:creator>RedSky001</dc:creator>
      <dc:date>2013-06-10T16:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: Scrambling and Section Access</title>
      <link>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457008#M170635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you both, this is exactly what I needed!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2013 16:28:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Scrambling-and-Section-Access/m-p/457008#M170635</guid>
      <dc:creator />
      <dc:date>2013-06-10T16:28:27Z</dc:date>
    </item>
  </channel>
</rss>

