<?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: OMIT In data reduction in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/OMIT-In-data-reduction/m-p/637738#M1089488</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OMIT will remove a complete field from the data model for the specific user, but I believe you can't add any logic here to the section access (especially since it looks like you want a record based logic here).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please have a look at&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization" title="http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Jun 2014 21:18:15 GMT</pubDate>
    <dc:creator>swuehl</dc:creator>
    <dc:date>2014-06-03T21:18:15Z</dc:date>
    <item>
      <title>OMIT In data reduction</title>
      <link>https://community.qlik.com/t5/QlikView/OMIT-In-data-reduction/m-p/637737#M1089487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi people&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to do data reduction in my document, and i want to NOT to SHOW some fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example, it is a financial document and the users cant see the lines if it is an employee, nobody can see the employee information for example the employee salary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i want to know if the OMIT property in secction acces allow me to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for example :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the users can not see lines if the TIPE EMPLOYEE is = 2, but i want to see all the rest of tipe employee for example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i attach an excel to have an example of secction acces&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you a lot&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fernando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jun 2014 18:46:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/OMIT-In-data-reduction/m-p/637737#M1089487</guid>
      <dc:creator>fkeuroglian</dc:creator>
      <dc:date>2014-06-03T18:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: OMIT In data reduction</title>
      <link>https://community.qlik.com/t5/QlikView/OMIT-In-data-reduction/m-p/637738#M1089488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OMIT will remove a complete field from the data model for the specific user, but I believe you can't add any logic here to the section access (especially since it looks like you want a record based logic here).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please have a look at&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/05/26/section-access&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields" title="http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2014/06/02/data-reduction-using-multiple-fields&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization" title="http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/02/complex-authorization&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jun 2014 21:18:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/OMIT-In-data-reduction/m-p/637738#M1089488</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2014-06-03T21:18:15Z</dc:date>
    </item>
  </channel>
</rss>

